Where Does Sublinks Store Config and Data?
Sublinks configures through Spring properties and env vars with Postgres in Docker. Pre-MVP layout and Lemmy contrast.
Last updated
Sublinks is still pre-MVP, so treat every path as dev-stage. The Java API reads Spring application properties or YAML plus environment variables, orchestrated through compose files in its docker repos. Postgres runs as a container service rather than a host install.
Lemmy admins should reset expectations. There is no lemmy.hjson here; the config surface is Spring resources plus env. Media and database live in Docker-managed volumes until the project stabilizes host-mount conventions. Check the repo compose files on your checkout before assuming any host path.
Where Sublinks stores this, by platform
src/main/resources/application.properties (plus env vars)
Pre-MVP: paths follow the developer compose in sublinks-api and sublinks-docker repos. Postgres persists in a Docker service volume, not a host data dir. Do not confuse with proxy tools named sublink; this is the Java link aggregator.
Frequently asked questions
How do I configure Sublinks?
Through Spring properties or YAML in resources plus environment overrides, composed via the backend services files. Copy the example compose setup first and edit domain and secrets. Expect renames while the project stays pre-release.
Where is the Sublinks database?
In the Postgres container volume managed by Docker Compose on current checkouts. Dump it with pg_dump through the service rather than hunting host files. Keep dumps with the properties file for a restorable pair.
How is Sublinks different from Lemmy paths?
Lemmy mounts lemmy.hjson plus pictrs and postgres volumes explicitly. Sublinks uses Spring config plus env with a Java API, separate federation service and TS frontend. Same fediverse idea, different file layout entirely.
Notice an outdated path? Let us know.