Bumps forgejo version from 10 -> 15 (current major)
Fixes ssh conflict with host default ssh listening port.
Current configuration prevents git push over ssh from working due to invalid rw privileges. Assuming host ssh server is listening on default port :22, DNS resolution to dokploy service domain will resolve to host IP address, ssh request will be routed to host ssh server instead of container ssh server.
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Issues related (if applicable)
Close automatically the related issues using the keywords: closes #ISSUE_NUMBER
Screenshots or Videos
🔄 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/Dokploy/templates/pull/880
**Author:** [@DiegoEnriquezSerrano](https://github.com/DiegoEnriquezSerrano)
**Created:** 5/19/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `update-forgejo-template`
---
### 📝 Commits (3)
- [`8b7cd62`](https://github.com/Dokploy/templates/commit/8b7cd62c57fee1f374f81ee4a5c4e06492986115) Update forgejo template; bumps Forgejo version to 15; fixes git push over ssh
- [`bedd98c`](https://github.com/Dokploy/templates/commit/bedd98c6ba68de35391610b1fd50af03e06e5e5a) updates template compose and toml to use internal port mapping
- [`16194df`](https://github.com/Dokploy/templates/commit/16194df3ad133d129c1f5fd74c173fa15206d037) Merge remote-tracking branch 'origin/canary' into update-forgejo-template
### 📊 Changes
**3 files changed** (+28 additions, -11 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/forgejo/docker-compose.yml` (+12 -9)
📝 `blueprints/forgejo/meta.json` (+1 -1)
📝 `blueprints/forgejo/template.toml` (+15 -1)
</details>
### 📄 Description
## What is this PR about?
* Bumps forgejo version from `10` -> `15` (current major)
* Fixes ssh conflict with host default ssh listening port.
* Current configuration prevents `git push` over ssh from working due to invalid rw privileges. Assuming host ssh server is listening on default port `:22`, DNS resolution to dokploy service domain will resolve to host IP address, ssh request will be routed to host ssh server instead of container ssh server.
## Checklist
Before submitting this PR, please make sure that:
- [ x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [ ] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [ ] I have added tests that demonstrate that my correction works or that my new feature works.
## Issues related (if applicable)
Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER`
## Screenshots or Videos
---
<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/Dokploy/templates/pull/880
Author: @DiegoEnriquezSerrano
Created: 5/19/2026
Status: 🔄 Open
Base:
canary← Head:update-forgejo-template📝 Commits (3)
8b7cd62Update forgejo template; bumps Forgejo version to 15; fixes git push over sshbedd98cupdates template compose and toml to use internal port mapping16194dfMerge remote-tracking branch 'origin/canary' into update-forgejo-template📊 Changes
3 files changed (+28 additions, -11 deletions)
View changed files
📝
blueprints/forgejo/docker-compose.yml(+12 -9)📝
blueprints/forgejo/meta.json(+1 -1)📝
blueprints/forgejo/template.toml(+15 -1)📄 Description
What is this PR about?
10->15(current major)git pushover ssh from working due to invalid rw privileges. Assuming host ssh server is listening on default port:22, DNS resolution to dokploy service domain will resolve to host IP address, ssh request will be routed to host ssh server instead of container ssh server.Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Close automatically the related issues using the keywords:
closes #ISSUE_NUMBERScreenshots or Videos
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.