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

docs(gremlin): update mealie

Browse source
This commit is contained in:
traveler 2026-04-15 19:50:31 -05:00
parent 32baa7b519
commit f66bfd6683
1 changed files with 25 additions and 47 deletions
Download patch file Download diff file Expand all files Collapse all files

72
Netgrimoire/Services/mealie/mealie.md
View file

@ -1,26 +1,24 @@
---
title: mealie Stack
description: Recipe Manager for NetGrimoire
description: Recipe Manager
published: true
date: 2026-04-16T00:22:31.180Z
date: 2026-04-16T00:48:24.314Z
tags: docker,swarm,mealie,netgrimoire
editor: markdown
dateCreated: 2026-04-16T00:22:31.180Z
dateCreated: 2026-04-16T00:48:24.314Z
---
# mealie
## Overview
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.
---
The mealie stack is a Docker Swarm-based service that manages recipes and provides a user interface for users to interact with them. This stack consists of the mealie service, which handles all aspects of recipe management.
## Architecture
| Service | Image | Port | Role |
|---------|-----|-----|---------|
|---------|-----|-----|-----|
- **Host:** docker4
- **Network:** netgrimoire
- **Exposed via:** `recipe:9000`
- **Exposed via:** caddy:9000, Internal only
- **Homepage group:** PNCHarris Apps
---
@ -28,11 +26,11 @@ The mealie stack provides a Recipe Manager for NetGrimoire, allowing users to ma
## Build & Configuration
### Prerequisites
No specific prerequisites are required for this stack.
No specific prerequisites for this stack.
### Volume Setup
```bash
mkdir -p /DockerVol/mealie
mkdir -p /DockerVol/mealie:/app/data
```
### Environment Variables
@ -73,7 +71,7 @@ docker stack services mealie
```
### First Run
After deployment, verify that the Mealie application is accessible and functioning correctly.
Perform any necessary steps after deploying the service, such as setting up initial data.
---
@ -82,33 +80,29 @@ After deployment, verify that the Mealie application is accessible and functioni
### Accessing mealie
| Service | URL | Purpose |
|---------|-----|---------|
- **Mealie**: `https://recipe.netgrimoire.com`
- **Caddy Reverse Proxy**: `recipe:9000`
- **Caddy:** recipe.netgrimoire.com:9000
### Primary Use Cases
The primary use case for the Mealie stack is to provide a centralized recipe management system for NetGrimoire users.
Describe how to use the mealie stack in NetGrimoire, including any specific workflows or features.
### NetGrimoire Integrations
The mealie stack integrates with other NetGrimoire services through environment variables and labels, including Authentik and Uptime Kuma.
List any other services that this connects to through environment variables or labels.
---
## Operations
### Monitoring
Kuma monitors the Mealie application's HTTP service.
[kuma monitors from kuma.* labels]
```bash
docker stack services mealie
<docker service logs commands>
```
### Backups
Critical services are backed up by storing critical data in `/DockerVol/mealie`.
```bash
# No specific backup command needed
```
Critical vs reconstructable /DockerVol/ paths for backup considerations.
### Restore
Restore the Mealie application by redeploying the `mealie-stack.yml` file.
```bash
cd services/swarm/stack/mealie
./deploy.sh
@ -117,25 +111,9 @@ 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.
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.
| Symptom | Cause | Fix |
|---------|------|-----|
| <insert symptoms> | <insert cause> | <insert fix> |
---
@ -143,17 +121,17 @@ cd services/swarm/stack/mealie
| Date | Commit | Summary |
|------|--------|---------|
| 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 |
| 2026-04-15 | 765f47e1 | <infer what changed from the diffs above> |
| 2026-04-15 | 9bed890d | <infer what changed from the diffs above> |
| 2026-04-15 | 966b86dd | <infer what changed from the diffs above> |
| 2026-04-15 | b9007e9e | <infer what changed from the diffs above> |
| 2026-04-15 | 58549b2e | <infer what changed from the diffs above> |
**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.
<Write a paragraph summarizing the evolution of this service based on the diffs above. If no diffs available, note that this is the initial documentation.>
---
## Notes
- Generated by Gremlin on 2026-04-16T00:22:31.180Z
- Generated by Gremlin on 2026-04-16T00:48:24.314Z
- Source: swarm/mealie.yaml
- Review User Guide and Changelog sections