Add easy way to integrate additional files to deployment #489
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are cases where adding a custom file to a deployment would be very helpful, for example to add a logo or overwrite a special config file, that might not make sense to fully represent in the
.envfile (e.g. custom css files, extensive configs as with mediawiki).A good solution would be to provide a simple list with
source:targetin.env. Source files should be found relative to theservers/<domain>/folder, as you'd probably store it in git with the cc configs.This is my workaround, though I don't find it very elegant:
Additional files:
In
<domain>.env:In
~/.abra/servers/<domain>/<app_name>/compose.yml:The upside of this method is being able to add anything I'd want without modifying the recipe.