distribution/cmd/registry/config.yml

version: 0.1
log:
  level: debug
  fields:
    service: registry
    environment: development
storage:
    cache:
        layerinfo: inmemory
    filesystem:
        rootdirectory: /tmp/registry-dev
    maintenance:
        uploadpurging:
            enabled: false
http:
    addr: :5000
    secret: asecretforlocaldevelopment
    debug:
        addr: localhost:5001
redis:
  addr: localhost:6379
  pool:
    maxidle: 16
    maxactive: 64
    idletimeout: 300s
  dialtimeout: 10ms
  readtimeout: 10ms
  writetimeout: 10ms
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`
Add support for configuration static logging fields To allow flexibility in log message context information, this changeset provides the ability to configure static fields that are included in the context. Such fields can be set via configuration or environment variables. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-03-25 01:12:04 +01:00			`fields:`
			`service: registry`
			`environment: development`
Use filesystem driver in default configuration 2014-12-15 20:53:52 +01:00			`storage:`
Allow control over which storage cache to use This allows one to better control the usage of the cache and turn it off completely. The storage configuration module was modified to allow parameters to be passed to just the storage implementation, rather than to the driver. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-04-03 01:38:01 +02:00			`cache:`
			`layerinfo: inmemory`
Use filesystem driver in default configuration 2014-12-15 20:53:52 +01:00			`filesystem:`
			`rootdirectory: /tmp/registry-dev`
Add configuration for upload purging Signed-off-by: Richard Scothern <richard.scothern@gmail.com> 2015-04-17 03:34:29 +02:00			`maintenance:`
			`uploadpurging:`
			`enabled: false`
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`
Add redis pool to registry webapp Redis has been integrated with the web application for use with various services. The configuraiton exposes connection details, timeouts and pool parameters. Documentation has been updated accordingly. A few convenience methods have been added to the context package to get loggers with certain fields, exposing some missing functionality from logrus. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-04-02 01:27:24 +02:00			`redis:`
			`addr: localhost:6379`
			`pool:`
			`maxidle: 16`
			`maxactive: 64`
			`idletimeout: 300s`
			`dialtimeout: 10ms`
			`readtimeout: 10ms`
			`writetimeout: 10ms`
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`
Add configuration for upload purging Signed-off-by: Richard Scothern <richard.scothern@gmail.com> 2015-04-17 03:34:29 +02:00