Deploy and fully automate a Spasm server with one script
  • Shell 86.1%
  • Jinja 13.9%
Find a file
2026-04-29 00:02:13 +01:00
ansible docs: edit readme 2026-04-17 00:03:52 +01:00
docs docs: add gpg verify steps 2026-04-29 00:02:13 +01:00
scripts/admin/server feat: add fuel 2026-04-02 07:00:11 +01:00
.env.example chore: edit env example 2026-04-15 02:51:59 +01:00
.gitignore feat: add fuel 2026-04-02 07:00:11 +01:00
fetch-verify-repo fix: remove git from url 2026-04-15 04:46:01 +01:00
import-gpg fix: import-gpg on the first run 2026-04-16 01:36:22 +01:00
init docs: edit readme 2026-04-17 00:03:52 +01:00
LICENSE feat: add fuel 2026-04-02 07:00:11 +01:00
package.json feat: add fuel 2026-04-02 07:00:11 +01:00
README.md docs: add gpg verify steps 2026-04-29 00:02:13 +01:00
server-setup feat: log server setup time and flags 2026-04-15 21:39:42 +01:00

Spasm forum full server setup

Mirrors: Forgejo Codeberg Github

Deploy your Spasm forum on a new VPS with a single script that handles everything automatically: industry-standard hardening, app installation with Podman, and auto-updates. You can also verify GPG signatures of all git commits. Enjoy a fully autonomous setup that requires zero server maintenance.

Note: use spasm-docker repo to launch Spasm on an existing server alongside other apps.

Prerequisites

  • DNS points to your server IP.
  • Ethereum or Nostr address/pubkey for an admin panel.

System

  • OS: Debian 13 (trixie)
  • CPU: 1 core
  • RAM: 2 GB

Installation

SSH into your server and execute the following commands from root or admin (sudo).

# install git (Debian)
sudo apt -y install git

git clone https://github.com/spasm-network/spasm-ansible ~/spasm-ansible/

sudo bash ~/spasm-ansible/server-setup

The script asks for your domain name, Ethereum or Nostr address/pubkey, and a server admin password to enable manual interventions (normally, it's not needed since the server is designed to run autonomously).

Your forum will be live after the script finishes execution, which takes about 10 minutes.