You can ignore files in your project which excludes them from the domino sync operation.
This includes if you sync from your local machine (with the CLI or R package, or sync at the end of a run or during a workspace session.
The .dominoignore is automatically created at the root of every new project.
A .git/ directory is always ignored by the sync operation, even if not listed in .dominoignore.
|
Note
|
You can use the * symbol as a wildcard to match files of a similar pattern.
All paths must be relative to the project root.
|
-
Enter the name of the file to be ignored in
.dominoignore. -
To ignore a folder and its contents, add the folder’s name to
.dominoignore.
You can configure your project to save results to an isolated branch.
You can access these results from the application as well as CLI, but they will not be downloaded by domino sync, nor will they be used as input to future runs unless you explicitly specify this.
See Download Execution Results for more information.
Sometimes, neither .dominoignore nor results branches are sufficient approaches.
For example, imagine you are developing a recurring data cleaning task that produces large files used by other projects.
You want to sync these results back to the main project at the end of the run, but don’t want to sync them to your local machine during development.
To do this, put your code in one project and import it into a different project in which the large-output runs will occur. This way you can sync with the code project without downloading the results stored in the data output project. You can even configure the code project to be imported as a package, and it will be automatically installed and accessible at runtime.