Guidance on multiple environment deployment and pushing changes to Github repo

Plasmic Studio Questions
1

Hi! I’m a beginner to Plasmic and recently started my first project straight from the Plasmic Studio. I set up a Github repo and Vercel deployment when I first started, and both worked for my first published version (i.e., I was able to see in the vercel domains and a local server through VS Code exactly what I saw in Plasmic Studio).

However, before publishing another set of changes for production, I tried to deploy them using a “test” environment (as per this article) to see the changes first in a production-like environment without actually pushing them to Github. It looked good but when I tried re-publishing with “Push to Github” checked and the tag set to “prod”, no changes were pushed to Github. In addition, I was only able to see changes to my all my vercel deployment domains only until half a day later. I’m wondering whether it just takes some time to see changes in both Github and Vercel or am I doing something wrong? And how do I properly push changes to Github when trying to work with multiple environments?

Would greatly appreciate the help on this :slight_smile:

Relevant links:

2

Hello @zach.berk and welcome to the forum!

When configuring the Push To Github action, did you set the mode to Loader or Codegen?

The article you linked is for the Loader use case, where no Plasmic-generated code is checked into your git repo. So if that’s the mode you selected, then the Push To Github action will only create a new repo for you which is not updated on subsequent publishes.

The repo is only updated if the mode is Codegen. Read more about it in the Github actions doc here.

For automation and deployments in the loader use case, you can setup webhooks to trigger re-deploys. Read more about it in the Automation and deployment docs

1 Like