Excluded Project Directories Being Deployed
I must be misunderstanding how the "Directories" management feature works, but could someone please shed some light on this for me? I couldn't find enough information in the documentation.
Here's what my understanding of this system is:
- You go to Settings -> Project -> Directories
- You mark any directories that should have NO actions (deployment being one of them) apply to them. IE, "in project libraries" (like node modules, or sass caches).
- If you do things (like deploy the project to a web server), these directories marked as "Excluded" should NOT be affected (and should not be deployed).
But the problem is, they are still being deployed when I deploy (whether it be upload or sync) the entire project.
Now, I know that deployment configuration has options for excluded paths, but shouldn't the paths being marked as "Excluded" as a global project setting do the same?
What am I missing here?
Please sign in to leave a comment.
Hi there,
AFAIK such behaviour (excluded folder still participates in deployment) was specifically asked by users (i.e. to upload some outside generated content (product images etc) that can cause IDE issues (slowdowns/duplicate content etc) when indexed but still needs to be uploaded trough one tool).
So yes -- in your case you need to exclude such folder twice.
Okay, thanks for the information.
So then, what is the benefit of excluding directories via Project Settings -> Directories?
To exclude such folders from indexing by IDE (e.g. files are too big; files are cached/optimized versions of the actual code/prevent full-text search or checking for errors/etc)
P.S.
As of v8 excluded folders are now participating in VCS operations (as per popular request) and can be shown in Project View tree (configurable).