From: cashmere <bbs@bbs.copland.systems>
To: bbs@bbs.copland.systems
Subject: [WORK IN PROGRESS] Quick setup
Date: Thu, 13 Aug 2026 17:37:51 +0000 [thread overview]
Message-ID: <6dffe14adb003004b9f10a34191f3215@bbs.copland.systems> (raw)
# Registration
Register on <https://bbs.copland.systems/register>. Your username must be at least 6 characters long and may only contain `a-z`, `0-9`, `-`, `_` and `.`. Registration gives you the **local** rank automatically: you can read everything and submit forum posts for moderation.
# Clone
Clone the repository. Replace `USERNAME` with the exact name you registered with:
```sh
fossil clone https://USERNAME@bbs.copland.systems bbs.fossil
```
The `USERNAME@` part matters: it makes your local clone use your registered name for everything you create. Without it, your changes would be authored under your operating system username, and that wrong name stays in the history forever. You do not need to wait for approval before cloning.
Fossil will ask for your password during the clone. Say yes when it asks to remember it, so later syncs will not ask again.
# Start UI
Start the local UI:
```sh
fossil ui bbs.fossil
```
Note: the local UI always shows you with full powers, including user administration. That is normal and only affects your own clone. Ranks are enforced on the server, never locally.
Make your changes through the local UI: forum posts, wiki pages, your profile page under `users/USERNAME`. Everything works offline.
# Push changes
Push your changes upstream:
```sh
fossil sync -R bbs.fossil
```
If your account has not been approved yet, this answers with `Error: not authorized to write`. That is expected and harmless: nothing is lost, your work stays in your local clone. Ask the sysop to approve you to the **wired** rank, then run the same command again.
As **wired** you can publish forum posts immediately, create and edit wiki pages, use chat and push your changes upstream.
# Troubleshooting
If anything ever feels out of sync between your local name and your registered name: do not try to fix it on the server. Delete your clone and clone again as described in **Clone**.
--
https://bbs.copland.systems/forumpost/6dffe14adb
next reply other threads:[~2026-08-13 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:37 cashmere [this message]
2026-08-14 19:56 ` [WORK IN PROGRESS] Quick setup joshuablais
2026-08-14 20:19 ` cashmere
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6dffe14adb003004b9f10a34191f3215@bbs.copland.systems \
--to=bbs@bbs.copland.systems \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).