Hello, I want to start by thanking you for all the work you have put in to komodo. I just found it a couple weeks ago and have been migrating my systems to it. I have been using systemd to run periphery per the recommendations that you and FoxxMD have made, but I don't think that is practical for the last couple of systems, so I had to dig into running periphery in a container and ran into a couple things that weren't clear to me and required some guess and check, so I'm submitting this PR to hopefully eliminate that uncertainty for people in the future.
Happy to take any feedback and make changes as you see fit.
🔄 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/moghtech/komodo/pull/402
**Author:** [@theRAAPster](https://github.com/theRAAPster)
**Created:** 4/9/2025
**Status:** ✅ Merged
**Merged:** 4/12/2025
**Merged by:** [@mbecker20](https://github.com/mbecker20)
**Base:** `1.17.1` ← **Head:** `update-periphery-container-docs`
---
### 📝 Commits (3)
- [`3df9292`](https://github.com/moghtech/komodo/commit/3df9292c8938ac1768031ef75c1011b9b40a4869) Add ports that need to be exposed if periphery is remote from core
- [`e113d15`](https://github.com/moghtech/komodo/commit/e113d1595be8c151659f5b244d1e6c8fa86be597) Spelling: overide -> override
- [`890e397`](https://github.com/moghtech/komodo/commit/890e397e2c4c58e95fad8ff14a5b1209dfcaccb2) Add info about using a custom config file when running periphery in docker
### 📊 Changes
**2 files changed** (+17 additions, -6 deletions)
<details>
<summary>View changed files</summary>
📝 `compose/periphery.compose.yaml` (+7 -1)
📝 `docsite/docs/connect-servers.mdx` (+10 -5)
</details>
### 📄 Description
Hello, I want to start by thanking you for all the work you have put in to komodo. I just found it a couple weeks ago and have been migrating my systems to it. I have been using systemd to run periphery per the recommendations that you and FoxxMD have made, but I don't think that is practical for the last couple of systems, so I had to dig into running periphery in a container and ran into a couple things that weren't clear to me and required some guess and check, so I'm submitting this PR to hopefully eliminate that uncertainty for people in the future.
Happy to take any feedback and make changes as you see fit.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/moghtech/komodo/pull/402
Author: @theRAAPster
Created: 4/9/2025
Status: ✅ Merged
Merged: 4/12/2025
Merged by: @mbecker20
Base:
1.17.1← Head:update-periphery-container-docs📝 Commits (3)
3df9292Add ports that need to be exposed if periphery is remote from coree113d15Spelling: overide -> override890e397Add info about using a custom config file when running periphery in docker📊 Changes
2 files changed (+17 additions, -6 deletions)
View changed files
📝
compose/periphery.compose.yaml(+7 -1)📝
docsite/docs/connect-servers.mdx(+10 -5)📄 Description
Hello, I want to start by thanking you for all the work you have put in to komodo. I just found it a couple weeks ago and have been migrating my systems to it. I have been using systemd to run periphery per the recommendations that you and FoxxMD have made, but I don't think that is practical for the last couple of systems, so I had to dig into running periphery in a container and ran into a couple things that weren't clear to me and required some guess and check, so I'm submitting this PR to hopefully eliminate that uncertainty for people in the future.
Happy to take any feedback and make changes as you see fit.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.