Setting up

The pages to read, in order, to put an Anahita site on the web: for a school, a newsroom, a library, a research group, a non-profit or any community of your own. The web app is a separate repository, anahita-web; its pages are linked where they come in.

1. Getting started: run the whole stack on your own machine first, and sign in to it. Then the web app's Getting started.
2. Configuration: every setting. The ones to decide before anybody signs up are the site's name (Site identity), who may join (Registration), what visitors may read (Privacy of the installation), and the first super administrator (First super administrator).
3. Registration and agreements: how people join, the approval queue, invitations, and your Terms of Service and Privacy Policy.
4. Privacy: who can see a post, a profile and the site, and the two settings that decide it for the whole installation.
5. Deploying: a live site on Kubernetes, on any provider. Hostnames, certificates, object storage, and the database. The web app is built and hosted on its own: Deploying the web app.
6. Federation: joining the fediverse and Bluesky. It is off until you turn it on, and each profile then chooses for itself. Choose the names first: they are for good.
7. The services a site may run or leave out. Each page says what happens without it:
   • Videos
   • Link previews
   • Recommendations
   • Download your data
   • The web shell, which gives each shared link its own title and picture
   • Websites: a website's feed as a profile to follow

Next: Customising, then Operating.