Comparing version 0.0.2 to 0.0.3
{ | ||
"name": "cartocc", | ||
"desciption": "Carto Config Customizer is a very simple tool for customizing layers values of a `.mml` config file ", | ||
"version": "0.0.2", | ||
"description": "Carto Config Customizer is a very simple tool for customizing layers values of a `.mml` config file ", | ||
"version": "0.0.3", | ||
"url": "https://github.com/yohanboniface/cartocc", | ||
@@ -6,0 +6,0 @@ "engines": { |
@@ -102,1 +102,11 @@ # CartoCC — Carto Config Customizer | ||
``` | ||
### Collaborative workflow suggestion | ||
When using TileMill in a collaborative workflow, the commits involving the `.mml file` can be polluted by changes related to local configuration. To avoid this, here is a suggested workflow. | ||
**Important limitation to notice**: it will not be possible to use TileMill itself for managing the `.mml` file. | ||
1. Use as `.mml` a `<project-name>.mml` file; only this one must be versionned (TileMill defaults to `<project-name>.mml` in case `project.mml` is missing) | ||
2. Use a file `cartocc.json` located in your project root to store the rules. | ||
3. Use the following command to process the configuration: `cartocc <project-name>`; this will generate a `project.mml` file in the project root, which will be used by TileMill; this file must not be committed. |
Sorry, the diff of this file is not supported yet
15775
112