v0.1.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

v0.0.4

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

v0.0.3

What's Changed

• Correct server port log for non 3000 port by @oesukam in #59
• Correct Postgres url from password:password to user:password by @vkrusen in #60
• fix: Properly parse environment variables by @manjime83 in #67
• v0.0.3 by @Siumauricio in #69

New Contributors

• @oesukam made their first contribution in #59
• @vkrusen made their first contribution in #60
• @manjime83 made their first contribution in #67

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

v0.0.2

What's Changed

• fix: typo in index.ts by @eltociear in #26
• feat: Update build.sh to provide arm64, aarch64 and x86 images by @mariusihring in #37
• fix: prevent to have empty traefik config in order to prevent domain… by @Siumauricio in #44
• revert: back to next 14 and remove arm/v7 due to unsuported versions … by @Siumauricio in #45
• fix(#42): initialize the database as a first service by @Siumauricio in #48
• v0.0.2 by @Siumauricio in #50

New Contributors

• @eltociear made their first contribution in #26
• @mariusihring made their first contribution in #37

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

v0.0.1

What's Changed

• fix: typo by @barelyhuman in #9
• Automatically navigate to new project after creation by @Rei-x in #7
• chore: improve local development by @Siumauricio in #13
• doc: Update prompt text by @ack3rs in #14
• fix(#10): slugify the appName and remove weird characters by @Siumauricio in #19
• feat: use ss -tulnp | grep ':PORT ' instead of lsof -i :PORT by @hauserkristof in #15
• Fix/builder env wrong way by @Siumauricio in #21
• fix(typo): enviroment -> environment by @jesse-holden in #20
• feat: add canary builds for testing purposes by @Siumauricio in #23
• Docs/contributing by @Siumauricio in #24
• Main release by @Siumauricio in #25

New Contributors

• @barelyhuman made their first contribution in #9
• @Rei-x made their first contribution in #7
• @Siumauricio made their first contribution in #13
• @ack3rs made their first contribution in #14
• @hauserkristof made their first contribution in #15
• @jesse-holden made their first contribution in #20

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