This commit is contained in:
		| @ -376,9 +376,9 @@ abra app run foo.bar.com db bash -c 'mysqldump -u root -p"$(cat /run/secrets/db_ | ||||
| ## Can I deploy a recipe without `abra`? | ||||
|  | ||||
| Yes! It's a design goal to keep the recipes not dependent on `abra` or any | ||||
| single tool that we develop. This means the configurationc commons can still be | ||||
| useful beyond this project. You can deploy a recipe with standard commands like | ||||
| so: | ||||
| single tool that we develop. This means that the configuration commons can | ||||
| still be useful beyond this project. You can deploy a recipe with standard | ||||
| commands like so: | ||||
|  | ||||
| ``` | ||||
| set -a | ||||
| @ -387,8 +387,7 @@ cd ~/.abra/recipes/myrecipe | ||||
| docker stack deploy -c compose.yml example_com | ||||
| ``` | ||||
|  | ||||
| `abra` makes all of this more cenvenient but other tooling could follow this | ||||
| approach. | ||||
| `abra` makes all of this more convenient. | ||||
|  | ||||
| ## Proxying apps outside of Co-op Cloud with Traefik? | ||||
|  | ||||
|  | ||||
		Reference in New Issue
	
	Block a user