Documentation (beta)

Exclude List patterns for deployment

As SyncRelease uses Phing’s file pattern set for processing exclusion list, you may want to review about file pattern set . If you are already familiar with Phing’s file pattern set, you will feel at home. If not, no worry either.


Following is the most common patterns for exclusion lists you will need most of the time.



Excluding Directory


Excluding a particular directory in your project for deployment process is easy. For example, let’s assume your project has the following directory structure.

applications
    /configs
        applications.ini
        navigation.xml
    /controllers
    /views
library
    /Zend
public
    /index.php

Then, your applications/configs directory contains configuration settings which you don’t want to be overwritten every time deployment is done. That is typically the case with deploying to PRODUCTION or STAGING where they might be configured differently. Then, to exclude the whole configs directory, use the following exclusion pattern.


applications/configs/**



Excluding File

There are times when you want to specifically exclude a particular file in your project when deploying. Taking the same example project as above, let’s say you want to exclude only applications/configs/application.ini file.


Then, the pattern is very simple i.e just the full path to that file relative to the project.


applications/configs/application.ini


Wild-card File Exclusion

Wild-card file exclusion is also doable in SyncRelease. For example, if you want to exclude all unnecessary .psd photoshop mockup files from any folders in your project, use the following pattern.


**/*.psd  #will exclude any photoshop file anywhere in your project

Note

You can enter any many exclusion patterns as you want. All you need to do is enter each exclusion pattern separated by a new line.