Remote source: A repository that contains one or more Garden modules and their corresponding
Remote module: The source code for a single Garden module. In this case, the
garden.ymlconfig file is stored in the main project repository while the module code itself is in the remote repository.
sourcesdirective in the project-level
garden.ymlconfig files. For example, this is the file tree for the remote
repositoryUrldirective in the module-level
repositoryUrlto a local file path:
garden.ymlfiles should be checked into your version control system and therefore shouldn't contain anything specific to a particular user's setup.
link module|sourcecommand. To link the
web-servicessource from above, you would run:
web-servicesrepository and it will work just the same as when you edit the main project. For example, if you run Garden in watch mode in the main project and update the local version of
web-services, you'll see Garden pick up the changes and re-build and re-deploy the services from
garden unlink source|module <name-of-source>. For example:
web-servicessource from above to something like a
masterbranch, and we now wanted to pull the latest code from the remote, we would run:
.garden/sources/projectsare handled like any other directory in the main project. They're scanned for
garden.ymlfiles and the modules found are synced to the
garden.ymlfile in the main project and then knows to looks for the source code for that module under
./garden/sources/modules. As for other modules, the code gets synced to the
./garden/sourcespaths. Additionally, Garden watches the local paths when in watch mode.
.garden/sourcesdirectory if the URL changes.