# Self-host VictoriaLogs

> A log database with a built in web UI and low memory use, with a data volume. Send logs to port 9428 from this project. The API has no login, so restrict access before exposing it.

- Page: https://levelrail.com/templates/victorialogs/
- JSON: https://levelrail.com/templates/victorialogs.json
- Category: Monitoring
- Licence: Apache-2.0 (Permissive license)
- Source: https://github.com/VictoriaMetrics/VictoriaLogs
- Upstream docs: https://docs.victoriametrics.com/victorialogs/

## Requirements
- Memory: about 256 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: v1.53.0

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| victorialogs | victoriametrics/victoria-logs | v1.53.0 | 9428 | vlogs_data -> /victoria-logs-data |

## Deploy

### CLI

```bash
levelrail-cli templates deploy victorialogs --name my-victorialogs
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/victorialogs/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## First run
1. Ship logs to http://victorialogs:9428 from this project, then open the web UI to search them.

## Questions

### Can I deploy VictoriaLogs 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 VictoriaLogs, 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 victoriametrics/victoria-logs:v1.53.0 is what you deploy there.

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