How to provision kadabra? #395
Closed
opened 2023-02-01 16:40:28 +00:00 by moritz
·
7 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
No labels
question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#395
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Related to coop-cloud/organising#236 I have some design questions about the autoupdater.
abra autoupdater provision?I would prefer to use cronjobs for the follwing reasons:
I think it would be a nice to provide an installation script that copies the binary, configures the cronjob and email settings.
A simple setup would look like this:
A disadvantage of this approach is that it's not completely independent of the underlying system.
Incredible!
I'd be up for a
curl https://install.kadabra.coopcloud.tech | bashand it seems to be inline with theabrainstaller. Following coop-cloud/abra#255 there is a proposal to remove provisioning logic, so documenting how to do this with classic*nixtooling seems ideal to me. I think the bash installer script could help people set up the basics?That could be worked into coop-cloud/abra#268 or in another place, as you like.
Some documentation for the decisions that we make here would be ideal.
coop-cloud/abra#268 is merged! We can get to the installer script shortly after. I think the releaser logic will publish binaries for the next release.
I pushed some brief docs about setting up the auto-updater:
https://docs.coopcloud.tech/operators/tutorial/#automatic-upgrades
An installer script will follow.
How to provision the autoupdater?to How to provision kadabra?So, coop-cloud/organising#402 is an issue but we're nearly there for being ready to wire up the installer script. Unless you can hack the script to download the correct "abra" binary and renamed it to
kadabraas is 🙃Binaries are there
Another idea would be to create a recipe for kadabra. With access to the docker socket it shouldn't be a problem to run kadabra inside a container I guess.
This would facilitate the deployment and the cron/alert configuration per env file.
p4u1 referenced this issue2024-03-11 12:57:14 +00:00
kadabrahas been archived: https://git.coopcloud.tech/toolshed/kadabra