Deploy LinkAce

Self-hosted bookmark archive with tags, lists, link checks; Postgres+Redis

Deploy LinkAce

Just deployed

/data

/app/storage

/var/lib/postgresql/data

Deploy and Host LinkAce on Railway

LinkAce is an open-source, self-hosted bookmark archive. You save links with tags, lists and notes, search them later, share selected lists publicly, and let LinkAce check regularly whether each saved page still works. It can also ask the Wayback Machine to keep a copy of every link you add.

About Hosting LinkAce

LinkAce is a Laravel (PHP) app. This template runs the official LinkAce v2.6.3 image, pinned by digest, with Caddy, PHP-FPM and Laravel's scheduler in one container, next to Railway's Postgres and Redis on the private network. The app keeps its files on a volume and its data in Postgres, so both survive redeploys. On every start it waits for the database, then runs the schema migrations itself. Secrets are generated, and nothing needs to be filled in at deploy time. After the deploy you open the public URL and create the first admin in LinkAce's setup wizard. It runs in 0.5 GB of RAM.

Common Use Cases

  • Keep a personal research archive of articles, docs and tools, organised with tags and lists
  • Find dead links early: LinkAce checks saved URLs every two hours and flags broken ones
  • Share a curated public list or a team reading list from your own domain

Dependencies for LinkAce Hosting

  • LinkAce web app and scheduler, built from aalfath/linkace-railway-template (official linkace/linkace:v2.6.3 image)
  • Postgres (Railway) for links, lists, tags, notes, users and settings
  • Redis (Railway) for cache and sessions

Deployment Dependencies

Implementation Details

Services in this template:

  • LinkAce: the web app on the public domain (health check /_health) plus Laravel's scheduler, which runs the import queue and the link checks. Volume on /app/storage.
  • Postgres: the database, on its own volume.
  • Redis: cache and login sessions.

After deploy: open the public URL, click through the requirements check (the database step is already done), and create the admin account. Optional extras go on the LinkAce service as variables: SMTP for emails (MAIL_MAILER=smtp, MAIL_HOST, MAIL_PORT, MAIL_USERNAME, MAIL_PASSWORD, MAIL_FROM_ADDRESS) and single sign-on (see the LinkAce docs). If you add a custom domain, set APP_URL to it and redeploy. LinkAce's own nightly backup is off; use Railway's Postgres and volume backups.

Updates: when the template repo moves to a new LinkAce version, Railway shows "update available" on your project. Read the repo's CHANGELOG.md, then apply it. Migrations run on start and your data stays.

Why Deploy LinkAce on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying LinkAce on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0