What's Changed

• Add web hook verification to GitHub Autodeploy by @slowlydev in #189
• feat(github-webhooks): #186 implement github autodeployment with zero… by @Siumauricio in #188
• chore: bump nocodb template version by @DarkPhoenix2704 in #191
• fix(git): set 22 port in git add host by @Siumauricio in #193
• feat(open-webui): add open-webui template by @kucherenko in #192
• fix(registry): remove login on self hosted by @Siumauricio in #196
• v0.3.1 by @Siumauricio in #197

New Contributors

• @slowlydev made their first contribution in #189
• @kucherenko made their first contribution in #192

Full Changelog: v0.3.0...v0.3.1

What's Changed

• chore: remove row selection count by @ephraimduncan in #178
• fix: avoid black background on light theme by @ephraimduncan in #177
• fix: avoid using defined secrets in calcom template by @ephraimduncan in #176
• feat: add documenso as template by @ephraimduncan in #175
• feat: nocodb template by @DarkPhoenix2704 in #182
• Feat/templates by @Siumauricio in #180
• feat: add glitchtip template by @Siumauricio in #184
• v0.3.0 by @Siumauricio in #185

New templates

1. Documenso
2. Glitchtip
3. NocoDB
4. appsmith
5. baserow
6. directus
7. excalidraw
8. ghost
9. grafana
10. n8n
11. odoo
12. uptime-kuma
13. wordpress
14. phpmyadmin
15. rocketchat
16. minio
17. metabase
18. meilisearch

New Contributors

• @ephraimduncan made their first contribution in #178
• @DarkPhoenix2704 made their first contribution in #182

Full Changelog: v0.2.5...v0.3.0

What's Changed

• fix: make databases be only available in manager by @Siumauricio in #162
• 40 feature request automatically generates domains by @Siumauricio in #163
• 147 add commit hash and commit message in the deployment list by @Siumauricio in #170
• refactor(#168): make project card be clickable everywhere by @Siumauricio in #171
• fix(#167): pass args in redis to require pass by @Siumauricio in #172
• fix(API): integrate next handler for swagger UI by @Siumauricio in #173
• v0.2.5 by @Siumauricio in #174

Domain generation

Watch a preview how easy is to generate a domain and see the your application fast and easy

Full Changelog: v0.2.4...v0.2.5

What's Changed

• 57 dokploy api or cli by @Siumauricio in #158
• v0.2.4 by @Siumauricio in #161

Features 🎊🎊🎊

1. We're excited to introduce Swagger OpenAPI documentation for Dokploy. This addition significantly enhances our API's usability and accessibility.

API Documentation: For comprehensive information on how to use our API, please visit our API documentation page.

2. New Command Line Interface (CLI)
   We've launched a new CLI to streamline your workflow and provide more flexibility in interacting with Dokploy.

CLI Guide: To learn how to leverage our new CLI, check out our CLI documentation.

Full Changelog: v0.2.3...v0.2.4

What's Changed

• Fix link to docs in README by @dharsanb in #137
• fix: env editor width overflow by @hehehai in #141
• fix(#149): use database user in mongodump by @Siumauricio in #150
• v0.2.3 by @Siumauricio in #156

New Contributors

• @dharsanb made their first contribution in #137

Full Changelog: v0.2.2...v0.2.3

What's Changed

• Updated the database view to hide the password in the connection string by @mariusihring in #128
• feat(#130): allow to pass enviroment variables to assign custom port … by @Siumauricio in #135
• feat: server support custom name by @hehehai in #87
• v0.2.2 by @Siumauricio in #136

Full Changelog: v0.2.1...v0.2.2

What's Changed

• fix(#119): remove none ports by @Siumauricio in #121
• refactor(#118): remove last toaster on start deployments by @Siumauricio in #122
• fix(#125): Use exec async and password stnd to automatically save in … by @Siumauricio in #126

Full Changelog: v0.2.0...v0.2.1

What's Changed 🎊🎊

• Docker compose support by @Siumauricio in #111
• Add calcom, pocketbase and plausible templates to the directory
  

Docker Compose Support

We introduce docker compose support, deploy applications from your github or deploy templates open source easily.

Documentation: https://docs.dokploy.com/docker-compose/overview

Note Atention:

For new installations this problem has been adressed

We need to add the docker provider to traefik, this in order to enable templates and docker compose routing, please do the following:

1. Go to /dashboard/traefik
2. Select traefik.yml
3. You will have this code

- providers:
-  file:
-    directory: /etc/dokploy/traefik/dynamic
-    watch: true
+ providers:
+ docker:
+    exposedByDefault: false
+  file:
+    directory: /etc/dokploy/traefik/dynamic
+    watch: true

in the entrypoints

- entryPoints:
-  web:
-    address: ':80'
-    http:
-      redirections:
-        entryPoint:
-          to: websecure
-          scheme: https
-          permanent: true
+ entryPoints:
+  web:
+   address: ':80'

So at the end your traefik.yml should look like this, don't forget to restart the traefik, go to /dashboard/settings/server/ -> traefik then reload to take the new changes

Full Changelog: v0.1.0...v0.2.0

What's Changed

• feat: appearance theme support system config by @hehehai in #104
• fix(README-ru): hyperlink-ed docs url by @bayram-dev in #106
• feat: (#107) webhook listener filter docker events based on image tag. by @hikinine in #108
• Feat/multi node support by @Siumauricio in #96
• feat: support code editor by @hehehai in #105

Multi node support

We introduce multi node support to link multiples servers and join them to a dokploy server.

Documentation: https://docs.dokploy.com/cluster/overview

⚠️ Note Atention:

Initially, in the installation that we had initially, we in the docker swarm used 127.0.0.0.0 to initialize the docker swarm orchestration, this is a problem if you really want to use the multinode because you can not use 127.0.0.0. as ip to be able to connect to other servers, therefore it is necessary to assign the public IP of your VPS when initializing the docker swarm network, we understand that this can be a downtime for a few seconds until all your applications get deploy, we know is not a ideal way for many people who really want to use it, but it is the only way to make sure that the multinode works correctly, if you really don't have the interest/want to use the multinode support, all right you don't have to do anything, your applications will continue to work the same way, but if you want to use it follow the next steps:

For new installations this problem has been adressed

1. Keep in mind that executing this command will delete all your services, but your information will be persistent as databases and others, so you will have a drop of all your applications and databases until dokploy initialize and manually you deploy your applications, you will have the same information exactly as you left it so you should not have any problem when deploying.

Just copy and paste this command!

docker swarm leave --force 2>/dev/null; advertise_addr=$(curl -s ifconfig.me); docker swarm init --advertise-addr $advertise_addr; echo "Swarm initialized"; docker network rm -f dokploy-network 2>/dev/null; docker network create --driver overlay --attachable dokploy-network; docker pull dokploy/dokploy:latest; docker service create --name dokploy --replicas 1 --network dokploy-network --mount type=bind,source=/var/run/docker.sock,target=/var/run/docker.sock --mount type=bind,source=/etc/dokploy,target=/etc/dokploy --publish published=3000,target=3000,mode=host --update-parallelism 1 --update-order stop-first dokploy/dokploy:latest

New Contributors

• @bayram-dev made their first contribution in #106
• @hikinine made their first contribution in #108

Full Changelog: v0.0.4...v0.1.0

What's Changed

• docs: reset password command fix by @hehehai in #75
• Modify README.md to support Chinese by @kwxmxb in #68
• Added German Readme by @DontFred in #83
• Added Russian readme file by @Mr1Blaze in #89
• fix: dashboard layout styles by @hehehai in #86
• fix(#93): extract all branches from repository by @Siumauricio in #95
• fix(#100): Remove published port in the redis database to be not expo… by @Siumauricio in #102
• Added new tested system by @Mr1Blaze in #101
• v0.0.4 by @Siumauricio in #103

Note

Initially when dokploy was installed by mistake we exposed the port of the redis database which is the one we use to make queues to the deployments, in this update we corrected that error, to apply the changes it is necessary to do the following:

1. Go to your server
2. run this command docker service rm dokploy-redis
3. go to your dokploy panel -> settings -> server -> reload (this will make to recreate the redis instance without the port exposed)

New Contributors

• @hehehai made their first contribution in #75
• @kwxmxb made their first contribution in #68
• @DontFred made their first contribution in #83
• @Mr1Blaze made their first contribution in #89

Full Changelog: v0.0.3...v0.0.4