mirror of
https://github.com/frappe/frappe_docker.git
synced 2026-06-17 05:45:09 +00:00
fix: Added missing title metadata
New files didn't have YAML metadata, it is added now.
This commit is contained in:
parent
208aa7b7f4
commit
bb06d6bb09
6 changed files with 24 additions and 0 deletions
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: Choosing a Method
|
||||
---
|
||||
|
||||
# Choosing a Deployment or Development Method
|
||||
|
||||
This repository (`frappe_docker`) supports **multiple ways to run Frappe using Docker**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: Docker Immutability
|
||||
---
|
||||
|
||||
# Important Concept: Immutability and Persistence
|
||||
|
||||
A frequent source of confusion is how **Docker-based Frappe deployments handle persistence**.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: Single Server Example
|
||||
---
|
||||
|
||||
# Single Server Example (nginx-proxy + acme-companion)
|
||||
|
||||
This guide demonstrates a single-server setup using nginx-proxy and acme-companion for HTTPS. It is best for a small number of hostnames and a single bench. If you need multiple benches or advanced routing, use the Traefik-based example instead.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: NGINX and ACME Companion
|
||||
---
|
||||
|
||||
# nginx-proxy + acme-companion (HTTPS)
|
||||
|
||||
This guide explains how to use nginx-proxy with acme-companion to provide HTTPS for a Frappe Docker stack.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: Caddy with HTTPS
|
||||
---
|
||||
|
||||
# Caddy reverse proxy (local HTTPS)
|
||||
|
||||
This guide shows how to use Caddy as an external reverse proxy in front of the frontend container. It is most useful for local HTTPS or internal networks.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,7 @@
|
|||
---
|
||||
title: Migrate Traefik from v2 to v3
|
||||
---
|
||||
|
||||
# Migrate an existing Traefik v2 instance to v3
|
||||
|
||||
Use this guide if you already run Traefik v2 with `frappe_docker` and want to upgrade to v3. It focuses on the image upgrade and the v3 routing rule changes that affect existing setups.
|
||||
|
|
|
|||
Loading…
Reference in a new issue