When merging YAML files, Mutagen will merge destination-specific configuration.Īs with normal Compose projects, you can specify these configuration elementsĪcross multiple YAML files. X-mutagen configuration looks something like: Synchronization sessions and configurationSource andĬonfigurationDestination keys for forwarding sessions. Specified using the configurationAlpha and configurationBeta keys for
Projects can also have endpoint-specific configuration options, which are You to define keys that refer to named sessions. In addition to a defaults key for synchronization and forwarding, it allows
Global configuration format described in the introduction. The format of the x-mutagen field is an extension of the Synchronization configuration here, whereas in real-world usage you’ll likely Targets, you don’t need to explicitly create networks as in this example-you can While volumes are necessary for synchronization
Gpodder install mutagen code#
In this example, we use a separate volume to store code and On our local system (so that you can test it locally and from other devices on We also define two Mutagen forwarding sessions: one that exposes theĭatabase to our local system (so that you can access it via a local client forĭevelopment purposes) and one that exposes a web appplication on all interfaces In this example, we define a Mutagen session to synchronize code from theĬompose project directory to a shared volume that we mount into our applicationĬontainer. # Define synchronization and forwarding sessions x-mutagen: sync: defaults: ignore: vcs: true code: alpha: "." beta: "volume://code" forward: database: source: "tcp:localhost:5432" destination: "network://backend:tcp:database:5432" web: source: "tcp::8080" destination: "network://frontend:tcp:web:8080" volumes: - code:/code networks: - frontend - backend. # Define networks networks: frontend: backend: # Define volumes volumes: code: # Define services services: database. Here’s an example of what such a YAML file might look X-mutagen field at the root of your Compose YAML with Mutagen configurationĪnd session definitions. To define synchronization and forwarding sessions, you just need to include an Information and creates, updates, and terminates Mutagen synchronization andįorwarding sessions alongside your Compose-based services, volumes, and The mutagen-compose command is aĬomplete Compose implementation that understands x-mutagen configuration Once you’ve added these fields, you can use the mutagen-compose command to Target Docker volumes and networks, respectively. In Compose YAML files to define synchronization and forwarding sessions that Mutagen Compose uses x-mutagen extension fields Here are a few other examples to get you started: To get an idea of what’s involved with integrating Mutagen, and try starting the That demonstrates using this integration in the Mutagen repository. Support for Docker Compose, but the best way to experience it is to look at anĮxample project and try it for yourself. The following sections provide detailed information about using Mutagen’s Of Mutagen Compose without the need for an alternative Compose implementation. Mutagen-synchronized filesystem caches, offering the same performance benefits Available that provides automatic replacement of bind mounts with
0 kommentar(er)
