Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: Add a minimal yaml file for use with production.py #31366

Merged
merged 1 commit into from
Nov 29, 2022
Merged

feat: Add a minimal yaml file for use with production.py #31366

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions lms/envs/minimal.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# WARNING: Experimental
#
# This is the minimal settings you need to set to be able to get django to
# load when using the production.py settings files. It's useful to point
# LMS_CFG and CMS_CFG to this file to be able to run various paver commands
# without needing a full docker setup.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you link a followup ticket here, like this one? I feel better about checking in experimental code when I know it'll be easy for someone in the future to check up on whether the code can be either polished or removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I linked to the same ticket for now(https://github.com/openedx/wg-developer-experience/issues/136).

#
# Follow up work will likely be done as a part of
# https://github.com/openedx/wg-developer-experience/issues/136
---

SECRET_KEY: aseuothsaeotuhaseotisaotenihsaoetih
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is clearly a Dvorak keymash. I think we should keep that kind of pretension out of the codebase.

FEATURES:
PREVIEW_LMS_BASE: "http://localhost"
TRACKING_BACKENDS: {}
EVENT_TRACKING_BACKENDS: {}
JWT_AUTH: {}
CELERY_QUEUES: {}
MKTG_URL_LINK_MAP: {}
MKTG_URL_OVERRIDES: {}
REST_FRAMEWORK: {}

# For just the CMS
LMS_ROOT_URL: "http://localhost"
LMS_INTERNAL_ROOT_URL: "http://localhost"