Prepare 0.7 release.

CHANGELOG.md

@@ -1,6 +1,6 @@
 ## Changelog
 
-### 0.7
+### 0.7 (2018-07-04)
 
 * When using MySQL for event storage, do not leak connections.
 * Last events were not shown when viewing a repo of non-default namespace.
@@ -9,12 +9,12 @@
 * Add `base_path` option to the config to run UI from non-root.
 * Add built-in cron feature for purging tags task.
 
-### 0.6
+### 0.6 (2018-05-28)
 
 * Add MySQL along with sqlite3 support as a registry events storage.
   New config settings `event_database_driver`, `event_database_location`.
 * Bump Go version and dependencies.
 
-### 0.5
+### 0.5 (2018-03-06)
 
 * Initial public version.

Dockerfile

@@ -12,7 +12,7 @@ RUN cd /opt/src/github.com/quiq/docker-registry-ui && \
 
 ADD events /opt/src/github.com/quiq/docker-registry-ui/events
 ADD registry /opt/src/github.com/quiq/docker-registry-ui/registry
-ADD main.go /opt/src/github.com/quiq/docker-registry-ui/
+ADD *.go /opt/src/github.com/quiq/docker-registry-ui/
 RUN cd /opt/src/github.com/quiq/docker-registry-ui && \
     go test -v ./registry && \
     go build -o /opt/docker-registry-ui github.com/quiq/docker-registry-ui

README.md

@@ -56,6 +56,7 @@ To receive events you need to configure Registry as follow:
             - application/octet-stream
 
 Adjust url and token as appropriate.
+If you are running UI from non-root base path, e.g. /ui, the URL path for above will be `/ui/api/events`.
 
 ## Using MySQL instead of sqlite3 for event listener
 
@@ -85,13 +86,13 @@ You can try to run in dry-run mode first to see what is going to be purged:
 
     docker exec -t registry-ui /opt/docker-registry-ui -purge-tags -dry-run
 
-Alternatively, you can schedule the purging task with built-in cron service.
+Alternatively, you can schedule the purging task with built-in cron feature:
 
-```config.yaml
-purge_tags_keep_days: 90
-purge_tags_keep_count: 2
-purge_tags_schedule: '10 3 * * *'
-```
+    purge_tags_keep_days: 90
+    purge_tags_keep_count: 2
+    purge_tags_schedule: '0 10 3 * * *'
+
+Note, the cron schedule format includes seconds! See https://godoc.org/github.com/robfig/cron
 
 ### Debug mode
 

config.yml

@@ -43,6 +43,8 @@ debug: true
 # How many days to keep tags but also keep the minimal count provided no matter how old.
 purge_tags_keep_days: 90
 purge_tags_keep_count: 2
-# Schedules to purge tags with cron format. (Only for server mode)
+# Enable built-in cron to schedule purging tags in server mode.
 # Empty string disables this feature.
+# Example: '25 54 17 * * *' will run it at 17:54:25 daily.
+# Note, the cron schedule format includes seconds! See https://godoc.org/github.com/robfig/cron
 purge_tags_schedule: ''