# Self-host UpSnap

> Web dashboard to wake, shut down and ping devices on your network, with scheduled wake ups and per device ports.

- Page: https://levelrail.com/templates/upsnap/
- JSON: https://levelrail.com/templates/upsnap.json
- Category: Networking
- Licence: MIT (Permissive license)
- Source: https://github.com/seriousm4x/UpSnap
- Upstream docs: https://github.com/seriousm4x/UpSnap/wiki

## Requirements
- Memory: about 128 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 5.7.3

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| upsnap | ghcr.io/seriousm4x/upsnap | 5.7.3 | 8090 | data -> /app/pb_data |

## Deploy

### CLI

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

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/upsnap/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. Open the address and create the first admin account. Wake on LAN needs the container on the same network as the devices, so check reachability from a test device.

## Questions

### Can I deploy UpSnap 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 upsnap for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/seriousm4x/upsnap:5.7.3 is what you deploy there.

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