Closed
Bug 1050859
Opened 10 years ago
Closed 10 years ago
Template marketplace-docker fig.yml
Categories
(Marketplace Graveyard :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jlockhart, Assigned: andy+bugzilla)
References
Details
The Wharfie project uses a YAML config file to tell fig how to orchestrate the services for the marketplace, but we need this to be templatable so that devs can add additional settings specific to their needs, for example add additional environment parameters to python/django services like Zamboni, Webpay, Solitude.
I envisage this working at runtime so assuming wharfie is the command you'd run something like:
'wharfie up'
This would build a fig.yml from a config and then run 'fig up' with it.
Likely things to template:
* Location of trees (this impacts volume sharing too so we'll need to bear that in mind.)
* Dev env hostname.
* Whether services are enabled or not.
* Env vars (as stated above).
I'd expect anything that's an env var should override anything in the dockerfile if it's defined in the fig.yml (This theory need testing).
Assignee | ||
Updated•10 years ago
|
Priority: -- → P4
Summary: Template Wharfie Fig YAML → Template Wharfie fig.yml and nginx.conf
Making the nginx.conf a separate bug as andym has already started work on the fig.yml side.
Assignee: scolville → amckay
Summary: Template Wharfie fig.yml and nginx.conf → Template Wharfie fig.yml
Summary: Template Wharfie fig.yml → Template marketplace-docker fig.yml
Assignee | ||
Comment 4•10 years ago
|
||
It is templated now, but I don't think I've seen anyone need anything more yet. If there's specific use cases lets file bugs for those.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•