You can configure projects to import files and environment variables from other projects. This way you can use your team’s existing work as reusable building blocks to avoid unnecessary repetition.
You can manage a canonical dataset used by multiple projects in a single place.
Your code can reside in a separate project from your data. You don’t have to duplicate large datasets in multiple projects.
An external data source (such as a database) that requires login credentials might be securely represented through environment variables in a single project, and then used by many projects.
You can import results from one model (such as trained model files or R workspaces) and use them in multiple downstream projects.
If a project’s files are organized as an R or Python package, you can configure other projects to automatically install them at runtime.
Configure the project from which you will export files and environment variables. You must have Owner, Collaborator, or Project Importer access to the projects to set them up for export. See Set Up Exports.
Import content from the projects that you configured for export. See Set Up Imports. After you’ve set up the import, the content from the exporting projects is accessible when you run code in the importing project.
During runs with imported files, each project directory is located at
/mnt<username>/<project name>, where
<username>is the owner of that particular project. Imported directories are read-only.
The path of your main project will also change from
/mnt<username>/<project name>. If you have hardcoded any paths in your projects to
/mnt, Domino recommends that you replace the hardcoded paths with the
$DOMINO_WORKING_DIRenvironment variable. This ensures the correct path, regardless of whether other projects are imported. See Domino Environment Variables for more information.