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

Why not ship with a .env file? #8

Open
mgifford opened this issue Jan 18, 2021 · 1 comment
Open

Why not ship with a .env file? #8

mgifford opened this issue Jan 18, 2021 · 1 comment

Comments

@mgifford
Copy link

I'm having trouble logging in after Docker is installed. I didn't create the .env first. I've tried removing & re-installing this, but it doesn't seem to be working.

I'll keep trying, but wanting to know why the .env isn't just shipped with a admin/admin type of u/p. Yes, this would be bad if it were a public site, but most won't be at first. And we can put many warnings into the README so folks are reminded to change the password.

@mgifford
Copy link
Author

Also, worth noting that it seems to work with the quotes in the .env:

ADMIN_USERNAME='admin'
ADMIN_PASSWORD='password'

Or possibly by nixing the volumes docker-compose down --volumes

Anyways, would be good to enhance the README to make this easier to work by default.

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