Explicitely tell where the .env file should be created #60

Merged
elegaanz merged 1 commit from plume/documentation:dot-env-location into dev 2019-10-30 14:17:20 +00:00
elegaanz commented 2019-08-09 10:27:22 +00:00 (Migrated from github.com)

It was not clear to someone.

It was not clear to someone.

maybe we should provide a .env.example in the repo, and ask peoples to cp it, and modify things? That way it's position will probably be more clear

maybe we should provide a .env.example in the repo, and ask peoples to cp it, and modify things? That way it's position will probably be more clear
elegaanz commented 2019-08-09 14:10:05 +00:00 (Migrated from github.com)

We should also consider the case where people don't clone the repo but use prebuilt binaries, but yes.

We should also consider the case where people don't clone the repo but use prebuilt binaries, but yes.
trinity-1686a approved these changes 2019-10-30 11:51:22 +00:00
trinity-1686a left a comment
Owner

I still think we should have a .env.example filled with all supported env vars (commented out for most), but this is for another repository

I still think we should have a .env.example filled with all supported env vars (commented out for most), but this is for another repository
Sign in to join this conversation.
No description provided.