Install on Windows Server

One script installs Statup as a Windows service. Docker stays the main way to install Statup.

Requirements

• Windows Server, 64-bit x86.
• Windows PowerShell 5.1 or PowerShell 7, opened as an administrator.

Install

irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1 | iex

To give parameters, run the script as a script block:

& ([scriptblock]::Create((irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1))) -Port 8080

Or download the file and run it:

irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1 -OutFile install.ps1
powershell -ExecutionPolicy Bypass -File install.ps1 -Port 8080

The script asks a few questions, one at a time, then downloads Statup, checks its checksum, installs the service and waits until it answers. It ends with the address of the instance. Open it to create the administrator: see First launch. An install that stops before Statup starts is undone.

Questions

Press Enter to take the value in brackets. A parameter given on the command line answers its question, which is then not asked.

• -Listen takes all (every address), local (this machine only, for a reverse proxy on it) or an IP address.
• A folder is a full path such as C:\Statup, without a quote, and not a system folder such as C:\Windows or C:\ProgramData. The data folder is on this machine. The backup folder may be a share: see Backups on a share. An existing folder that holds other files is refused.
• The firewall profiles are Domain, Private and Public, one or more.
• The questions need a console. Without one, the script stops and asks for -Unattended.
• When C:\ProgramData\Statup\statup.env exists, from an earlier install that was removed, its settings are kept and only the program folder and the account are asked.

Other parameters

See Without access to GitHub for -Archive and -Mirror.

Install without questions

Give -Unattended and the parameters you need:

& ([scriptblock]::Create((irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1))) -Unattended -Port 8080 -Listen local

Service account

-ServiceAccount takes one of these:

• Virtual, the default: the account NT SERVICE\Statup, which has no password.
• LocalSystem.
• An account with a password, such as DOMAIN\statup or .\statup for a local account, given with -Credential. Without it, the script asks for the password, or stops under -Unattended.
• A group managed service account, such as DOMAIN\statup$, which has no password.

The password is handed to Windows and never written to a file. The script gives the account the right to log on as a service, and the access it needs to the folders of Statup.

$credential = Get-Credential -UserName 'DOMAIN\statup' -Message 'Statup service account'
& ([scriptblock]::Create((irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1))) -ServiceAccount 'DOMAIN\statup' -Credential $credential -Unattended

Windows Firewall

The script opens the port in a rule named Statup, for the profiles of the networks the machine is on, or for the ones you give with -FirewallProfile. When Statup listens on this machine only, it opens nothing. An upgrade moves the rule to the port of the settings. Uninstalling removes it.

What the script installs

• The program, data, uploads and backup folders, and the folder of the settings, are open to the administrators, to the system and to the service account, and to nobody else: ProgramData would let every user read them, and a program folder outside Program Files would let them add files. The service reads statup.env and cannot change it.
• Windows restarts the service after a failure: twice after 5 seconds, then after a minute. The count starts again after a day.
• statup.log, next to the database, holds the log of the server. Above 10 MB, it is set aside as statup.log.1, which replaces the previous one, and a new file starts.
• The service is managed with Get-Service Statup, Stop-Service Statup and Start-Service Statup.

Change a setting

statup.env holds HOST, PORT, DATABASE_URL, UPLOAD_DIR and BACKUP_DIR. Add any other setting to it, one NAME=value per line, then restart the service:

notepad C:\ProgramData\Statup\statup.env
Restart-Service Statup

DATABASE_URL='C:\ProgramData\Statup\statup.db'

The firewall rule stays on the old port after a change of PORT, until the script is run again. After a change of DATABASE_URL, UPLOAD_DIR or BACKUP_DIR, run the script again too: it creates the new folder and lets the service write to it. If Statup does not start, statup.log tells why.

Maintenance commands

Run statup.exe in PowerShell as an administrator, with --env and the settings file. See Command line.

& 'C:\Program Files\Statup\statup.exe' --env C:\ProgramData\Statup\statup.env backup
& 'C:\Program Files\Statup\statup.exe' --env C:\ProgramData\Statup\statup.env reset-password [email protected]

To restore, stop the service first:

Stop-Service Statup
& 'C:\Program Files\Statup\statup.exe' --env C:\ProgramData\Statup\statup.env restore C:\ProgramData\Statup\backups\statup-backup-2026-10-29-163045.db
Start-Service Statup

More on backups in Backups.

Backups on a share

A backup folder such as \\nas\statup must let the service account write to it: the script cannot set that on a share. For the virtual account, give the right to the account of the computer, DOMAIN\SERVER$.

HTTPS

For HTTPS and a name of your own, put IIS in front of Statup: see IIS. Any other reverse proxy works too.

Upgrade

Run the install script again. It finds the installed service and updates it: it stops the service, replaces the program, keeps the settings and the data, moves the firewall rule to the port of the settings and starts the service. The parameters of a new install are ignored, and it says so. To choose the version, add -Version.

• Statup backs up the database before an upgrade changes it: see Upgrading.
• An older version than the installed one is refused unless you confirm, as its database may be too new for it. With -Unattended, it is refused.
• The script waits up to 30 seconds for Statup to answer. A long upgrade can end on “does not answer” while Statup is still starting: read statup.log.

Uninstall

& ([scriptblock]::Create((irm https://github.com/karl-cta/statup/releases/latest/download/install.ps1))) -Uninstall

The script asks first; -Unattended skips the question. It stops and removes the service and the firewall rule, and the program files. It keeps the data and backup folders and statup.env. Installing again finds the settings and keeps them. The program folder is not in the settings: without -InstallDir, it is C:\Program Files\Statup again.

Without access to GitHub

Download install.ps1, statup-<version>-windows-x86_64.zip and SHA256SUMS from the release page on another computer, and copy them over.

The script does not check an archive it is given. Compare the hash of the archive with its line in SHA256SUMS, then install it:

(Get-FileHash -Algorithm SHA256 statup-0.11.0-windows-x86_64.zip).Hash
Select-String statup-0.11.0-windows-x86_64.zip SHA256SUMS
powershell -ExecutionPolicy Bypass -File install.ps1 -Archive statup-0.11.0-windows-x86_64.zip

To serve the files from your own server, copy the archive and SHA256SUMS under <url>/v<version>/. The script downloads them from there and refuses an archive whose checksum differs.

powershell -ExecutionPolicy Bypass -File install.ps1 -Mirror https://files.example.com/statup -Version 0.11.0