Why not ship with a .env file?

MSU-NatSci / DomainAccessibilityAudit

Web application to create domain and subdomain accessibility audits, with violation statistics.

GNU General Public License v3.0

48 stars 19 forks source link

Why not ship with a .env file? #8

Open mgifford opened 3 years ago

mgifford commented 3 years ago

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 commented 3 years ago

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.