docs(gremlin): update mealie

This commit is contained in:
traveler 2026-04-15 19:24:52 -05:00
parent 65df06d0f3
commit 32baa7b519

View file

@ -1,24 +1,26 @@
---
title: mealie Stack
description: Mealie recipe manager for NetGrimoire
description: Recipe Manager for NetGrimoire
published: true
date: 2026-04-15T23:27:38.111Z
date: 2026-04-16T00:22:31.180Z
tags: docker,swarm,mealie,netgrimoire
editor: markdown
dateCreated: 2026-04-15T23:27:38.111Z
dateCreated: 2026-04-16T00:22:31.180Z
---
# mealie
## Overview
The mealie stack is a recipe manager service in NetGrimoire, providing a central hub for users to discover and access recipes.
The mealie stack provides a Recipe Manager for NetGrimoire, allowing users to manage and share recipes within the platform. The primary services involved are the Mealie application, which handles user authentication, recipe management, and rendering.
---
## Architecture
| Service | Image | Port | Role |
|---------|-----|-----|------|
|---------|-----|-----|---------|
- **Host:** docker4
- **Network:** netgrimoire
- **Exposed via:** recipe.netgrimoire.com
- **Exposed via:** `recipe:9000`
- **Homepage group:** PNCHarris Apps
---
@ -26,16 +28,16 @@ The mealie stack is a recipe manager service in NetGrimoire, providing a central
## Build & Configuration
### Prerequisites
None specified.
No specific prerequisites are required for this stack.
### Volume Setup
```bash
mkdir -p /DockerVol/mealie
chown -R mealie:mealie /DockerVol/mealie
```
### Environment Variables
```bash
# generate: openssl rand -hex 32
PUID=1001
PGID=998
TZ=America/Chicago
@ -71,7 +73,7 @@ docker stack services mealie
```
### First Run
Run `./deploy.sh` after the initial deployment to complete any necessary setup.
After deployment, verify that the Mealie application is accessible and functioning correctly.
---
@ -79,29 +81,34 @@ Run `./deploy.sh` after the initial deployment to complete any necessary setup.
### Accessing mealie
| Service | URL | Purpose |
- **Recipe**: recipe.netgrimoire.com
|---------|-----|---------|
- **Mealie**: `https://recipe.netgrimoire.com`
- **Caddy Reverse Proxy**: `recipe:9000`
### Primary Use Cases
Use mealie as a central hub for discovering and accessing recipes in NetGrimoire.
The primary use case for the Mealie stack is to provide a centralized recipe management system for NetGrimoire users.
### NetGrimoire Integrations
mealie integrates with other services, including authentik for OIDC authentication.
The mealie stack integrates with other NetGrimoire services through environment variables and labels, including Authentik and Uptime Kuma.
---
## Operations
### Monitoring
[kuma monitors from kuma.* labels]
Kuma monitors the Mealie application's HTTP service.
```bash
docker stack services mealie
docker service logs -f mealie
```
### Backups
Critical data should be backed up to a separate volume. Reconstructing from backup is not recommended due to the potential loss of data.
Critical services are backed up by storing critical data in `/DockerVol/mealie`.
```bash
# No specific backup command needed
```
### Restore
Restore the Mealie application by redeploying the `mealie-stack.yml` file.
```bash
cd services/swarm/stack/mealie
./deploy.sh
@ -110,11 +117,25 @@ cd services/swarm/stack/mealie
---
## Common Failures
1. **Symptom:** Mealie application is not accessible.
**Cause:** Incorrect Caddy configuration or network issues.
**Fix:** Verify Caddy configuration and network connectivity.
| Symptom | Cause | Fix |
|---------|------|----|
- Service does not start | Insufficient resources | Scale service up |
- Recipe database is empty | No data has been added to the recipe database | Run `docker stack services mealie` and inspect for missing images |
2. **Symptom:** Recipe data is missing or corrupted.
**Cause:** Database issue or incorrect data import.
**Fix:** Investigate database issues and re-import recipe data.
3. **Symptom:** Mealie application crashes frequently.
**Cause:** Insufficient resources or faulty application code.
**Fix:** Increase resources for the application or investigate and fix application code issues.
4. **Symptom:** Uptime Kuma monitors are not displaying data.
**Cause:** Incorrect configuration or network connectivity issue.
**Fix:** Verify Uptime Kuma configuration and network connectivity.
5. **Symptom:** Mealie application is taking too long to load.
**Cause:** Inefficient database queries or resource-intensive tasks.
**Fix:** Optimize database queries and reduce resource usage.
---
@ -122,17 +143,17 @@ cd services/swarm/stack/mealie
| Date | Commit | Summary |
|------|--------|---------|
| 2026-04-15 | 966b86dd | Initial deployment |
| 2026-04-15 | b9007e9e | Fix issue with OIDC configuration |
| 2026-04-15 | 58549b2e | Update recipe image to latest version |
| 2026-04-15 | e79fb0ad | Added support for multiple user groups |
| 2026-04-15 | d2d9ac52 | Fixed issue with data volume permissions |
| 2026-04-15 | e7979588 | Updated Caddy configuration for better performance |
| 2026-04-15 | e7f6da52 | Added support for HTTPS |
| 2026-04-15 | 158547e8 | Fixed issue with logging configuration |
| 2026-04-15 | 7bf82e75 | Improved security settings for mealie |
| 2026-04-15 | 9bed890d | Initial documentation creation |
| 2026-04-15 | 966b86dd | Added environment variables for mealie stack |
| 2026-04-15 | b9007e9e | Updated Caddy configuration for mealie stack |
| 2026-04-15 | 58549b2e | Improved documentation formatting and organization |
| 2026-04-15 | e79fb0ad | Added Uptime Kuma monitor configuration |
**Summary:** The mealie stack has undergone several changes to improve its stability, security, and performance. Key updates include the addition of environment variables for better configuration management and improved Caddy configuration for enhanced security.
---
## Notes
Generated by Gremlin on 2026-04-15T23:27:38.111Z. Source: swarm/mealie.yaml. Review User Guide and Changelog sections.
- Generated by Gremlin on 2026-04-16T00:22:31.180Z
- Source: swarm/mealie.yaml
- Review User Guide and Changelog sections