I’ve run into a major pain point when it comes to using connect and Git.
I set up Git in my theme folder on Local. Which creates the .git folder
I push my site to Flywheel which then ignores the .git which is ok, I see no reason to have git live on flywheel.
Pain Point: my node_modules folder gets uploaded to flywheel, which sucks since it’s huge and I really only need it while developing locally. anyway to ignore this? .localignore ?
Pain Point : When I need to pull the site from flywheel it overides all the files…including my .git…so bye bye git, and come the anoying process of having to clone again from origin.
Possible solution: have a way to not override local .git folder? even if the flywheel copy ends up changing my files…if I have my local git folder then i can always ignore the changes that the download caused.
I would also love a way to tell local to ignore directories and not just files. I am having the same issue with my node_modules being pushed to the flywheel / live environment.
This not only uses up space on the hosting it also slows the transfer process.
We’re prioritizing the .git folder issue in an upcoming update.
Regarding node_modules (and other files/folders to ignore), we’re currently working on the flow for this and hope to have a solution soon after the .git issue is addressed
As a very iffy but working fix in the meantime, if you move your node_modules to the app directory it won’t push it, and you should still be able to use a lot of utilities.
Again, use this extremely iffy fix at your own caution. There’s lot of things that could go wrong. However, my gulp build works just fine like this as long as I’m not installing any more modules.
Hi @clay
I am using Local version 2.1.2 and am still experiencing issues with git. When pulling down from the Flywheel site to my Local it overrides the git folder. Is there anyway around this?
+1 for ignoring node_modules in theme. I also have a bower_components that I’d like to ignore.
@clay what would be the possibility of a .ignore file similar to git or even deployHQ?
This would allow users to specify any files in their theme, or even plugins that they didn’t want pushed live.
Looks like node_modules is now ignored, I’m in a case where I would like it to not be ignored. Is this possible?
I push and pull and it would be great to have everything synced even if on the prod server the files are just taking up space. I’m open to suggestions for sure.
This is not the expected behavior. I just tested this on macOS and Windows and it worked properly on macOS (preserved the .git directory) but did not on Windows.
I’ve written up an issue in our tracker so we can get this resolved. Sorry for the trouble!
