How to properly deploy with DevKinsta

Hi,

On DevKinsta I see the “Sync” button. But I didn’t find a detailed explanation about how to use it and what the implications are.

If I choose to sync “Files”, what files does it mean?

I need to be able to develop locally (update the theme and plugins, test it all out) and then push my changes. But I don’t want to push test files like media uploads.

Ideally, I need to be able to push only Core, Plugin and Theme files.

Is there some sort of config file where I can set what files are going to be synced or not (like a .gitignore)?

Also, is there any post-deployment scripts I can run on Kinsta, like webpack compilation, or does it need to happen locally before syncing final files?

Hi @alvarofranz :wave:

Welcome to the Kinsta Community!

When pushing a local site from DevKinsta to Kinsta (staging), you can selectively choose which specific files or folders to transfer. Under the Sync (Push to Kinsta) Settings, you’ll find the option to check the items you want to push from DevKinsta to Kinsta. In the sample screenshot below, you can see that I selected only the readme.html file and the wp-admin folder directory to be pushed to the Kinsta server.

I hope this information is helpful.

Thanks. This could do the job but it’s very manual.

A tool claiming to be useful for developers should have some sort of benefits over just using a vanilla FTP client.

Is there really no way to exclude files and folders so I don’t have to manually select everything every time I want to deploy?

Maybe DevKinsta is just not the right tool for this.

Thanks for helping!

Hello @alvarofranz :wave:

I have responded in your new thread in regards to this. You can use GitHub Actions to achieve this with DevKinsta and Kinsta-hosted sites.

You can find my message here: How to properly deploy WordPress to Kinsta? - #2 by VladimirM