Dev/Prod envs using 2 instances (Community Edition)
Would I encounter any issues if I have 2 GitHub branches:
- dev
- master
and use
wmill sync push in a GitHub Action [with 2 different domains / tokens]?7 Replies
I don't think so
one thing I considered is that the resources must match up and if I add multiple in production (e.g. if I have a schedule for a flow that operates on multiple resources of a given resource type), this will cause a slight drift
unless there's a way to NOT pull resources
that's what git sync is for
(which is EE)
what's the difference between pulling with the --stateful flag and without it
--stateful is super obsolete, we will probably remove it in not too long
you should use git sync (which is EE)
you can use CLI push and pull but it's non stateful and it will overwrite everything
it can only work without drift, and drift can only work if windmill updates your git repo on any changes, which is what git sync is for
so you can do some automation without git sync
but the complexity is not worth imho
i see
Update: I think I can utilize variables / secrets (which I won't pull using sync) for the dynamic values inside each resource, e.g. db host / pass / etc
Yes that's recommended