Decide on one way to provision servers #326

Closed
opened 2022-06-03 11:55:07 +00:00 by knoflook · 1 comment
Owner

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

Related PR: https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/pulls/71 [In the docs we're saying](https://docs.coopcloud.tech/operators/tutorial/#server-setup) 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](https://docs.coopcloud.tech/operators/tutorial/#add-your-server) `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 added the
documentation
label 2022-06-03 11:55:07 +00:00
Owner

@knoflook

Ah yes, a bit confusing alright.

we should encourage using -p -a for provisioning imo

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"?

say that installing docker & initialising swarm is the advanced approach

Proposal:

abra has support for creating servers (abra server new) but that is a more advanced automation option which is 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're ready to start.

Since -p does provision pretty reliably?

Thanks for picking this up!

@knoflook Ah yes, a bit confusing alright. > we should encourage using -p -a for provisioning imo 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 https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/pulls/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`"? > say that installing docker & initialising swarm is the advanced approach Proposal: > `abra` has support for creating servers (`abra server new`) but that is a more advanced automation option which is 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're ready to start. Since `-p` does provision pretty reliably? Thanks for picking this up!
decentral1se added this to the (deleted) project 2022-06-17 09:35:23 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#326
No description provided.