# Self-host LinkAce

> 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.

- Page: https://levelrail.com/templates/linkace/
- JSON: https://levelrail.com/templates/linkace.json
- Category: Productivity
- Licence: GPL-3.0-or-later (Copyleft license)
- Source: https://github.com/Kovah/LinkAce
- Upstream docs: https://www.linkace.org/docs/

## Requirements
- Memory: about 256 MiB
- amd64: published, arm64: published
- Needs configuration before start: no
- Pinned image tag: v2.6.3

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| linkace | linkace/linkace | v2.6.3 | 80 | storage -> /app/storage |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| linkace | APP_KEY | generated |
| linkace | APP_TIMEZONE | preset |
| linkace | APP_URL | preset |
| linkace | DB_CONNECTION | preset |
| linkace | DB_DATABASE | preset |
| linkace | LOG_CHANNEL | preset |
| linkace | TRUSTED_HOSTS | preset |
| linkace | TRUSTED_PROXIES | preset |

## Deploy

### CLI

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

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

### API

```bash
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"
  }'
```

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

## Questions

### 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.

Self-host LinkAce, LinkAce docker compose file, deploy LinkAce on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
