The ability to exclude/ignore files used only for development would be a welcome addition. Giving the option to ignore items such as dot config files, node_modules, package.json, etc. A similar request is posted here, but I believe the feature should go further than just ignoring node_modules.
Thank you for the feature request @deadband !
A request for the ability to not push/pull uploads is asked here, and I believe this would also be a beneficial addition.
A syncing function within DevKinsta that worked more like rsync would be excellent, with the ability to ignore specific files/directories and only sync those with changes.
+10 to this. Ability to completely exclude whole directories, such as backups from wp-content/uploads, would be very welcome.
I approve this great idea!
Hello everyone, I’m just announcing that file/folder exclusion is now live in version 2.8.0: DevKinsta Releases (Minor) - #13 by Kevin
This is a UI to include/exclude files but as far as I know it isn’t powered by an ignore file or similiar which is what folks are asking for.
Would be lovely to see this hide ignored files (and would make the UI more responsive), with the option to view and add them if needed and ideally possibly remember selections from last time.
As it stands its a very manual process still and often my UI struggles to even render all the files.
My usecases are:
- Sync up user generated content from live - for this I don’t mind pulling down the whole database but I only want to pull down the uploads folder etc. rather than everything.
- Push changes up but not developer files or wordpress files
Hello @Pete_Duncanson
Since your posts in the 3 threads are in regards to the same issue, I suggest we continue the discussion here: How to properly deploy WordPress to Kinsta? - #3 by Pete_Duncanson
I’ll send my reply soon.
Kind regads