Missing mariadb compose file #27
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?
did I miss a step or something? Here's how I tried to set it up:
abra app new nextcloud -S
abra app config files.aadils.computer
(update url in config file)abra app deploy files.aadils.computer
Soooo, some work just went down on the database stuff in #26 /cc @yksflip and I believe you need to do this in your
.env
file:This should have been covered in the
.env.sample
file you received on new app creation but maybe you created it before this upgrade work happened? Unsure.Other work-arounds may be doing something like:
Unsure of your local git repository state, it could be confusing
abra
potentially.hmm so I tried the
git checkout main
andgit pull origin main
, but when I runabra app deploy
I get the same error. I checked the nextcloud recipe directory and it reverted to the previous git state.Ah hmm, perhaps checking out the latest once more and running
deploy -C
?I think we need to publish this new version in the catalogue which I will try to do soon.
hmm I thought I did that here maybe i did smth wrong?
Ah, nice! I deployed this by running
make
in~/.abra/catalogue
. I think only Autonomic people can actually deploy the changes at the moment 😿 We need to work out access or better, automation to get those changes out as they come in.Also, please note folks, we've not really had several folks using a recipe ("operators") and several folks maintaining that recipe ("maintainers") at the same time before imho, so we're working this out as we go along 😆 Thanks for patience on these growing pains...
Oh, I mistakenly didn't deploy the changes 🦀 but @knoflook is picking this up 🤞
This should be fixed now! Ping on matrix chat if you want new catalogue changes deployed for now. Feel free to re-open if stuff is still borked!