Skip to content

Releases: Dokploy/dokploy

v0.2.3

21 Jun 22:18
fe22890
Compare
Choose a tag to compare

What's Changed

New Contributors

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

v0.2.2

09 Jun 07:56
2b7c763
Compare
Choose a tag to compare

What's Changed

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

v0.2.1

07 Jun 18:40
1b7244e
Compare
Choose a tag to compare

What's Changed

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

v0.2.0

03 Jun 05:25
Compare
Choose a tag to compare

What's Changed 🎊🎊

  • Docker compose support by @Siumauricio in #111
  • Add calcom, pocketbase and plausible templates to the directory
    Screenshot 2024-06-02 at 11 24 26 PM

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

Screenshot 2024-06-02 at 11 22 44 PM

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

v0.1.0

30 May 07:02
2902281
Compare
Choose a tag to compare

What's Changed

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

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

v0.0.4

23 May 06:00
56a94ad
Compare
Choose a tag to compare

What's Changed

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

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

v0.0.3

10 May 08:27
17da902
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.0.2...v0.0.3

v0.0.2

05 May 19:28
2541832
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.0.1...v0.0.2

v0.0.1

02 May 03:48
de278d9
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: https://github.com/Dokploy/dokploy/commits/v0.0.1