torpid arrow
Hey all,
Just wondering if there’s a good guide on setting up an existing deployed appsmith app locally for development.
We have a GitHub repo for the app and I’m curious if there’s a good workflow for serving it locally to check changes before pulling from the actual deployed instance.
Thanks in advance!
I should say that I want to do this so that we can check interactions with an api that I’m also serving locally
hard elmBOT
Hi there!
Welcome to Appsmith Support.
You can export the app from your server and import it into your local setup.
You can create a separate branch for the local copy in your repository (e.g.
dev) and keep the production app connected to your main branch (e.g. master).
This way, changes made locally can be committed to Git and pulled into your
Master environment once everything is working fine.
Let us know if you have further questions.
torpid arrow
Thank you! Just one more question — I’m wondering if there’s a good way to separate API IP addresses in main and dev — I was thinking a gitignore file could be useful but I can’t figure out where those are stored and don’t necessarily want to change them on every merge
torpid arrow
I guess a better question would be — is there any way to read environment variables into appsmith for use as the api IP
hard elmBOT
Datasources are workspace scoped. You can accomplish this by having two
workspaces. You will have a datasource with the same name but different
credentials in both workspaces. You can use Git to develop in one workspace,
commit the changes, and pull them to a production workspace. The queries should
continue to function as expected.
torpid arrow
I see — didn’t realize you could save an API IP as a data source. Thank you!