Install
Install logship-frontend
The logship frontend is a web application that provides a browser-based UI for querying, dashboards, and administration. It is available as an OCI container image.
Docker
Images are published to the Logship container registry:
| Registry | Image |
|---|---|
| Logship Container Registry | cr.logship.io/logship-frontend |
Pull the image
docker pull cr.logship.io/logship-frontend:latestRun a local container
docker run -d --name logship-frontend \
-p 8000:8000 \
-e ASPNETCORE_URLS=http://+:8000 \
cr.logship.io/logship-frontend:latestdocker run -d --name logship-frontend `
-p 8000:8000 `
-e ASPNETCORE_URLS=http://+:8000 `
cr.logship.io/logship-frontend:latest- UI:
http://localhost:8000
Docker Compose
services:
logship-frontend:
image: cr.logship.io/logship-frontend:latest
ports:
- "8000:8000"
environment:
ASPNETCORE_URLS: http://+:8000
restart: unless-stoppedFull stack with Docker Compose
Deploy the frontend alongside the database:
services:
logship-database:
image: cr.logship.io/logship-database:latest
ports:
- "5000:5000"
- "6000:6000"
volumes:
- ./logship:/logship
environment:
ASPNETCORE_URLS: http://+:5000
restart: unless-stopped
logship-frontend:
image: cr.logship.io/logship-frontend:latest
ports:
- "8000:8000"
environment:
ASPNETCORE_URLS: http://+:8000
depends_on:
- logship-database
restart: unless-stoppeddocker compose up -dVersion pinning
Pin to a specific version instead of latest:
docker pull cr.logship.io/logship-frontend:0.1.0| Tag | Description |
|---|---|
latest | Latest stable release |
x.y.z | Specific version |
Native install by sh
For native single-host installs, use the deployment installer from logship-deployments:
curl -fsSL https://raw.githubusercontent.com/logship-io/logship-deployments/main/src/shell/install.sh | sh -s -- --frontendBy default this installs under /opt/logship/frontend, writes appsettings.json, and creates a systemd service on Linux. Add --database and --agent to provision the whole stack together.
Configuration
Point the frontend at your logship database backend using the ClientSettings.BackendUrl setting.
See the Configuration page for full details.
Upgrades
- Container: Pull the new tag and restart.
- Native: Re-run the shell installer with
--frontend(and--overwriteif you want to regenerate config), then restart or let systemd restart the service.