Skip to content

Releases: louislam/dockge

1.4.2

21 Jan 17:02
@louislam louislam
1.4.2
4a9173f
Compare
Choose a tag to compare
1.4.2 Latest
Latest

🐛 Bug Fixes

  • #380 Fixed the startup issue that Dockge is no longer working after restart
  • #342 Fixed the login placeholder issue (Thanks @cyril59310)

🦎 Translation Contributions

Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.

Contributors

queeup, catfishlty, and 15 other contributors
Assets 2
Loading
0 Join discussion

1.4.0

03 Jan 12:29
@louislam louislam
1.4.0
f8ad8c4
Compare
Choose a tag to compare
1.4.0

🆕 New Features

  • #200 Initial support for multiple Dockge instances

🦎 Translation Contributions

Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.

How to setup multiple instances

Assume that you have 4 Dockge instances currently.

  1. Find one Dockge instance as your primary Dockge
  2. Login to your primary Dockge
  3. In the homepage, you can connect to other Dockge instances by clicking New Agent.
  4. Now you should see all instances are online and all stacks across all Dockge instances are in the stack list.

How it works?

  • Your browser only need to connect to Dockge 1. Dockge 2/3/4 are connected from Dockge 1.
  • Dockge 1 works like a proxy, it will forward requests/responses from Dockge 2/3/4 to your browser.

Contributors

Zandor300, abnerssantana, and 17 other contributors
Assets 2
Loading
14 Join discussion

1.4.0-beta.0

26 Dec 12:00
@louislam louislam
1.4.0-beta.0
5578f28
Compare
Choose a tag to compare
1.4.0-beta.0 Pre-release
Pre-release

🆕 New Features

  • #200 Multiple Dockge instances

🦎 Translation Contributions

Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.

How to switch to the beta version?

Open dockge's compose.yaml and change the image tag from 1 to beta like:

...
services:
  dockge:
    image: louislam/dockge:beta
...

And then update and restart the stack:

docker compose pull
docker compose up -d

How to setup multiple instances

Assume that you have 4 Dockge instances currently.

  1. Find one Dockge instance as your primary Dockge
  2. Login to your primary Dockge
  3. In the homepage, you can add new agent. Connect all 3 other Dockge instances.
  4. Now you should see all instances are online and all stacks across all Dockge instances are in the stack list.

How it works?

  • Your browser only need to connect to Dockge 1. Dockge 2/3/4 are connected from Dockge 1.
  • Dockge 1 works like a proxy, it will forward requests/responses from Dockge 2/3/4 to your browser.

Contributors

demonisius, NexiaMoe, and 5 other contributors
Assets 2
Loading
5 Join discussion

1.3.4

16 Dec 15:34
@louislam louislam
1.3.4
ac2a62a
Compare
Choose a tag to compare
1.3.4

⬆️ Improvements

🐛 Bug Fixes

  • #301 Fixed an envsubst issue that it won't work if the yaml contains non-string primitive types
  • #303 Updated Docker Dompose plugin from 2.21.0 to 2.23.3, which may fixed some upstream bugs

🦎 Translation Contributions

Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.

Contributors

PeterDaveHello, alexdelprete, and 7 other contributors
Assets 2
Loading
0 Join discussion

1.3.3

10 Dec 13:28
@louislam louislam
1.3.3
03c7815
Compare
Choose a tag to compare
1.3.3

🐛 Bug Fixes

  • #255 Fix: The .env editor is stopped working if the file contains \r\n (Thanks @syko9000)
  • #269 Fix: Check update is not working
  • #268 Envsubst the yaml file in order to display the correct values in the UI instead of tags such as ${PORT}
  • #270 Fix: .env code change is not reactive

🦎 Translation Contributions

⬆️ Security Fixes

Others

  • Other small changes, code refactoring and comment/doc updates in this repo:
    #264 (Thanks @derekmahar)

Please let me know if your username is missing, if your pull request has been merged in this version, or your commit has been included in one of the pull requests.

Contributors

derekmahar, syko9000, and 5 other contributors
Assets 2
Loading
1 Join discussion

1.3.1

04 Dec 18:51
@louislam louislam
1.3.1
bd5dd3c
Compare
Choose a tag to compare
1.3.1

🆕 New Features

  • #218 #231 Added support for editing .env file (Thanks @syko9000)
  • #212 Added pnpm run reset-password, which is used for resetting your password.

Improvements

  • #228 Sort non-managed stacks to the end of stack list
  • #227 Improved performance

🐞 Bug Fixes

  • #206 Fixed an issue that the container terminal could be wrong if containers from different stacks had the same service name (Thanks @ThalesC)
  • #235 Fixed an issue that the external network do not show correctly in 1.3.0

🦎 Translation Contributions

Others

Contributors

syko9000, lucasreiners, and 15 other contributors
Assets 2
Loading

1.3.0

04 Dec 16:07
@louislam louislam
1.3.0
54fb2c1
Compare
Choose a tag to compare
1.3.0

🆕 New Features

  • #218 #231 Added support for editing .env file (Thanks @syko9000)
  • #212 Added pnpm run reset-password, which is used for resetting your password.

Improvements

  • #228 Sort non-managed stacks to the end of stack list
  • #227 Improved performance

🐞 Bug Fixes

  • #206 Fixed an issue that the container terminal could be wrong if containers from different stacks had the same service name (Thanks @ThalesC)

🦎 Translation Contributions

Others

Contributors

syko9000, lucasreiners, and 15 other contributors
Assets 2
Loading
2 Join discussion

1.2.0

26 Nov 10:18
@louislam louislam
1.2.0
9a5d403
Compare
Choose a tag to compare
1.2.0

Warning

It is highly recommended that you should upgrade to it, if you are using any older version, due to the 100% CPU usage issue.

🆕 New Features

  • #182 Add support for extra info: URLs

Improvements

  • #174 version: 3.8 will no longer be added automatically to your compose file.
  • #60 Close terminal if there is no clients connecting
  • Dockge will no longer add empty fields (networks, volumes etc.) into your compose file.

🐞 Bug Fixes

  • #186 Fixed the 100% cpu usage and terminal issues (Thanks @williamstein)
  • #171 Fixed the status issue that is incorrect for dockge stack

🦎 Translation Contributions

Others

Contributors

RyanBalfanz, williamstein, and 13 other contributors
Assets 2
Loading
6 Join discussion

1.1.1

21 Nov 12:43
@louislam louislam
1.1.1
52e1f55
Compare
Choose a tag to compare
1.1.1

🆕 New Features

  • #122 Added an ability to "down" a stack

Improvements

  • #124 Reduced some unnecessary file read

Bug fixes

  • 0208684 Update a stopped stack, will no longer start the stack
  • c8770a9 Fixed incorrect stack status

🦎 Translation Contributions

Others

  • Other small changes, code refactoring and comment/doc updates in this repo:
    @RyanBalfanz @MrEddX

Contributors

RyanBalfanz, AlexMcArrow, and 8 other contributors
Assets 2
Loading

1.1.0

19 Nov 09:46
@louislam louislam
1.1.0
a007ec5
Compare
Choose a tag to compare
1.1.0

🆕 New Features

🦎 Translation Contributions

Contributors

ThalesC, furkanipek, and 2 other contributors
Assets 2
Loading
0 Join discussion