starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-25 11:20:56 +03:00
Code Issues 42 Packages Projects Releases 12 Wiki Activity

[PR #432] [CLOSED] Add MariaDB Changes, Split out Caddy to it's own container #758

New Issue
Closed
opened 2026-02-04 18:48:30 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 18:48:30 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/432
Author: @luthes
Created: 6/26/2024
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (10+)

📊 Changes

9 files changed (+313 additions, -178 deletions)

View changed files

➕ .dockerignore (+10 -0)
➕ .env.docker (+3 -0)
📝 .github/docker/entrypoint.sh (+20 -52)
➕ Caddyfile (+11 -0)
📝 Dockerfile (+53 -38)
➕ compose.yml (+54 -0)
📝 composer.json (+1 -2)
📝 composer.lock (+158 -85)
📝 config/database.php (+3 -1)

📄 Description

Lance and I worked on this a bit this evening. There may be some work left to do here, but this essentially splits Caddy, the Panel, and adds in the MariaDB database. A docker compose up in the main directory will get it running. I'll work on adding Redis next.

I think splitting this out to a full cluster setup, and something a bit more like what Lance had in the original PR with a single container/sqlite is a good idea. Maybe something like compose-cluster.yml, compose[-sqlite].yml, and flagging compose-cluster.yml as a more advanced setup option might be a good idea.

Apologies for the second PR. I based this branch off of Lance's issue/311 PR, but it needs a sync to main, and this can be pointed back over there without being too messy.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pelican-dev/panel/pull/432 **Author:** [@luthes](https://github.com/luthes) **Created:** 6/26/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (10+) - [`5772820`](https://github.com/pelican-dev/panel/commit/577282094271076ac0977d8cc0fbcaaae46ba559) Add some docker - [`e4e1733`](https://github.com/pelican-dev/panel/commit/e4e1733c3d6073baba16435d1771c2670fd01dd7) Don’t include this - [`de2491e`](https://github.com/pelican-dev/panel/commit/de2491e15f79e7144b90859d183a057d8b5aa2c9) Fix missing route files - [`efbcd21`](https://github.com/pelican-dev/panel/commit/efbcd21861a3dc81585ec60a0edbc9862469fbaf) Use variables - [`1ce7225`](https://github.com/pelican-dev/panel/commit/1ce72254df9766f609f2ceebf898e5bfd6073a70) Allow both relative and absolute paths - [`1a60eac`](https://github.com/pelican-dev/panel/commit/1a60eacdec59da8fdd6b7518225d7d8494532fca) Already have defaults - [`44a97be`](https://github.com/pelican-dev/panel/commit/44a97be18d719593181cf2fa520597fb3a06cf42) Docker - [`f7bd576`](https://github.com/pelican-dev/panel/commit/f7bd5763375ab2370520adc8868b8a1175bd74a6) Remove old one - [`f58afcd`](https://github.com/pelican-dev/panel/commit/f58afcd4f46ecf93f9629f4445396d14b551ffd8) Use this one primarily - [`8e64c8d`](https://github.com/pelican-dev/panel/commit/8e64c8df703ec42ef8ebe3da1e689fedee90553a) Update variables ### 📊 Changes **9 files changed** (+313 additions, -178 deletions) <details> <summary>View changed files</summary> ➕ `.dockerignore` (+10 -0) ➕ `.env.docker` (+3 -0) 📝 `.github/docker/entrypoint.sh` (+20 -52) ➕ `Caddyfile` (+11 -0) 📝 `Dockerfile` (+53 -38) ➕ `compose.yml` (+54 -0) 📝 `composer.json` (+1 -2) 📝 `composer.lock` (+158 -85) 📝 `config/database.php` (+3 -1) </details> ### 📄 Description Lance and I worked on this a bit this evening. There may be some work left to do here, but this essentially splits Caddy, the Panel, and adds in the MariaDB database. A `docker compose up` in the main directory will get it running. I'll work on adding Redis next. I think splitting this out to a full cluster setup, and something a bit more like what Lance had in the original PR with a single container/sqlite is a good idea. Maybe something like compose-cluster.yml, compose[-sqlite].yml, and flagging compose-cluster.yml as a more advanced setup option might be a good idea. Apologies for the second PR. I based this branch off of Lance's issue/311 PR, but it needs a sync to main, and this can be pointed back over there without being too messy. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 18:48:30 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#758
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?