Enable abra to include utility recipes #488
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#488
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Its currently not possible to reuse solutions made in one recipe in others without copy-pasting. I would love to reuse parts without having to maintain them seperately. My current use case would be including postgres with major version upgrades. A quick idea to solve this:
include
Would need to implement in abra:
I am unsure if its worth it the additional complexity right now, on the other hand it could make creating and maintaining recipes with the usual databases, caches etc easier.
Good point, it would be great to improve here! But ouch, I'd not wish implementing git submodule handling in
abra
on my worst enemies 😆 I think a simple way to support this would be to agree on a convention (e.g.~/.abra/scripts/abra.sh
or whatever) that isabra
sees, it can source before running stuff?Can you elaborate on how that would work?
I agree that submodules are a pain, they just seem to fit the purpose quite well. I think its important to somehow prevent including the wrong version (looking into it, git submodules might not even be good at that 🤦).