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

Stop deployment if .env file was manually edited (offer portal-setup-following) #296

Open
firyx opened this issue Apr 27, 2022 · 0 comments

Comments

@firyx
Copy link
Collaborator

firyx commented Apr 27, 2022

OK. If this is our preferred approach then feel free to resolve this.

I still feel that this extra step is somehow unnecessary and many people will forget it and it will lead to a lot of frustration.

Is it possible to add a start-up step that does the following:

  1. Compare the current content of .env to a backed up copy created during the last successful run of portal-setup-following (ignoring empty lines and trailing whitespace).
  2. If the content differs, automatically re-run portal-setup-following.

This would be a great QoL improvement for portal operators.

Originally posted by @ro-tex in #291 (comment)

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