Download via Git¶
This option requires several command-line tools:
Once these are installed, you should:
## Navigate to your extension directory, e.g. cd sites/default/files/civicrm/ext ## Download the extensions git clone https://github.com/civicrm/org.civicrm.flexmailer git clone https://github.com/civicrm/org.civicrm.shoreditch git clone https://github.com/veda-consulting/uk.co.vedaconsulting.mosaico ## Download additional dependencies cd uk.co.vedaconsulting.mosaico ./bin/setup.sh -D
bin/setup.sh handles various build activities:
## Download dependencies ./bin/setup.sh -D ## Regenerate DAOs ./bin/setup.sh -g ## Build zip archive ./bin/setup.sh -z
We use Gulp and Sass for styling and handle different running tasks. Firstly, you should install node packages using npm package manager:
Styling changes should go into
sass directory and compiled to CSS using the following command:
Once you are done making your changes, please use BackstopJS (see Testing to check for any possible visual regression issues
This extension ships with a patched version of Mosaico. The patches are maintained as a fork in https://github.com/civicrm/mosaico using Twigflow (Rebase).
The build/publish process has a few properties:
- It combines
civicrm/mosaico, and any other runtime dependencies into one
- The version number is determined by reading
<version>) and appending the current Unix timestamp.
- Example: If the
versionis declared as
1.0.beta1, then it will be published as
- Three files are published:
- The new
- A JSON document describing the build.
- An alias is provided under the folder
The bot does not publish the new version to
civicrm.org. To do this, download the
latest.zip to get the version from the info.xml (
Then add the actual release zip file to the release node on
Last time a release was tagged (2.5) the extension publisher made it available for download via the extension feed even though it was unpublished. This needs to be fixed before the next release!