---------------------- The

.garden/mutagen/

sub-directory is created by Garden as part of the underlying Mutagen synchronization process. If you're not seeing this directory, it could be due to a few reasons: 1. The synchronization process hasn't started or completed successfully. You can check the status of the synchronization process by running the

garden util mutagen sync list

command from your project root directory. This command lists all active syncs. If there are issues with synchronization, this command can help troubleshoot or gather more information. source () 2. There might be an issue with the path of your Garden project. If the path is too long, Garden will create a new directory to manage syncs. This was mentioned in a Discord support thread where a user encountered a similar issue. source () 3. There could be a problem with your Garden configuration. You can check your Garden configuration for errors by running the

garden validate

command. This command throws an error and exits with code 1 if something's not right in your Garden config files. source () If none of these suggestions help, it might be worth reporting this as an issue on the Garden GitHub page. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

---------------------- The

sourcePath

in your sync configuration should be set to the path of the local directory you want to synchronize with the target. This can be a templated path to another action's source path (e.g.

${actions.build.my-container-image.sourcePath}

), or a relative path. If a path is hard-coded, it's recommended to stick with relative paths, and use forward slashes (

/

) as a delimiter. Windows-style paths with back slashes (

\

) and absolute paths will work on some platforms, but they are not portable and will not work for users on other platforms. By default, if no value is provided, it defaults to the Deploy action's config's directory. Here's an example of how you might set it:

yaml
sync: 
  paths: 
    - sourcePath: "src"

In this example, "src" is the local directory that will be synchronized with the target. You wouldn't typically set

sourcePath

to "/app" unless "/app" is a directory in your local file system that you want to sync.

Sources: - Helm Module () - Jib Container Module () - Container Module () - Kubernetes Module () - Container Deploy Action () - Kubernetes Deploy Action () - Helm Deploy Action () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

---------------------- If your

garden.yml

file is in the root directory and your source directory is named

/app

, you should use

./app

to reference it. The

./

prefix indicates that the path is relative to the current directory (which is the root directory in this case). Here's an example:

yaml
sync: 
  paths: 
    - sourcePath: "./app"

In this example,

./app

is the local directory that will be synchronized with the target. Using

/app

without the

./

prefix would be interpreted as an absolute path from the root of your file system, which is likely not what you want. Remember, it's recommended to use relative paths in your Garden configuration to ensure portability across different platforms. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

---------------------- Yes, you can delete a remote deployment with Garden. The

garden cleanup

command is used to clean up (i.e., delete or undeploy) specific or all deployed services. To delete a specific service, you can use the

garden cleanup deploy

command followed by the name of the service. For example:

sh
garden cleanup deploy my-service # deletes my-service

To delete all deployed services in the project, you can simply use the

garden cleanup deploy

command without specifying a service name:

sh
garden cleanup deploy # deletes all deployed services in the project

Please note that this command does not take into account any deploys depending on the cleaned up actions, and might therefore leave the project in an unstable state. Running

garden deploy

after will re-deploy anything missing. If you want to delete a running namespace, you can use the

garden cleanup namespace

command. This will clean up everything deployed in the specified environment, and trigger providers to clear up any other resources and reset it. When you then run

garden deploy

after, the namespace will be reconfigured.

sh
garden cleanup namespace [options]

Please be aware that you should not delete the

garden-system

namespace directly, because Kubernetes may fail to remove persistent volumes. Instead, use the

garden plugins kubernetes uninstall-garden-services --env <env-name>

command to remove all cluster-wide Garden services.

Sources: - Garden Cleanup Deploy () - Garden Cleanup Namespace () - FAQ - How do I delete the services in the

garden-system

namespace? () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

---------------------- The

mutagen-agent

is part of the underlying Mutagen synchronization process used by Garden. It's automatically installed and managed by Garden, and you typically don't need to install it manually. If you're not seeing the

mutagen-agent

in your

.garden

directory, it could be due to a few reasons: 1. The synchronization process hasn't started or completed successfully. You can check the status of the synchronization process by running the

garden util mutagen sync list

command from your project root directory. This command lists all active syncs. If there are issues with synchronization, this command can help troubleshoot or gather more information. source () 2. There might be an issue with the path of your Garden project. If the path is too long, Garden will create a new directory to manage syncs. This was mentioned in a Discord support thread where a user encountered a similar issue. source () 3. There could be a problem with your Garden configuration. You can check your Garden configuration for errors by running the

garden validate

command. This command throws an error and exits with code 1 if something's not right in your Garden config files. source () If none of these suggestions help, it might be worth reporting this as an issue on the Garden GitHub page. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------