This page is a work-in-progress guide to get your own Federated Wiki server running, using Co-op Cloud 
– the same system that's running this wiki .
🍎 ＲＥＱＵＩＲＥＭＥＮＴＳ
👉 A server - virtual or physical. A cheap ($5/€5 per month, 1GB RAM) Virtual Private Server (VPS) should be fine, as should a spare computer.
👉 A domain name - ideally registered through Gandi.net or OVH, although support for most other providers can be added quickly.
👉 Knowledge: basic (UNIX/Linux) command-line skills, and the ability to configure DNS records.
💡 If you don't have one or any of these things, but you'd like a Federated Wiki of your own, then get in touch! Join the Co-op Cloud Matrix channel or email Autonomic Co-operative on helo@autonomic.zone.
🍎 ＳＥＴ－ＵＰ
1. Install Docker on your server, and install "abra", the Co-op Cloud command-line tool, on either your computer, or your server. You can find step-by-step instructions for all of this in the "Deploy your first app" guide in the Co-op Cloud documentation
2. Deploy Traefik (following the same guide). When you get to the `abra app traefik_example_com config` step, uncomment either the Gandi or OVH sections, depending on your DNS provider
3. Add your Gandi/OVH API key, with e.g. `abra app traefik_example_com secret insert gandiv5_api_key v1 my-cool-api-key`
4. Create an instance of federatedwiki: run `abra app new federatedwiki`, then follow prompts.
5. Make sure DNS records are set up for your Federated Wiki instance. As well as the wildcard record you added in step #1, you might want to add a second wildcard record below it. E.g. if your wiki domain is `wiki.example.com`, you might want to add an A or a CNAME for `*.wiki.example.com`.
6. Deploy your app, with `abra app fedwiki_example_com deploy`.
7. Visit https://wiki.example.com, or any subdomain e.g. https://test.wiki.example.com, in a web browser.
🍎 ＡＵＴＨＥＮＴＩＣＡＴＩＯＮ
This deployment currently uses "Friends" security.
By default, anyone can create a wiki by visiting the URL and clicking the lock to claim it.
If someone loses their browser session, or wants to log in from a different device then you, the administrator, will need to look up their "friend secret".
To do so, run `abra app fedwiki_example_com run app cat .wiki/WIKIDOMAIN/status/owner.json`, where WIKIDOMAIN is the domain (or subdomain) of the wiki.
Alternatively, you can set things up so that only wikis which are predefined in the server configuration are allowed. Run `abra app fedwiki_example_com config`, and uncomment the lines relating to "owner" security.
🍎 ＴＲＯＵＢＬＥＳＨＯＯＴＩＮＧ
👉 If you get SSL errors, check the logs of your Traefik instance to see if there are any issues generating certificates – run `abra app traefik_example_com logs`, or optionally `abra app traefik_example_com config` to increase LOG_LEVEL first. You might also want to enable Traefik's dashboard (in that same config file) to see if there are any typoes or other problems in the route / service definitions.
👉 `.wiki/WIKIDOMAIN/status/owner.json` files won't exist if you're using "owner" security – you will either need to give out the top-level key, or manually define wikis (and users).
🍎 ＭＡＩＮＴＥＮＡＮＣＥ
👉 To upgrade, run `abra app fedwiki_example_com deploy --update`. Abra will automatically fetch the latest version of Fedwiki, and warn you if you're already on the latest.
👉 To download a backup, run `abra app fedwiki_example_com backup`. This will download a copy of the `.wiki` directory to `~/.abra`.
👉 If you need to restart Federated Wiki, e.g. after changing a config file, run `abra app fedwiki_example_com restart app`
🍎 ＫＮＯＷＮ ＩＳＳＵＥＳ
👉 Doesn't federate with unenecrypted (HTTP vs HTTPS) wikis, unless you're logged-in.
👉 Owner usernames are automatically generated (although they can be changed)