Skip to content

Organizational Decisions to Make #223

@wesleyboar

Description

@wesleyboar

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions