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

Organizational Decisions to Make #223

Open
wesleyboar opened this issue Sep 1, 2023 · 0 comments
Open

Organizational Decisions to Make #223

wesleyboar opened this issue Sep 1, 2023 · 0 comments

Comments

@wesleyboar
Copy link
Member

Overview

There are some organizational decisions to make (source).

To Decide

Should CMS_TEMPLATES be Defined in This Repo for Every Project?

Ideas:

  • flat overwrite Core-CMS and duplicate defaults (has duplication)
  • load from Core-CMS and append to defaults as needed (no duplication)

How to Best Warn Developers Not to Put EMAIL Settings in This Repo?

The EMAIL… settings should be set on server.". Currently, there are commented fake EMAIL settings in settings_custom.py that warn developers and link to that document.

Distinguish Which CMS Settings are For https://github.com/TACC/Core-CMS-Custom And https://github.com/TACC/Core-Portal-Deployments

I think Core-CMS-Custom CMS settings are those expected by default for local testing (most), and Core-Portal-Deployments CMS settings are anything else (few).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant