There are som different concepts in dropcat, description of them below.
Environment yaml files
The base configuration on a site is in yaml files that is normaly placed inside
a directory in the root of your project in a folder called .dropcat. They could
also be placed in the root of the project.
Naming convention is:
- dropcat.dev.yml = dev environment
- dropcat.prod.yml = prod environment
- etc.
You could specify which environment to use, with the --env option, so to use
prod you use:
dropcat update --env=prod
Better use is to set the the environment at the beginning of a job or in a script,
then you use the environment variable DROPCAT_ENV, like:
export DROPCAT_ENV=prod
Trackerfiles
Trackerfiles is yaml-files used to store information about an application and deploys. A default tracker for the site is created in the prepare and a backup tracker.
Normaly trackerfiles is stored in a location like:
/var/lib/jenkins/trackerdir
Defined in yaml like:
tracker:
dir: /var/lib/jenkins/trackerdir
Default tracker
The default tracker has the basic infromation about the site, like remote adress to web server, drush alias, mysql login etc.
The deafult tracker is saved in the folder default inside the trackerdir, with the name of the application - if you application has the name ‘foobar’, you will get a default tracker called ‘foobar.yml’ inside default folder.
Backup tracker
the rollback tracker files is stored in the appname folder (like mysite) below the trackerdir, named after the deploy (like mysite_1016.yml). Inside it you have information about the real path to the site on the web server, path to database backup etc. Stuff that is needed to rollback the latest deploy.