How to exclude development files from push/pull to/from Flywheel sites?

[earthmanmedia]

Issue Summary

How am I able to exclude files from being pushed to Flywheel server

Rationale: Pushing files and folders to the www root may result in unexpected permission changes on Flywheel

Troubleshooting Questions

Use cases for excluding files from push/pull to/from Flywheel sites:

• excluding custom media folders
• excluding specific vendor folders, node_module, and source files only used in development
• excluding cache files, and other plugin artifacts that are specific to each environment

In the docs, these are the closest I could find to a working model, but they relate to wp-engine:

Change Local Connect Exclude Files

According to the documentation for Local Connect there is a list of excluded files that will NOT be pulled from WP Engine when you pull a site. Unfortunately .github/workflows/workflow-file.yml is not in this path list so when I pull from WPE via Local Connect it deletes my github automated deployment to WPE. Is there a way to add items to this list so they get ignored when you pull a site?

How to ignore certain folders from pull and push in WPEngine?

I dont want certain folders to be pulled or pushed from WP Engine Is there any way we can exclude certain folders from being pulled or pushed? something like gitignore where it ignores the files/folders when pushing to GitHub

Here are some other threads that are related, but they appear unresolved/ignored:

Ignore Media Files on Push & Pull

Love the checkbox that allows me to ignore DB on push. Would love something similar for media My clients seem to really hate me and always upload lots of video and images. pushing and pulling gigs of data is not my idea of a fun time.

Ignore node_modules when pushing to server

Is there a way to ignore the node_modules folder when pushing a site from local to wpengine?

Replication

I have submitted support tickets / chats to Flywheel due to the unexpected changing of ownership after files are pushed using localwp - they end up somehow as owned by root:root making them inaccessible. This has happened a few times.

System Details

• All versions

[ben.turner]

Right now there isn’t a way to globally ignore files or folders. I think the closest thing is to use the Magic Sync viewer to un select the files that you don’t want to deploy.

I can see how that would become annoying if you never want to deploy the .github or node_modules folders. Probably the best thing to do would be to create a feature request along the lines of allowing users to specify files and folders that should be ignored when using Local Connect.