[feat] Multinode Guide So Far #331

2026-09-23T09:38:03Z

amras commented

2026-09-23 09:38:03 +00:00

Over a few sessions, @papiris:data.coop and I pooled our knowledge and experience into this pad. The result is this How-To Guide, describing what we know so far about multinode setups. Meaning: 1 or more manager node, with 1 or more worker nodes in a docker swarm.

I've done my best to follow the syntax used in other docs, but I'm not sure exactly what flavor of markdown we're using or how to render it locally. I'd appreciate a review - both to make sure things render properly, and to confirm the information is legible, usefully linked, and correct.

Over a few sessions, @papiris:data.coop and I pooled our knowledge and experience into [this pad](https://pad.data.coop/SCAk4RQhRBy84SylWQehIQ?view). The result is this How-To Guide, describing what we know so far about multinode setups. Meaning: 1 or more manager node, with 1 or more worker nodes in a docker swarm. I've done my best to follow the syntax used in other docs, but I'm not sure exactly what flavor of markdown we're using or how to render it locally. I'd appreciate a review - both to make sure things render properly, and to confirm the information is legible, usefully linked, and correct.

❤️ 2

amras added 1 commit 2026-09-23 09:38:04 +00:00

[feat] Multinode Guide So Far 0c804a382b

Over a few sessions, @papiris:data.coop and I
 pooled our knowledge and experience into
 [this pad](https://pad.data.coop/SCAk4RQhRBy84SylWQehIQ?view).

This commit creates a How-To Guide,
 describing what we know so far about
 multinode setups. Meaning: 1 or more manager node,
 with 1 or more worker nodes in a docker swarm.

3wordchant commented

2026-10-15 06:28:01 +00:00

how to render it locally.

make — but your mileage may vary, Python is still somehow sometimes painful.

Meanwhile I tried taking a run at edits but I'm not sure what the formatting of the numbered items should be, e.g. **1. *On every node*, make sure docker is installed and running. — is this meant to be a double-indented bulleted list? If you let me know I can finish my patch 😄

> how to render it locally. `make` — but your mileage may vary, Python is still somehow sometimes painful. Meanwhile I tried taking a run at edits but I'm not sure what the formatting of the numbered items should be, e.g. `**1. *On every node*, make sure docker is installed and running.` — is this meant to be a double-indented bulleted list? If you let me know I can finish my patch 😄

3wordchant commented

2026-10-15 06:28:23 +00:00

Also, should have led with this, AMAZING WORK, so hype about this 🤘

amras commented

2026-10-15 13:02:07 +00:00

Meanwhile I tried taking a run at edits but I'm not sure what the formatting of the numbered items should be, e.g. **1. *On every node*, make sure docker is installed and running. — is this meant to be a double-indented bulleted list? If you let me know I can finish my patch 😄

** here is meant to be bold. Embarrasingly, I forgot the closing ** on each line 😅

My reasoning:

Initially these were regular numbered items, but I figured this format, of short summary, then paragraphs and code examples, might need special formatting. Both because the numbered items aren't all in one block - which can break some markdown parsers - and because the summary could be highlighted somehow.

I found a working example in the operators tutorial. This looked legible, so I borrowed the formatting here.

> Meanwhile I tried taking a run at edits but I'm not sure what the formatting of the numbered items should be, e.g. `**1. *On every node*, make sure docker is installed and running.` — is this meant to be a double-indented bulleted list? If you let me know I can finish my patch 😄 `**` here is meant to be bold. Embarrasingly, I forgot the closing ** on each line 😅 My reasoning: Initially these were regular numbered items, but I figured this format, of short summary, then paragraphs and code examples, might need special formatting. Both because the numbered items aren't all in one block - which can break some markdown parsers - and because the summary could be highlighted somehow. [I found a working example in the operators tutorial.](https://docs.coopcloud.tech/operators/tutorial/#web-proxy-setup) This looked legible, so I borrowed the formatting here.

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin multinode-howto:multinode-howto

git checkout multinode-howto

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/docs.coopcloud.tech#331