Decide on one way to provision servers #326
Closed
opened 2022-06-03 11:55:07 +00:00 by knoflook
·
1 comment
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
documentation
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#326
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 PR: coop-cloud/docs.coopcloud.tech#71
In the docs we're saying
abra has support for both creating servers (abra server new) & provisioning them (passing --provision to abra server add) but those are more advanced automation options which are covered in the handbook. For this tutorial, we'll focus on the basics. Assuming you've managed to create a testing VPS with some $hosting_provider, you'll need to install Docker, add your user to the Docker group & setup swarm mode:
and then telling folks to run
abra server add <server-domain> -pwe should encourage using
-p -afor provisioning imo and say that installing docker & initialising swarm is the advanced approach. Let me know what you think and i'll re-work this PR @decentral1se @3wordchant@knoflook
Ah yes, a bit confusing alright.
I'm not sure because most VPS providers wire up your account SSH key into the root user account. At least in my experience. So,
-ais not really necessary then for the default?Maybe we could adjust coop-cloud/docs.coopcloud.tech#71 to instead to a big yellow warning saying "hey, take a second to stop and think - do you have root access? Yes, then fine. No? Then pass
-a"?Proposal:
Since
-pdoes provision pretty reliably?Thanks for picking this up!
decentral1se referenced this issue from toolshed/abra2023-01-31 20:43:01 +00:00