Adds a high-performance, open-source sync engine (ElectricSQL) allowing users to bypass cloud quotas and host their own real-time local-first PostgreSQL synchronization.
Template features:
Includes template.toml structured variables with autocomplete UI.
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)
N/A
Screenshots or Videos
(You can drag and drop a screenshot of the ElectricSQL dashboard here later if Dokploy asks for one, but it's optional!)
Greptile Summary
This PR adds an ElectricSQL blueprint template to the Dokploy template collection, providing a self-hosted sync engine for PostgreSQL. The overall structure is reasonable, but there are several blocking issues that need to be resolved before merging.\n\nKey issues found:\n\n- Broken logo file (blueprints/electric-sql/logo.svg): The file contains the literal text 404: Not Found rather than valid SVG content. The logo was never successfully sourced and must be replaced with the actual ElectricSQL SVG logo.\n- Accidental Strapi deletion (meta.json): The existing strapi template entry has been inadvertently removed. This is an unrelated change that will break the Strapi template for all users — it must be restored.\n- Unpinned Docker image tag: electricsql/electric:latest should be pinned to the specific version referenced in meta.json (1.4.15) to ensure reproducibility and prevent supply chain risk (per AGENTS.md).\n- Service name mismatch: The service is named electric in docker-compose.yml and template.toml, but AGENTS.md requires the service name to match the blueprint folder name exactly (electric-sql).
Confidence Score: 1/5
Not safe to merge — contains a broken logo file, an accidental deletion of an unrelated template (Strapi), and a non-compliant unpinned image tag.
Three separate blocking issues exist: a completely invalid logo asset, an unintended removal of the Strapi entry from meta.json (which would break an existing live template), and an unpinned Docker image tag against explicit project policy. These must all be fixed before the PR can be merged safely.
All four changed files require attention: logo.svg (broken content), docker-compose.yml (unpinned image, wrong service name), template.toml (service name mismatch), and meta.json (accidental Strapi deletion).
Important Files Changed
Filename
Overview
blueprints/electric-sql/logo.svg
File contains literal '404: Not Found' text instead of valid SVG content — the logo was never successfully sourced.
blueprints/electric-sql/docker-compose.yml
Service name 'electric' does not match blueprint folder 'electric-sql' (violates AGENTS.md naming rule), and image uses unpinned 'latest' tag instead of the specific version referenced in meta.json.
blueprints/electric-sql/template.toml
Variable definitions and domain config look reasonable; serviceName should be updated to 'electric-sql' to match the folder name once docker-compose.yml is fixed.
meta.json
Adds the electric-sql entry correctly, but accidentally removes the unrelated Strapi template entry — a significant unintended deletion.
This PR removes the existing strapi entry from meta.json, which is completely unrelated to adding ElectricSQL. Strapi is an established template in the repository and should not be removed. This looks like an unintentional edit — perhaps a copy/paste or merge conflict that deleted this block.
The Strapi entry (with id: "strapi", name: "Strapi", etc.) needs to be restored.
🔄 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/754
**Author:** [@ahmed-lotfy-dev](https://github.com/ahmed-lotfy-dev)
**Created:** 3/26/2026
**Status:** ❌ Closed
**Base:** `canary` ← **Head:** `feat/add-electric-sql-template`
---
### 📝 Commits (3)
- [`8dedee8`](https://github.com/Dokploy/templates/commit/8dedee8c48188266b4a1ae1b094bd146fed42771) feat: add electric-sql blueprint template
- [`63a2703`](https://github.com/Dokploy/templates/commit/63a27039d43ab4f2728aa7a5a19f98891c380b06) fix: add domain variable and fix env format in electric-sql template
- [`85d3b2c`](https://github.com/Dokploy/templates/commit/85d3b2c330910311ccd67f5ed64dddf554ef373d) fix: remove config.mounts from electric-sql template
### 📊 Changes
**4 files changed** (+54 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/electric-sql/docker-compose.yml` (+17 -0)
➕ `blueprints/electric-sql/logo.svg` (+1 -0)
➕ `blueprints/electric-sql/template.toml` (+18 -0)
📝 `meta.json` (+18 -18)
</details>
### 📄 Description
## What is this PR about?
New PR of [ElectricSQL]
Adds a high-performance, open-source sync engine (ElectricSQL) allowing users to bypass cloud quotas and host their own real-time local-first PostgreSQL synchronization.
Template features:
- Includes [template.toml](cci:7://file:///mnt/hdd/projects/my-skills-folder/export-dokploy-templates/electric-sql/template.toml:0:0-0:0) structured variables with autocomplete UI.
- Conforms to Dokploy's `container_name` and [docker-compose.yml](cci:7://file:///mnt/hdd/projects/my-skills-folder/export-dokploy-templates/electric-sql/docker-compose.yml:0:0-0:0) guidelines.
- Uses dynamic password helpers for `ELECTRIC_SECRET`.
## 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
- [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)
N/A
## Screenshots or Videos
*(You can drag and drop a screenshot of the ElectricSQL dashboard here later if Dokploy asks for one, but it's optional!)*
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds an ElectricSQL blueprint template to the Dokploy template collection, providing a self-hosted sync engine for PostgreSQL. The overall structure is reasonable, but there are several blocking issues that need to be resolved before merging.\n\n**Key issues found:**\n\n- **Broken logo file** (`blueprints/electric-sql/logo.svg`): The file contains the literal text `404: Not Found` rather than valid SVG content. The logo was never successfully sourced and must be replaced with the actual ElectricSQL SVG logo.\n- **Accidental Strapi deletion** (`meta.json`): The existing `strapi` template entry has been inadvertently removed. This is an unrelated change that will break the Strapi template for all users — it must be restored.\n- **Unpinned Docker image tag**: `electricsql/electric:latest` should be pinned to the specific version referenced in `meta.json` (`1.4.15`) to ensure reproducibility and prevent supply chain risk (per `AGENTS.md`).\n- **Service name mismatch**: The service is named `electric` in `docker-compose.yml` and `template.toml`, but `AGENTS.md` requires the service name to match the blueprint folder name exactly (`electric-sql`).
<h3>Confidence Score: 1/5</h3>
Not safe to merge — contains a broken logo file, an accidental deletion of an unrelated template (Strapi), and a non-compliant unpinned image tag.
Three separate blocking issues exist: a completely invalid logo asset, an unintended removal of the Strapi entry from meta.json (which would break an existing live template), and an unpinned Docker image tag against explicit project policy. These must all be fixed before the PR can be merged safely.
All four changed files require attention: `logo.svg` (broken content), `docker-compose.yml` (unpinned image, wrong service name), `template.toml` (service name mismatch), and `meta.json` (accidental Strapi deletion).
<details><summary><h3>Important Files Changed</h3></summary>
| Filename | Overview |
|----------|----------|
| blueprints/electric-sql/logo.svg | File contains literal '404: Not Found' text instead of valid SVG content — the logo was never successfully sourced. |
| blueprints/electric-sql/docker-compose.yml | Service name 'electric' does not match blueprint folder 'electric-sql' (violates AGENTS.md naming rule), and image uses unpinned 'latest' tag instead of the specific version referenced in meta.json. |
| blueprints/electric-sql/template.toml | Variable definitions and domain config look reasonable; serviceName should be updated to 'electric-sql' to match the folder name once docker-compose.yml is fixed. |
| meta.json | Adds the electric-sql entry correctly, but accidentally removes the unrelated Strapi template entry — a significant unintended deletion. |
</details>
</details>
<!-- greptile_failed_comments -->
<details><summary><h3>Comments Outside Diff (1)</h3></summary>
1. `meta.json`, line 5970-5987 ([link](https://github.com/dokploy/templates/blob/ea6e8b07087ecf746814d4a1f1c075051567b82e/meta.json#L5970-L5987))
<a href="#"><img alt="P0" src="https://greptile-static-assets.s3.amazonaws.com/badges/p0.svg?v=7" align="top"></a> **Strapi entry accidentally deleted**
This PR removes the existing `strapi` entry from `meta.json`, which is completely unrelated to adding ElectricSQL. Strapi is an established template in the repository and should not be removed. This looks like an unintentional edit — perhaps a copy/paste or merge conflict that deleted this block.
The Strapi entry (with `id: "strapi"`, `name: "Strapi"`, etc.) needs to be restored.
</details>
<!-- /greptile_failed_comments -->
<sub>Reviews (1): Last reviewed commit: ["feat: add electric-sql blueprint templat..."](https://github.com/dokploy/templates/commit/ea6e8b07087ecf746814d4a1f1c075051567b82e) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=26434557)</sub>
> Greptile also left **3 inline comments** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Context used - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<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/754
Author: @ahmed-lotfy-dev
Created: 3/26/2026
Status: ❌ Closed
Base:
canary← Head:feat/add-electric-sql-template📝 Commits (3)
8dedee8feat: add electric-sql blueprint template63a2703fix: add domain variable and fix env format in electric-sql template85d3b2cfix: remove config.mounts from electric-sql template📊 Changes
4 files changed (+54 additions, -18 deletions)
View changed files
➕
blueprints/electric-sql/docker-compose.yml(+17 -0)➕
blueprints/electric-sql/logo.svg(+1 -0)➕
blueprints/electric-sql/template.toml(+18 -0)📝
meta.json(+18 -18)📄 Description
What is this PR about?
New PR of [ElectricSQL]
Adds a high-performance, open-source sync engine (ElectricSQL) allowing users to bypass cloud quotas and host their own real-time local-first PostgreSQL synchronization.
Template features:
container_nameand docker-compose.yml guidelines.ELECTRIC_SECRET.Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
N/A
Screenshots or Videos
(You can drag and drop a screenshot of the ElectricSQL dashboard here later if Dokploy asks for one, but it's optional!)
Greptile Summary
This PR adds an ElectricSQL blueprint template to the Dokploy template collection, providing a self-hosted sync engine for PostgreSQL. The overall structure is reasonable, but there are several blocking issues that need to be resolved before merging.\n\nKey issues found:\n\n- Broken logo file (
blueprints/electric-sql/logo.svg): The file contains the literal text404: Not Foundrather than valid SVG content. The logo was never successfully sourced and must be replaced with the actual ElectricSQL SVG logo.\n- Accidental Strapi deletion (meta.json): The existingstrapitemplate entry has been inadvertently removed. This is an unrelated change that will break the Strapi template for all users — it must be restored.\n- Unpinned Docker image tag:electricsql/electric:latestshould be pinned to the specific version referenced inmeta.json(1.4.15) to ensure reproducibility and prevent supply chain risk (perAGENTS.md).\n- Service name mismatch: The service is namedelectricindocker-compose.ymlandtemplate.toml, butAGENTS.mdrequires the service name to match the blueprint folder name exactly (electric-sql).Confidence Score: 1/5
Not safe to merge — contains a broken logo file, an accidental deletion of an unrelated template (Strapi), and a non-compliant unpinned image tag.
Three separate blocking issues exist: a completely invalid logo asset, an unintended removal of the Strapi entry from meta.json (which would break an existing live template), and an unpinned Docker image tag against explicit project policy. These must all be fixed before the PR can be merged safely.
All four changed files require attention:
logo.svg(broken content),docker-compose.yml(unpinned image, wrong service name),template.toml(service name mismatch), andmeta.json(accidental Strapi deletion).Important Files Changed
Comments Outside Diff (1)
meta.json, line 5970-5987 (link)This PR removes the existing
strapientry frommeta.json, which is completely unrelated to adding ElectricSQL. Strapi is an established template in the repository and should not be removed. This looks like an unintentional edit — perhaps a copy/paste or merge conflict that deleted this block.The Strapi entry (with
id: "strapi",name: "Strapi", etc.) needs to be restored.Reviews (1): Last reviewed commit: "feat: add electric-sql blueprint templat..." | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.