Self-host LinkAce with Levelrail

A self-hosted bookmark archive with tags, lists, link checks and a REST API. GPL-3.0 licensed. Runs on SQLite in one container. On first open, register the admin account; the public address you assign is used as the app URL, so assign the domain before the first visit.

  • AuthorKovah
  • LicenceGPL-3.0-or-later
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host LinkAce

  1. Pull the images

    One image is pulled on your server.

    Show images
    • linkace/linkace:v2.6.3
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

LinkAce requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-or-later, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then LinkAce. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the LinkAce docs page.

Deploy LinkAce your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy LinkAce from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain linkace=app.example.com.

levelrail-cli templates install linkace --name my-linkace

Deploy LinkAce with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/linkace/install \
  -d '{
    "name": "my-linkace"
  }'

LinkAce configuration

LinkAce services

ServiceImagePortsVolumes
linkace linkace/linkace:v2.6.3 80 storage -> /app/storage

LinkAce environment variables

VariableServiceValue
APP_KEY linkace Generated at deploy
APP_TIMEZONE linkace Preset by the template
APP_URL linkace Preset by the template
DB_CONNECTION linkace Preset by the template
DB_DATABASE linkace Preset by the template
LOG_CHANNEL linkace Preset by the template
TRUSTED_HOSTS linkace Preset by the template
TRUSTED_PROXIES linkace Preset by the template

Ports and volumes

Ports
80
Volumes
1 named mount: storage -> /app/storage

LinkAce FAQ

How much memory does LinkAce need?

The catalog lists about 256 MiB of memory for LinkAce.

Does LinkAce run on arm64?

For LinkAce, an arm64 image is published; amd64 is image published.

What licence is LinkAce under?

LinkAce is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.

Does LinkAce need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does LinkAce use?

LinkAce listens on port 80 inside the stack.

Where does LinkAce keep its data?

In a named volume: storage mounted at /app/storage.

Can I deploy LinkAce on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for LinkAce, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image linkace/linkace:v2.6.3 is what you deploy there.

levelrail-cli templates install linkace --name my-linkace