-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the latest django-docker #2172
Changes from 4 commits
8960555
33c1e19
a077480
57b7fda
f9b9bee
363b515
d46a91b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -658,7 +658,8 @@ def get_setting(name, settings=local_settings, default=None): | |
# Time in seconds to wait before killing unused visualization | ||
DJANGO_DOCKER_ENGINE_SECONDS_INACTIVE = 60 * 60 | ||
# Location of DjangoDockerEngine proxy logging | ||
PROXY_LOG = '/tmp/django_docker_engine.log' | ||
DJANGO_DOCKER_ENGINE_DATA_DIR = '/data/django-docker-engine-data' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is where docker instances will have mounted volumes for their inputs and ephemeral storage needs. The path is accessed by docker-engine: If docker-engine is running on a separate instance, it will be a directory on that instance. If we can use ECS, then this may be moot. But it needs to be somewhere for now, and this is better than having it hard-coded to a path on the root volume. Using On vagrant, do you have a strong preference about whether we create a There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK then it's fine to use It's probably a good idea to add Finally, it'd be great to consolidate all storage related Puppet resources into one module (similar to python.pp for example). |
||
PROXY_LOG = '/data/django-docker-engine.log' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's probably best to follow standard Django logging practices instead of restricting logging to just a file. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point: I think there was some reason initially why it didn't fit, but I can't recall it now, and I'm not sure the reason would be valid even if I could. refinery-platform/django_docker_engine#80 |
||
|
||
REFINERY_DEPLOYMENT_PLATFORM = "vagrant" | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be combined into a separate module along with storage related items in aws.pp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hackdna Are you saying create a
storage.pp
?Would this be better suited for an issue outside of this pr?
Just seeing this comment: #2172 (comment) if you want to checkout this branch and make the
storage.pp
file that would be really helpful.