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

Mark the compose/.env file so it won't overwrite an existing file #24

Open
dajtxx opened this issue Feb 6, 2023 · 0 comments
Open

Mark the compose/.env file so it won't overwrite an existing file #24

dajtxx opened this issue Feb 6, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@dajtxx
Copy link
Collaborator

dajtxx commented Feb 6, 2023

The reason the .env file was not in the repo was so it wouldn't overwrite the local copy in an installation, losing usernames and passwords.

In the effort to make IoTa work 'out of the box' this was changed so the .env file became a runnable default.

This is too dangerous for production use so see if there is another way to work around this. Probably modifying run.sh to check for the file and copy it from config if it doesn't exist is the easiest way.

@dajtxx dajtxx self-assigned this Feb 15, 2023
@dajtxx dajtxx added the bug Something isn't working label Feb 15, 2023
dajtxx pushed a commit that referenced this issue Oct 31, 2023
…toring_mqtt_refactor

Feature/monitoring mqtt refactor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant