Tutorial/Tool on working with different environments (DEV, TEST, PROD...) to achieve Continuous Deployment
I would like to have a tutorial/tool explaining/enabling how to work with different environments (DEV, TEST, PROD...), so that I can set an automated pipeline for CD.
Carlos Gines
shared this idea
-
AdminSumedha Mehta
(Admin, MongoDB)
commented
Hi all - we have made some improvements in this space and have also released another tutorial video for this. Feel free to leave additional feedback in the forum or here on the tool!
https://www.youtube.com/watch?v=-JcEa1snwVQ&t=1110s&ab_channel=MongoDB
-
Fatimah Sanni
commented
Hi @lauren, I noticed something with your code, there were no ids in your config.json, how did you do that? That's the blocker for us, everything with a config.json has an id unique to it, so what that means is that for the different environments, you have different ids and that's weird for git versioning.
Anytime we create a new function and imported, the id is automatically generated and added to the config.json. Thanks
-
Lauren
commented
Hi, Carlos,
Thanks for the feedback! I discussed this topic at MongoDB.live in June. You may find the recording helpful: https://www.youtube.com/watch?v=RlouET0cPsc. My GitHub repo has a detailed readme with explanations of how I configured everything including Travis CI: https://github.com/mongodb-developer/SocialStats
I'm working on converting this talk to a blog series that will be released on the DevHub (https://developer.mongodb.com) over the next few months.