How to properly deploy WordPress to Kinsta?

Hello @Pete_Duncanson :wave:

I would like to answer each point you made separately.

  • The Kinsta pull is not the same as GitHub deployment cycle, therefore, .gitignore wouldn’t work in that case, you would have to manually select what you are pulling down from Kinsta.

  • As long as you’re setting the correct SSH port for Kinsta environments (the ports will be different) you shouldn’t have an issue using the existing key and you don’t have to generate a new one

  • GitHub actions might not be the best solutions for syncing upload files, because CI/CD is aimed towards continuous development of code, not the files/content

Based on your use cases described in this thread, using DevKinsta granular push/pull is still the only option from DevKinsta. You could also try rsync however, that would have to be done via SSH and it’s not a part of Kinsta interface.

I’m not sure what is the exact content that you need to pull down and then push back to live and staging servers and why do you need them locally (what actions are done on these files and/or database tables) so feel free to reply and if we have any workflow that would be compatible with DevKinsta, we would be happy to recommend it.

Kind regards

1 Like