Self-host LubeLogger with Levelrail
A self-hosted vehicle maintenance and fuel mileage tracker with reminders and document storage. MIT licensed. On first open, register the first user, which becomes the root account.
- Memory256 MiB
- Archarm64
- Services1
How to self-host LubeLogger
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/hargata/lubelogger:v1.7.4
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 8080.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
LubeLogger requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- 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 LubeLogger. 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 LubeLogger docs page.
Deploy LubeLogger your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy LubeLogger from the CLI
levelrail-cli templates install lubelogger --name my-lubelogger Deploy LubeLogger with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/lubelogger/install \
-d '{
"name": "my-lubelogger"
}' LubeLogger configuration
LubeLogger services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| lubelogger | ghcr.io/hargata/lubelogger:v1.7.4 | 8080 | data -> /App/dataconfig -> /App/configkeys -> /root/.aspnet/DataProtection-Keys |
LubeLogger environment variables
| Variable | Service | Value |
|---|---|---|
| LANG | lubelogger | Preset by the template |
| LC_ALL | lubelogger | Preset by the template |
| LUBELOGGER_ALLOWED_FILE_EXTENSIONS | lubelogger | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 3 named mounts: data -> /App/data, config -> /App/config, keys -> /root/.aspnet/DataProtection-Keys
LubeLogger FAQ
How much memory does LubeLogger need?
The catalog lists about 256 MiB of memory for LubeLogger.
Does LubeLogger run on arm64?
For LubeLogger, an arm64 image is published; amd64 is image published.
Does LubeLogger need configuration before it starts?
No. The template fills in its own defaults.
Which ports does LubeLogger use?
LubeLogger listens on port 8080 inside the stack.
Where does LubeLogger keep its data?
In named volumes: data mounted at /App/data, config mounted at /App/config and keys mounted at /root/.aspnet/DataProtection-Keys.
Can I deploy LubeLogger on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id lubelogger for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/hargata/lubelogger:v1.7.4 is what you deploy there.