Hi,
I understand that Bloop is shutting down as a startup and Projects, Remote etc. are implemented as server-dependent features.
However, given the open-source nature of the project, it's very easy to spin up a local or company shared server to continue hosting those features. In fact I had set this up and migrated all data from Bloop Cloud to my locally hosted database.
The latest update 0.1.44 has now forced the shutdown of Projects - they are export-only and cannot be accessed, regardless of which API is used.
I understand that you want to prepare people for the shutdown and ensure that everyone starts to off board off of Bloop Cloud, however I fail to see the logic of shutting it down on local infrastructure, especially given the growing competition in this space with Projects being one of Vibe Kanban's main differentiator.
Please consider the following:
- Disable projects ONLY IF the client connects to default Bloop Cloud API
- Let the community decide whether to remove Projects from the codebase or keep maintaining them
Additionally, I'd like to note that the Data Export feature is incomplete - it lacks issue links to workspaces and project settings (such as colors).
I have solved the above with custom Frontend scrapers and data backfill, but would still expect that the export feature would allow me to get all data without loss, including relationships.
Hi,
I understand that Bloop is shutting down as a startup and Projects, Remote etc. are implemented as server-dependent features.
However, given the open-source nature of the project, it's very easy to spin up a local or company shared server to continue hosting those features. In fact I had set this up and migrated all data from Bloop Cloud to my locally hosted database.
The latest update 0.1.44 has now forced the shutdown of Projects - they are export-only and cannot be accessed, regardless of which API is used.
I understand that you want to prepare people for the shutdown and ensure that everyone starts to off board off of Bloop Cloud, however I fail to see the logic of shutting it down on local infrastructure, especially given the growing competition in this space with Projects being one of Vibe Kanban's main differentiator.
Please consider the following:
Additionally, I'd like to note that the Data Export feature is incomplete - it lacks issue links to workspaces and project settings (such as colors).
I have solved the above with custom Frontend scrapers and data backfill, but would still expect that the export feature would allow me to get all data without loss, including relationships.