The sample.env file is not used by any system, and should only be used to help other devs understand what environment variables might be needed for an app.
The sample.env file is publicly visible on Replit. So, any secrets (DB passwords) kept in there can be easily taken, leaving your Database in jeopardy. It could end up costing you money, or, worse, lead you to be liable for illegal activity on your database account, if you do not remove visible access to your URI
.env files should be used for secrets. Or, if you have specifically set the configurations to, another plain text file name can be used.
On Replit, the SECRETS tab on the left nav is equivalent to a .env file, and you should use this for environment variables.
Otherwise, it is most likely the console/terminal will have helpful errors/warnings I suggest you spend some time getting used to, and searching for results.
Unfortunately the new secret left tab is not yet available to all users.Replit says its is still neing rolled out to users and may take some time. Until then, I guess, I will put a hold on these assignments!
Ah. Well, sorry about that. Is there not any way to opt in to the update? It sounds bizarre that you would not be able to create any environment variables.
I just got this new feature available for my replit. for the mongodb password do i store the password as PW in the key and my password value in the value tab without any equal to sign?
And the SESSION_SECRET in the key tab and its value in the value tab? with or without quotes?
cannot see any examples on google for this new feature…