Update project page/README and example issue-75; rebuild project

.gitignore

@@ -3,3 +3,4 @@ node_modules
 package-lock.json
 registry-data
 .idea
+_site

README.md

@@ -1,38 +1,47 @@
+---
+title: Project Page
+---
+
 # Docker Registry UI
 
 ## Overview
 
-This project aims to provide a user interface for your private docker registry v2.
+This project aims to provide a simple and complete user interface for your private docker registry.
-There is no default registry on this UI, you should add your own with the UI.
+You have the choice between two versions, the **standard interface** and the **static interface**.
+
+In the **standard interface**, there is no default registry, you need to add your own within the UI.
 You can manage more than one registry server.
-All registries will be stored in the [local storage](https://en.wikipedia.org/wiki/Web_storage#Local_and_session_storage) of your browser.
+All registries will be stored in the [local storage](https://en.wikipedia.org/wiki/Web_storage#Local_and_session_storage) of your browser. No configuration is needed when you launch the UI.
+
+In the **static interface**, it will connect to a single registry and will not change. The configuration is done at the start of the interface, when you use the docker images whose tags contain the `static` keyword.
 
 This web user interface uses [Riot](https://github.com/Riot/riot) the react-like user interface micro-library and [riot-mui](https://github.com/kysonic/riot-mui) components.
 
-## [GitHub Page](https://joxit.dev/docker-registry-ui) and [Live Demo](https://joxit.dev/docker-registry-ui/demo/)
+## [Project Page](https://joxit.dev/docker-registry-ui) and [Live Demo](https://joxit.dev/docker-registry-ui/demo/)
 
 ![preview](https://raw.github.com/Joxit/docker-registry-ui/master/docker-registry-ui.gif "Preview of Docker Registry UI")
 
 ## Features
 
 -   List all your repositories/images.
--   List all tags for a repository/image
+-   List all tags for a image.
--   Sort the tag list
+-   Sort the tag list with number compatibility (see [#46](https://github.com/Joxit/docker-registry-ui/pull/46)).
--   One interface for many registries
+-   Use a secured docker registry.
--   Use a secured docker registry
+-   Display image size (see [#30](https://github.com/Joxit/docker-registry-ui/issues/30)).
--   Share your docker registry with query parameter `url` (e.g. `https://joxit.dev/docker-registry-ui/demo?url=https://registry.example.com`)
+-   Multi arch supports, Alpine and Debian based images with supports for arm32v7 and arm64v8.
--   Use `joxit/docker-registry-ui:static` as reverse proxy to your docker registry (This will avoid CORS).
+-   Copy `docker pull` command to clipboard (see [#42](https://github.com/Joxit/docker-registry-ui/issues/42)).
--   Display image size (see #30)
+-   Show sha256 for specific tag (hover image tag).
--   Add Title when using REGISTRY_URL (see #28)
+-   Display image creation date (see [#49](https://github.com/Joxit/docker-registry-ui/issues/49))
--   Alpine and Debian based images with supports for arm32v7 and arm64v8
+-   Display image history (see [#58](https://github.com/Joxit/docker-registry-ui/pull/58) & [#61](https://github.com/Joxit/docker-registry-ui/pull/61)).
--   Copy `docker pull` command to clipbloard
+-   Image aggregation (see [#56](https://github.com/Joxit/docker-registry-ui/issues/56)).
--   Show sha256 for specific tag (hover image tag)
+-   Display image/tag count (see [#56 issue comment](https://github.com/Joxit/docker-registry-ui/issues/56#issuecomment-449246524)).
--   Display image creation date (see #49)
+-   Select multiple tags to delete (see [#29](https://github.com/Joxit/docker-registry-ui/issues/29)).
--   Display image history (see #58)
+-   Select all tags with ALT + Click to delete (see [#80](https://github.com/Joxit/docker-registry-ui/issues/80)).
--   Display image/tag count
+-   One interface for many registries **standard interface**.
--   Image aggregation (see #56)
+-   Share your docker registry with query parameter `url` (e.g. `https://joxit.dev/docker-registry-ui/demo?url=https://registry.example.com`) **standard interface**.
--   Customise docker pull command on static registry UI (see #71)
+-   Use `joxit/docker-registry-ui:static` as reverse proxy (with `REGISTRY_URL` environment variable) to your docker registry (This will avoid CORS) **static interface**.
--   Multi-delete and multi-select shortcut (Alt+click) (see #29 and #80)
+-   Add Title when using `REGISTRY_URL` (see [#28](https://github.com/Joxit/docker-registry-ui/issues/28)) **static interface**.
+-   Customise docker pull command on static registry UI (see [#71](https://github.com/Joxit/docker-registry-ui/issues/71)) **static interface**.
 
 ## Getting Started
 
@@ -103,7 +112,7 @@ To run the docker and see the website on your 80 port, try this:
 docker run -d -p 80:80 joxit/docker-registry-ui
 ```
 
-#### Run the static docker
+#### Run the static interface
 
 Some env options are available for use this interface for only one server.
 
@@ -120,7 +129,7 @@ docker run -d -p 80:80 -e URL=http://127.0.0.1:5000 -e DELETE_IMAGES=true joxit/
 ```
 
 Example with `REGISTRY_URL`, this will add a proxy to your registry.
-Your registry will be accessible here : `http://127.0.0.1/v2`, this will avoid CORS errors (see #25).
+Your registry will be accessible here : `http://127.0.0.1/v2`, this will avoid CORS errors (see [#25](https://github.com/Joxit/docker-registry-ui/issues/25#issuecomment-360522487)).
 Be careful, `joxit/docker-registry-ui` and `registry:2` will communicate, both containers should be in the same network or use your private IP.
 
 ```sh

_config.yml

@@ -1,7 +1,13 @@
-title: Docker Registry v2 User Interface
+title: Docker Registry User Interface
+description: The simplest and most complete UI for your private registry!
 url: https://joxit.dev/docker-registry-ui
 google_analytics: UA-99119327-1
 theme: jekyll-theme-cayman
 author: Jones Magloire
 twitter:
   username: Joxit
+defaults:
+  - scope:
+      path: ""
+    values:
+      image: /screenshot.png

demo/index.html

@@ -24,15 +24,15 @@
   <link href="https://fonts.googleapis.com/css?family=Roboto:regular,bold,italic,thin,light,bolditalic,black,medium&amp;lang=en" rel="stylesheet" type="text/css">
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <meta property="og:locale" content="en_US" />
-  <meta name="description" content="This is the live demo for my project Docker Registry v2 web User Interface. Sources : https://github.com/Joxit/docker-registry-ui" />
+  <meta name="description" content="This is the live demo for Docker Registry User Interface. Try it now! Sources : https://github.com/Joxit/docker-registry-ui" />
-  <meta property="og:description" content="This is the live demo for my project Docker Registry v2 web User Interface. Sources : https://github.com/Joxit/docker-registry-ui" />
+  <meta property="og:description" content="This is the live demo for Docker Registry User Interface. Try it now! Sources : https://github.com/Joxit/docker-registry-ui" />
   <link rel="canonical" href="https://joxit.dev/docker-registry-ui/demo/" />
   <meta property="og:url" content="https://joxit.dev/docker-registry-ui/demo/" />
-  <meta property="og:site_name" content="Demo | Docker Registry UI" />
+  <meta property="og:site_name" content="Live Demo | Docker Registry User Interface" />
   <meta name="twitter:card" content="summary" />
   <meta name="twitter:site" content="@Joxit" />
   <meta name="twitter:creator" content="@Jones Magloire" />
-  <title>Demo | Docker Registry UI</title>
+  <title>Live Demo | Docker Registry User Interface</title>
 </head>
 
 <body>

examples/issue-75/README.md

@@ -2,6 +2,6 @@
 
 Run this command `docker-compose up -d`, then you can push your images (e.g localhost:5000/alpine).
 
-Be careful, the docker registry is using status codes 307 for each requests, that means you must configure your s3 to accept same requests as your private registry (that means `DELETE`, `Access-Control-Allow-Origin` and others).
+Be careful, the docker registry is using status codes 307 for each requests, that means you must configure your s3 to accept same requests as your private registry (that means `DELETE`, `Access-Control-Allow-Origin` and others). To avoid this, we need the option `storage.redirect.disable: true`, with this you will use your registry credentials (if you are using it).
 
 This s3 server allow all requests.

examples/issue-75/registry-config/config.yml

@@ -20,6 +20,8 @@ storage:
     v4auth: true
     chunksize: 5242880
     rootdirectory: /
+  redirect:
+    disable: true
 http:
   addr: 0.0.0.0:5000
   headers:

index.md

@@ -0,0 +1 @@
+README.md