Decide on one way to provision servers #326
Loading…
x
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?
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> -p
we should encourage using
-p -a
for 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,
-a
is 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
-p
does provision pretty reliably?Thanks for picking this up!
decentral1se referenced this issue from toolshed/abra2023-01-31 20:43:01 +00:00