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.

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

Radically simplify envs/ #34445

Closed
kdmccormick opened this issue Jun 2, 2022 · 0 comments
Closed

Radically simplify envs/ #34445

kdmccormick opened this issue Jun 2, 2022 · 0 comments
Labels
code health Proactive technical investment via refactorings, removals, etc. duplicate This issue or pull request already exists elsewhere

Comments

@kdmccormick
Copy link
Member

kdmccormick commented Jun 2, 2022

Dupe of #34446


random thoughts:

  • envs/common should provide prod-ready defaults for as many settings as possible, which distributions like Tutor should feel comfortable using as a starting point
  • envs/production is 2U-specific now since Tutor doesn't use it
  • envs/devstack will become 2U-specific once the community drops devstack
  • envs/bock_choy can be killed
  • OEP-45's recommendation that "yaml should be used for all overrides" is unrealistic and seems to be an over-engineered way of eschewing Django's own configuration system.
@kdmccormick kdmccormick added the code health Proactive technical investment via refactorings, removals, etc. label Jun 2, 2023
@kdmccormick kdmccormick changed the title Upstream envs: simplify common.py and DEPR production.py, etc? Radically simplify envs/ Mar 28, 2024
@kdmccormick kdmccormick transferred this issue from openedx-unsupported/wg-developer-experience Mar 28, 2024
@kdmccormick kdmccormick added the duplicate This issue or pull request already exists elsewhere label Mar 28, 2024
@kdmccormick kdmccormick closed this as not planned Won't fix, can't repro, duplicate, stale Mar 28, 2024
@github-project-automation github-project-automation bot moved this to Done in Arch-BOM Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Proactive technical investment via refactorings, removals, etc. duplicate This issue or pull request already exists elsewhere
Projects
No open projects
Development

No branches or pull requests

1 participant