I would have added this as a comment under the blog you linked to but think here might be better place for this conversation.
I’ve spent some time this morning trying to get this working but have hit a few hurdles and unknowns. Can you shed some light on these questions and blockers?
-
Once I pull down from Kinsta is it right that I can’t pull do a full sync again as it will just over-write everything including git folders. So this is in effect a one time deal. I know I can select which files/folders to pull down but would be lovely if that was initially from a ignore file or similar (with the option for me to over power that via the UI if needed) see Ability to Ignore Development Files From Syncing - #6 by Kevin
-
I have both a live and staging environment and would like these to update when I push to main or staging respectively. I’m happy to create two Github actions for this from the script provided and two lots of git hub secrets too however I hit a blocker with the SSH key step on the server. Both my environments already have a SSH key and its the same key between them. I don’t want to change it or overwrite is as I’m not sure if its used internally for Kinsta stuff at all. Can I use the same key for both environments? Or do I need to create a unique one per environment?
-
How can I sync up uploaded files etc from live using this setup? Would I use the DevKinsta UI as mentioned in my first point?
Cheers
Pete