distribution/cmd/registry/config.yml

version: 0.1
log:
  level: debug
storage:
    filesystem:
        rootdirectory: /tmp/registry-dev
http:
    addr: :5000
    secret: asecretforlocaldevelopment
    debug:
        addr: localhost:5001
notifications:
    endpoints:
        - name: local-8082
          url: http://localhost:5003/callback
          headers:
             Authorization: [Bearer <an example token>]
          timeout: 1s
          threshold: 10
          backoff: 1s
          disabled: true
        - name: local-8083
          url: http://localhost:8083/callback
          timeout: 1s
          threshold: 10
          backoff: 1s
          disabled: true
Add registry main cmd 2014-12-02 02:36:20 +01:00			`version: 0.1`
Allow logging formatter to be configured This changeset simply adds hooks into the configuration system to support multiple different kinds of output formats. These formatters are provided by logrus and include options such as "text" and "json". The configuraiton documentation has been updated accordingly. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-03-24 04:13:35 +01:00			`log:`
			`level: debug`
Use filesystem driver in default configuration 2014-12-15 20:53:52 +01:00			`storage:`
			`filesystem:`
			`rootdirectory: /tmp/registry-dev`
Add registry main cmd 2014-12-02 02:36:20 +01:00			`http:`
Fix address 2014-12-11 02:59:13 +01:00			`addr: :5000`
Add debug server to support pprof and expvar If configured, a debug http server will be started to serve default registered endpoints, such as pprof and expvar. The endpoint should be secured carefully and not available to external traffic. It is disabled by default but the development config has been modified to make it available on localhost. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-01-29 00:45:25 +01:00			`secret: asecretforlocaldevelopment`
			`debug:`
			`addr: localhost:5001`
Webhook notification support in registry webapp Endpoints are now created at applications startup time, using notification configuration. The instances are then added to a Broadcaster instance, which becomes the main event sink for the application. At request time, an event bridge is configured to listen to repository method calls. The actor and source of the eventBridge are created from the requeest context and application, respectively. The result is notifications are dispatched with calls to the context's Repository instance and are queued to each endpoint via the broadcaster. This commit also adds the concept of a RequestID and App.InstanceID. The request id uniquely identifies each request and the InstanceID uniquely identifies a run of the registry. These identifiers can be used in the future to correlate log messages with generated events to support rich debugging. The fields of the app were slightly reorganized for clarity and a few horrid util functions have been removed. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-01-29 00:55:18 +01:00			`notifications:`
			`endpoints:`
			`- name: local-8082`
			`url: http://localhost:5003/callback`
			`headers:`
			`Authorization: [Bearer <an example token>]`
			`timeout: 1s`
			`threshold: 10`
			`backoff: 1s`
			`disabled: true`
			`- name: local-8083`
			`url: http://localhost:8083/callback`
			`timeout: 1s`
			`threshold: 10`
			`backoff: 1s`
			`disabled: true`