Skip to main content

Hi there,


Quick question on the app lifecycle. If I have an app that’s running live on monday code and I want to make incremental changes that I want to test locally, what’s the recommended approach?


I can think of two options:



  • create a new feature and depending on the case, replicate the functionality from the live feature, test it, and when ready push to monday code

  • create a different app to test locally, and once ready merge the changes with the live app and push to monday code


I’d like to hear if folks have other suggestions too! Thanks so much!

Hi @razme,


This question is better suited for the apps & developers category of the community, so just FYI, I changed the post category to move it there!


Best,

Rachel

Thanks so much!

I’d say that it’s best practice to have separate versions of apps on separate instances e.g. at:



That way, if anything bad happening in development, you can dispose of yourcompany-develop.monday.com and create a new instance.


Examples of things “going bad”



  • accidentally switching on multi-region monday-code when you’re not ready yet (theres no way back) – I know people with this problem

  • accidentally releasing a feature which is not ready – there are likely a few people who have don this – I’ve seen it when trying out other people’s apps


I’d then migrate the features from the app on your develop env to staging to check that everything works nicely in a “live” environment. If you’re happy, move it over to your production environment and release it there.


When mdc release their app manifest, it will make things a lot easier to copy apps from one account/instance to another, but in the meantime theres a lot of manual work to achieve the setup described above.

Reply


Terms & ConditionsCookie settings