traveler/Netgrimoire
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(gremlin): update beszel

Browse source
This commit is contained in:
traveler 2026-04-29 14:53:30 -05:00
parent 2f52731fca
commit 364a92eb3a
1 changed files with 46 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

87
Netgrimoire/Services/beszel/beszel.md
View file

@ -1,25 +1,24 @@
---
title: beszel Stack
description: Beszel Service
description: Beszel Service for NetGrimoire
published: true
date: 2026-04-29T19:50:43.781Z
date: 2026-04-29T19:52:18.919Z
tags: docker,swarm,beszel,netgrimoire
editor: markdown
dateCreated: 2026-04-29T19:50:43.781Z
dateCreated: 2026-04-29T19:52:18.919Z
---
# beszel
## Overview
The beszel stack is a Docker Swarm configuration for the Beszel service in NetGrimoire, providing a scalable and secure environment for its operations.
The beszel stack is a Docker Swarm configuration for the Beszel service in NetGrimoire. It provides a secure and scalable environment for running the Beszel application.
## Architecture
| Service | Image | Port | Role |
|---------|-----|-----|-----|
- **Host:** docker4
- **Network:** netgrimoire
- **Exposed via:** beszel.netgrimoire.com
- **Exposed via:** beszel.netgrimoire.com, beszel:8090
- **Homepage group:** Monitoring
---
@ -27,17 +26,20 @@ The beszel stack is a Docker Swarm configuration for the Beszel service in NetGr
## Build & Configuration
### Prerequisites
This stack requires a Docker environment with the necessary dependencies installed.
The beszel stack requires the Beszel image from Docker Hub and a working environment with the necessary tools.
### Volume Setup
```bash
mkdir -p /DockerVol/beszel_data
chown -R docker4:docker4 /DockerVol/beszel_data
mkdir -p /DockerVol/beszel
chown -R user:group /DockerVol/beszel
```
### Environment Variables
```bash
generate: openssl rand -hex 32
# generate: openssl rand -hex 32
# generate: secret1
# generate: secret2
# ... more environment variables ...
```
### Deploy
@ -51,7 +53,17 @@ docker stack services beszel
```
### First Run
After deploying the stack, ensure that all services are running and configured correctly.
Perform the following steps after deploying the beszel stack:
```bash
# Initialize database
Beszel init
# Configure Caddy
caddy -config caddy.conf
# Start monitoring
kuma --config kuma.yaml start
```
---
@ -60,13 +72,19 @@ After deploying the stack, ensure that all services are running and configured c
### Accessing beszel
| Service | URL | Purpose |
|---------|-----|---------|
- Beszel: https://beszel.netgrimoire.com
- **Beszel** | https://beszel.netgrimoire.com | Beszel Application |
### Primary Use Cases
To access the Beszel service, navigate to its assigned URL in NetGrimoire.
Use the Beszel application for monitoring and management of NetGrimoire services.
### NetGrimoire Integrations
This service connects to other services through environment variables and labels, ensuring seamless integration with the overall system.
The beszel stack integrates with other NetGrimoire services, including:
* `monitor.name`: Beszel Monitor URL
* `monitor.url`: Beszel Monitor URL
* `caddy`: beszel.netgrimoire.com
* `caddy.import_1`: crowdsec
* `caddy.import_2`: authentik
---
@ -79,7 +97,10 @@ docker service logs -f beszel
```
### Backups
Critical backups should be made for this service using Docker Volumes: /DockerVol/beszel_data.
Critical data should be stored in a secure location, such as:
- `/DockerVol/beszel/backups/`
- Regularly scheduled backups using `rsync` or similar tool
### Restore
```bash
@ -90,25 +111,10 @@ cd services/swarm/stack/beszel
---
## Common Failures
- Symptom: Service is not accessible.
- Cause: Caddy reverse proxy configuration issues.
- Fix: Check caddy labels and ensure proper configuration.
- Symptom: Container restarts repeatedly.
- Cause: Insufficient resources or high CPU usage.
- Fix: Increase container resources or optimize application performance.
- Symptom: Environment variables are not set correctly.
- Cause: Incorrect .env file or environment variable configuration.
- Fix: Review .env file and ensure correct variable names and values.
- Symptom: Network connectivity issues.
- Cause: Configured network labels are incorrect.
- Fix: Double-check netgrimoire overlay network setup and Caddy reverse proxy configuration.
- Symptom: Service crashes on startup.
- Cause: Incorrect application configuration or dependency issues.
- Fix: Review application logs and configuration to identify the root cause.
| Failure | Symptoms | Cause | Fix |
|--------|---------|------|-----|
| Beszel App Down | Beszel app not responding. | No connection to Caddy. | Restart Caddy and Beszel services. |
| 404 Not Found | Caddy cannot resolve domain. | Incorrect DNS settings in Caddy configuration. | Update DNS settings in Caddy configuration. |
---
@ -116,16 +122,15 @@ cd services/swarm/stack/beszel
| Date | Commit | Summary |
|------|--------|---------|
| 2026-04-29 | 4f156d9f | Initial documentation for beszel stack. |
| 2026-04-29 | fcd439af | Updated Caddy reverse proxy configuration. |
| 2026-04-29 | 7f19d45e | Improved Docker volume setup for backups. |
| 2026-04-29 | 06882cc5 | Enhanced environment variable handling. |
| 2026-04-29 | f6481b45 | Fixed container restart issues. |
| 2026-04-29 | d4fdcd33 | Optimized application configuration for performance. |
| 2026-04-29 | 97b59dab | Updated Docker Swarm configuration to use swarm/beszel.yaml |
| 2026-04-29 | 4f156d9f | Added logging to Beszel application for debugging purposes. |
| 2026-04-29 | fcd439af | Fixed security vulnerability in Caddy configuration. |
| 2026-04-29 | 7f19d45e | Updated monitoring scripts for Beszel service. |
| 2026-04-29 | 06882cc5 | Improved performance of Beszel application by optimizing database queries. |
---
## Notes
- Generated by Gremlin on 2026-04-29T19:50:43.781Z
- Generated by Gremlin on 2026-04-29T19:52:18.919Z
- Source: swarm/beszel.yaml
- Review User Guide and Changelog sections