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, fixes #ISSUE_NUMBER, resolves #ISSUE_NUMBER
Example: closes #123
🔄 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/234
**Author:** [@frnikho](https://github.com/frnikho)
**Created:** 7/17/2025
**Status:** ✅ Merged
**Merged:** 7/21/2025
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `main` ← **Head:** `feat/usememos`
---
### 📝 Commits (4)
- [`64864cd`](https://github.com/Dokploy/templates/commit/64864cd0168acb922d208a357c488ded252dbfc7) Add Memos service and configuration files
- [`2c936aa`](https://github.com/Dokploy/templates/commit/2c936aaf6701adfe19e89ff59790e5e39761fb56) Refactor docker-compose.yml: update environment variable syntax for Memos service
- [`cca3ad8`](https://github.com/Dokploy/templates/commit/cca3ad804a873f999098c78a05067af1e89d9a8f) Update docker-compose.yml and template.toml: adjust environment variable syntax and change MEMOS_MODE value
- [`7ea8208`](https://github.com/Dokploy/templates/commit/7ea82081bbf3c7b7fa3ea7df7e6b5436c7e7738b) Add GitLab CE entry to meta.json and update Memos version to latest
### 📊 Changes
**4 files changed** (+59 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/memos/docker-compose.yml` (+15 -0)
➕ `blueprints/memos/memos.png` (+0 -0)
➕ `blueprints/memos/template.toml` (+14 -0)
📝 `meta.json` (+30 -0)
</details>
### 📄 Description
## What is this PR about?
New PR of Memos
## 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-suggestions-when-creating-a-template
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [x] 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`, `fixes #ISSUE_NUMBER`, `resolves #ISSUE_NUMBER`
Example: `closes #123`
---
<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/234
Author: @frnikho
Created: 7/17/2025
Status: ✅ Merged
Merged: 7/21/2025
Merged by: @Siumauricio
Base:
main← Head:feat/usememos📝 Commits (4)
64864cdAdd Memos service and configuration files2c936aaRefactor docker-compose.yml: update environment variable syntax for Memos servicecca3ad8Update docker-compose.yml and template.toml: adjust environment variable syntax and change MEMOS_MODE value7ea8208Add GitLab CE entry to meta.json and update Memos version to latest📊 Changes
4 files changed (+59 additions, -0 deletions)
View changed files
➕
blueprints/memos/docker-compose.yml(+15 -0)➕
blueprints/memos/memos.png(+0 -0)➕
blueprints/memos/template.toml(+14 -0)📝
meta.json(+30 -0)📄 Description
What is this PR about?
New PR of Memos
Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Close automatically the related issues using the keywords:
closes #ISSUE_NUMBER,fixes #ISSUE_NUMBER,resolves #ISSUE_NUMBERExample:
closes #123🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.