PLANKA Community (Release Version 2.0) announcement #663

New Issue

OVERLORD · 2026-02-04T20:44:42+03:00

OVERLORD commented

2026-02-04 20:44:42 +03:00

Originally created by @nickbe on GitHub (Mar 3, 2025).

The next generation of Planka is around the corner and we are currently testing the first release version. Also there's a ton of other things to be done simultaneously. These are the things the community doesn't have to care about, but for our company they are vital. And while we know that you are getting impatient waiting for the release we want to remind you that, what you will be able to use just like that in the end, had cost us years of effort a considerable amount of money and it still does and will continue to do so.

To protect our own interests we intend to make absolutely sure everything in Planka will work according to design and concept. We will have little time for "small" bug reports and therefore we will get rid of them as best as possible.

Contracts have to be made, agreements are in the works, lawyers are involved and infrastructure needs to be set up and tested until it works perfectly. No risk - no fun is an advice only fools give to other fools. And raising a well structured and sustainable company is not a fools game. Finally handing over a good part of our creation to the community because we like open source is fun, but at the same time as serious as it gets.

Having said this we want to let you know that we are close to finishing the important things. Several more days will pass until we are ready to release and as much as we'd like to do it yesterday, we need patients ourselves and take meticulous care to do it properly and without haste.

Originally created by @nickbe on GitHub (Mar 3, 2025). The next generation of Planka is around the corner and we are currently testing the first release version. Also there's a ton of other things to be done simultaneously. These are the things the community doesn't have to care about, but for our company they are vital. And while we know that you are getting impatient waiting for the release we want to remind you that, what you will be able to use just like that in the end, had cost us years of effort a considerable amount of money and it still does and will continue to do so. To protect our own interests we intend to make absolutely sure everything in Planka will work according to design and concept. We will have little time for "small" bug reports and therefore we will get rid of them as best as possible. Contracts have to be made, agreements are in the works, lawyers are involved and infrastructure needs to be set up and tested until it works perfectly. No risk - no fun is an advice only fools give to other fools. And raising a well structured and sustainable company is not a fools game. Finally handing over a good part of our creation to the community because we like open source is fun, but at the same time as serious as it gets. Having said this we want to let you know that we are close to finishing the important things. Several more days will pass until we are ready to release and as much as we'd like to do it yesterday, we need patients ourselves and take meticulous care to do it properly and without haste.

OVERLORD closed this issue

2026-02-04 20:44:43 +03:00

OVERLORD commented

2026-02-04 20:44:50 +03:00

@Neurology0443 commented on GitHub (Mar 3, 2025):

Thank you very much for sharing your hard work with us. I know you can't do a living with a thank you nor Am I able to contribute financially or help out with my basic bash scripting skills... However, it's very important to me to write it "out loud" ?not just with an emoji.

It's getting very difficult to get nice things in a more an more closed source world pay-walled behind ads ridden spywares... It because simple project like yours that the community still exist and can thrive further in a more and more obnoxious connected world !

From the bottom of my heart, thank you ! Can't wait to give it a try 👍

@Neurology0443 commented on GitHub (Mar 3, 2025): Thank you very much for sharing your hard work with us. I know you can't do a living with a thank you nor Am I able to contribute financially or help out with my basic bash scripting skills... However, it's very important to me to write it "out loud" ?not just with an emoji. It's getting very difficult to get nice things in a more an more closed source world pay-walled behind ads ridden spywares... It because simple project like yours that the community still exist and can thrive further in a more and more obnoxious connected world ! From the bottom of my heart, thank you ! Can't wait to give it a try 👍

OVERLORD commented

2026-02-04 20:44:53 +03:00

@KaptianCore commented on GitHub (Mar 6, 2025):

Is it safe to assume that when 2.0 releases it will come with some sort of script or way to easily migrate from 1.x to 2.0?

@KaptianCore commented on GitHub (Mar 6, 2025): Is it safe to assume that when 2.0 releases it will come with some sort of script or way to easily migrate from 1.x to 2.0?

OVERLORD commented

2026-02-04 20:44:57 +03:00

@meltyshev commented on GitHub (Mar 12, 2025):

Is it safe to assume that when 2.0 releases it will come with some sort of script or way to easily migrate from 1.x to 2.0?

Hi! Yep, the upgrade script is nearly finished.

@meltyshev commented on GitHub (Mar 12, 2025): > Is it safe to assume that when 2.0 releases it will come with some sort of script or way to easily migrate from 1.x to 2.0? Hi! Yep, the upgrade script is nearly finished.

OVERLORD commented

2026-02-04 20:45:05 +03:00

@jaimedmp commented on GitHub (Mar 18, 2025):

Hi, is the upgrade script will include a database upgrade/migration. In my instance, I have postgres:14-alpine installed.

@jaimedmp commented on GitHub (Mar 18, 2025): Hi, is the upgrade script will include a database upgrade/migration. In my instance, I have postgres:14-alpine installed.

OVERLORD commented

2026-02-04 20:45:20 +03:00

@meltyshev commented on GitHub (Mar 18, 2025):

Hi, is the upgrade script will include a database upgrade/migration. In my instance, I have postgres:14-alpine installed.

Hi! The migration script will only modify the database structure and update images. However, you can migrate to Postgres 16 right now by following these steps:

Backup everything first!
Create a database dump:

docker exec -t "planka-postgres-1" pg_dump -U postgres planka > dump.sql

Stop containers and delete the database volume:

docker compose down
docker volume rm "planka_db-data"

Update the Postgres version in docker-compose.yml:

...
  postgres:
    image: postgres:16-alpine
...

Pull the new Postgres version and restore the dump:

docker compose pull postgres
docker compose up postgres -d
cat dump.sql | docker exec -i "planka-postgres-1" psql -U postgres -d planka

Start all services again:

docker compose up -d

Note: container names and volume names may differ based on your configuration. Make sure that all names in double quotes match your setup. If everything was successful, you can also delete the dump.sql file by rm dump.sql.

@meltyshev commented on GitHub (Mar 18, 2025): > Hi, is the upgrade script will include a database upgrade/migration. In my instance, I have postgres:14-alpine installed. Hi! The migration script will only modify the database structure and update images. However, you can migrate to Postgres 16 right now by following these steps: 1. **Backup everything first!** 3. Create a database dump: ```sh docker exec -t "planka-postgres-1" pg_dump -U postgres planka > dump.sql ``` 3. Stop containers and delete the database volume: ```sh docker compose down docker volume rm "planka_db-data" ``` 4. Update the Postgres version in `docker-compose.yml`: ``` ... postgres: image: postgres:16-alpine ... ``` 5. Pull the new Postgres version and restore the dump: ```sh docker compose pull postgres docker compose up postgres -d cat dump.sql | docker exec -i "planka-postgres-1" psql -U postgres -d planka ``` 6. Start all services again: ```sh docker compose up -d ``` _Note: container names and volume names may differ based on your configuration. Make sure that all names in double quotes match your setup. If everything was successful, you can also delete the `dump.sql` file by `rm dump.sql`._

OVERLORD commented

2026-02-04 20:45:35 +03:00

@jaimedmp commented on GitHub (Mar 20, 2025):

Hi, thank you for your help, the instructions worked perfectly!

@jaimedmp commented on GitHub (Mar 20, 2025): Hi, thank you for your help, the instructions worked perfectly!

OVERLORD commented

2026-02-04 20:45:40 +03:00

@KaptianCore commented on GitHub (Mar 31, 2025):

Hey I was wondering if there was any update you guys could provide on V2 if not no worries just thought I'd see as I am super keen to upgrade.

@KaptianCore commented on GitHub (Mar 31, 2025): Hey I was wondering if there was any update you guys could provide on V2 if not no worries just thought I'd see as I am super keen to upgrade.

OVERLORD commented

2026-02-04 20:45:43 +03:00

@stufently commented on GitHub (May 4, 2025):

Where I can get helm chart ?

@stufently commented on GitHub (May 4, 2025): Where I can get helm chart ?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#663