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

Add interactive helper for setting up a .env file for staff #3810

Closed
larsyencken opened this issue Jul 24, 2024 · 2 comments
Closed

Add interactive helper for setting up a .env file for staff #3810

larsyencken opened this issue Jul 24, 2024 · 2 comments
Labels
ops Devops related issues (stagings servers, ...)

Comments

@larsyencken
Copy link
Contributor

Context

To run the full owid-grapher codebase for a site, you run make up.full. That copies .env.example-full to .env, and starts the services.

However, there are many non-optional environment variables needed to set up the environment.

Problem

It's not clear where to get those variables from (as in, not documented), and not smooth to fill them in one by one.

Proposal

Add an interactive helper that helps you add one by one the missing environment variables that are not marked optional, until you have all you need to spin up the local server successfully.

@toni-sharpe
Copy link
Contributor

toni-sharpe commented Aug 23, 2024

Question it sounds like "staff" could also be "open-source contributors" - is this correct? Maybe we need a distinction, or to be careful with language/definitions with the vision to have a full open-source project?

@larsyencken
Copy link
Contributor Author

H

Question it sounds like "staff" could also be "open-source contributors" - is this correct? Maybe we need a distinction, or to be careful with language/definitions with the vision to have a full open-source project?

"staff" means folk that work at OWID. The make up.full recipe is one that only staff can run, since it needs a bunch of credentials that make up doesn't.

@larsyencken larsyencken removed their assignment Oct 18, 2024
@larsyencken larsyencken closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ops Devops related issues (stagings servers, ...)
Projects
None yet
Development

No branches or pull requests

4 participants