Hi, I suggest to change database credential in .env file or in heroku you can use ENV that heroku already provided it.
To make sure for secret things never in commit. To make sure another people also not doing commit credential in they code (especially for open source code).
That's a great input! Thanks for the suggestion 😊 Tho the .env is often indicated in the .gitignore file (Yet it'll be nice to include that in the article regardless) So, I guess I'll check the env provided by Heroku
Hi, I suggest to change database credential in .env file or in heroku you can use ENV that heroku already provided it.
To make sure for secret things never in commit. To make sure another people also not doing commit credential in they code (especially for open source code).
Just for suggestion. :D
Btw, great content!
That's a great input! Thanks for the suggestion 😊 Tho the .env is often indicated in the .gitignore file (Yet it'll be nice to include that in the article regardless) So, I guess I'll check the env provided by Heroku
Yes, .env usually in .gitignore, my focus here to make anyone aware about their credential in their code. 😀
Ow I see 🤔 If you put it that way, then I'll add those steps regarding Heroku Config Vars. Thanks again for your suggestion!