Installation and setup

Table of contents

Introduction

The archtika CMS can be fully self-hosted and is a completely independent entity, meaning there are no external interfaces it needs to talk to. This gives you full control over your data.

Please note that after installation, the first user to be registered is the Administrator user, who will have access to the Manage tab, allowing them to manage all users registered on the system. You can see this tab in the Preview section of the Content Management article.

NixOS

Coming soon, see: https://github.com/NixOS/nixpkgs/pull/365218

In nixpkgs there is a complete module for archtika which you can use to easily deploy it on your server and there are some settings you can play with.

Here is a sample setup with some of the archtika module options provided, used in the deployment of the quality assurance instance:

services.archtika = {
  enable = true;
  domain = "qs.archtika.com";
  acmeEmail = "thilo.hohlt@tutanota.com";
  dnsProvider = "porkbun";
  dnsEnvironmentFile = /var/lib/porkbun.env;
  settings = {
    disableRegistration = true;
    maxWebsiteStorageSize = 250;
    maxUserWebsites = 3;
  };
};

For the dnsProvider and dnsEnvironmentFile options, you should read the LEGO Documentation, as this is the Let's Encrypt client and ACME library used by nixpkgs.

Docker

The ability to use Docker for installation may be available in the future, currently only NixOS modules are available as an option, as this project relies heavily on the Nix ecosystem for development environments, packaging and deployment.