prime
prime copied to clipboard
Documentation Clarification
Is it possible to update the documentation with more detail for getting started? For example, it says to modify the ".env" file but doesn't list where it is and a file search for "*.env" returns nothing. The only one that seems to be present is /usr/lib/node_modules/@primecms/cli/template/_.env on CentOS7 which has jinja2 syntax for the database but doesn't seem to affect anything when changed and the app still connects to 127.0.0.1 instead of the actual DB.
Yes, clearly the documentation needs much more work. I would also propose to add documentation for the environmental variables that are supported for configuration; I was unable to get my prime, hosted not on localhost working, until I discovered the CORE_URL
environmental variable. Otherwise, this is a very interesting project, and I would be willing to help in documentation.
@mbailey-eh In case you haven't solved your original issue yet, the .env
file is literally .env
, with nothing in the beginning (i.e. a hidden file), which explains why *.env
won't return anything.