container/greenwave
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The greenwave package
4 commits 7 branches 0 tags 39 KiB
  • Dockerfile 100%
Find a file
Ralph Bean e29f931fb6 Include the fedmsg-hub process. 
Do this so that people can override the default ENTRYPOINT to use the
same container image to run the greenwave backend software.  See

- https://pagure.io/greenwave/pull-request/51
- https://pagure.io/greenwave/pull-request/86
2017-09-23 09:53:52 -04:00
Dockerfile Include the fedmsg-hub process. 2017-09-23 09:53:52 -04:00
README.md Initial commit (#1483358). 2017-08-23 11:56:53 -04:00

README.md

% GREENWAVE (1) Container Image Pages % Matt Jia mjia@redhat.com % Aug 2017

NAME

Greenwave - Service for making decisions based on test results

DESCRIPTION

This container provides the Greenwave web application only. The application is stateless and does not require any volumes.

USAGE

Create a directory or Docker volume to hold configuration for the Greenwave service. This volume should be mounted as /etc/greenwave inside the container. It must contain one file, settings.py. You can find an example configuration in /usr/share/doc/greenwave/conf/settings.py.example or view it online.

The default container entrypoint starts the web application on port 8080.

docker run -p 8080:8080 -v greenwave-config:/etc/greenwave:ro greenwave

ENVIRONMENT VARIABLES

FLASK_SECRET_KEY= Secret key used for various cryptographic purposes within the Flask framework. This value must be unique per deployment, and not disclosed to anyone. If this is set, it overrides any value provided in the SECRET_KEY setting in /etc/greenwave/settings.py.

SEE ALSO

Greenwave project
Greenwave documentation