Kaneo – An open source project management platform
45 comments
·February 22, 2025stego-tech
pylotlight
I was onboard before reading RMQ.. less keen on using that, perhaps we can swap it out with somethnig else.
mdaniel
It seems to just have named it RabbitMQ but speaks AMQP https://github.com/kaneo-app/app/blob/v0.1.0/apps/api/src/ev... and I know ActiveMQ supports AMQP <https://activemq.apache.org/components/artemis/documentation...> probably a bunch of other brokers do, too
flkenosad
It's an internal tool. How much does your task manager really need to scale?
jarym
Everything has to go in Kubernetes these days… usually at the request of users who lack the relatively trivial skill to convert a Compose definition into a set of Kubernetes resources.
jlkuester7
Yeah, was thinking that as well. IMHO, compose.yaml is the best balance of convenience and simplicity if you need one (or even "several") instances. You should only get more fancy if you need to deploy `n` instances with auto provision/load-balancing/failover/etc.
Aeolun
It seems to me that converting docker-compose to kubernetes is fairly straightforward too.
otherme123
You can enter any data in the "register" form as long as it validated (e.g. mail@made.up), it lets you in anyway without mail verification.
dietr1ch
Then just give me a button to try anonymously
pooper
For anyone who wants my username and password, I tried the following for both username and password. Feel free to use this as your demo (remember your scout's promise though).
billg@microsoft.com
Edit: looks like I managed to break my instance without even trying. I can't edit my first task that I created.
https://demo.kaneo.app/dashboard/workspace/nyxfpvfgkk412xg4n...
Steps to reproduce:
1. Log in as billg@microsoft.com
2. Click on workspace Microsoft Blue
3. Click on project DataCenters
4. Click on the first task, DAT-1 Build data centers around the world
5. Observe the screen just says "Task edit" with nothing else there.codelion
Great points about the documentation! I totally agree that more detail on production setups and security is crucial. Docker Compose is fine for kicking the tires, but it quickly falls short in real-world scenarios.
The Kubernetes suggestion is spot on too. It's almost a must-have these days for anything beyond a basic deployment.
And the RabbitMQ rationale is super important. Transparency about those kinds of choices builds trust and encourages community contributions. Took me a while to figure out why some projects went with certain dependencies, and clear documentation would have saved me a lot of time.
superfrank
I was super interested in this, but I bounced from your landing page after about 30 second. Echoing what everyone else says:
- Put screenshots on the landing page
- If I click "Try Demo" I just get sent to a log in page and I have no idea what to do next. I don't even want to try a demo, I just want to know what the damn product looks like. If I've got to create an account just to see your product, that's an instant bounce from me.
Fixing both of those would be ideal, but fixing even one would be a massive help.
jsomedon
The point of demo is to make it as easy as possible to try your product. Having people register really defeats the purpose. Either get rid of login phase for demo, or at least prefill input fields with some demo user/password pair.
fuomag9
If a GRAPHICAL software project doesn't have screenshots I'm not even considering deploying it
yodon
"No screenshots, no interest"
aacevski
Hey y'all, I'm Andrej. The developer behind Kaneo. Sorry for not inserting any screenshots. Honestly this software is still in beta and I'm still working on this. Thank you for the feedback. I had
- I will remove the sign ups for the demo - Add more screenshots
This is a passion project as someone mentioned. I love open source and it will always stay free. Hopefully I'll be able to share it whenever it's complete it.
PS: I had no idea this was posted here
Thank you all.
Jedd
Appreciate it must be frustrating to get a lot of (repeated) suggestions for things that are already further down your todo list.
Let me add one and a half. : )
Comparison / advantages (even if anticipated rather than current) over competitive products in this space, which I assume are things like Planka, Kanboard, and other similarly generous and responsibly licensed kanban/project-management tools.
Tangentially related, in your documentation a discussion around your architecture decisions - f.e. rabbitmq, sqlite.
adastra22
The fact that it is trending on HN despite the lack of adequate Kandi g page material indicates there is demand for such an app. Keep working on it!
tarapichumani
agree, the feedback is a sign of market demand. thanks for sharing this, going to check it out :)
gclawes
I wish you could do the demo without having to sign up
Xiol32
Bounced out so hard. Not even any screenshots on the first page.
remram
No screenshot, no video, can't middle-click on any of the links. This is a terrible landing page!
I hope the product is different, but I have no way to find out since no public demo.
layer8
The feature cards trying to look like stacks is also weird. In addition, I would expect clicking on (say) “Visual Task Management” to show a page with a more detailed description of that feature, along with screenshots showcasing it. Lastly, the page doesn’t seem to support light mode.
pratio
Congratulations on the release. While I echo the sentiments from others that screenshots or a video would've been very useful, the signup works without an email confirmation which is great, so I was able to see how the interface looks like. It has a very linear like feel https://linear.app/.
- If you could deploy a demo that doesn't require a signup/sign in, it'll make things a lot easier. You can reset it every x hours.
- The feature list is empty as I can't see what it offers or a comparison to other tools.
- After creating a task, I can't edit it.
Project management is very complicated and there's different groups of users, which one is yours? Those who need a full fledged jira with sso? they won't self host and won't care if it's open source. Small shops that need something cheap? Hobbyists or students?
I'm selfhosting vikunja https://vikunja.io/ at the moment. Opensource and supports my selfhosted sso.
You can find more here
https://github.com/awesome-selfhosted/awesome-selfhosted?tab...
https://github.com/awesome-selfhosted/awesome-selfhosted?tab...
Once again kudos on releasing and opensourcing it.
brimstedt
> Those who need a full fledged jira with sso? they won't self host and won't care if it's open source.
Not necessarily true. Id like to replace jira in an enterprise environment and we do need sso and prefer to self host.
eGQjxkKF6fif
Here's some screenshots I took: https://imgur.com/a/gpbQ1cZ
jofzar
Saying in the nicest way op, this just looks like todoist with a more focus on modern AMOLED/OLED/dark theme.
preezer
Screenshots where? Insert asking ape meme
cloudking
Homepage needs a brief demo video in the hero section
robertclaus
Looking at the GitHub project, this looks to be a passion project more than a community driven one. It's great to see a project like that getting some eyes and potentially attracting contributors. If anything, the main website is a little misleading in this regard.
Little technical nitpick - I would have prioritized moving off of a shared-volume sqlite database before introducing a backend message queue.
e-m-p
+1 on screenshots and not requiring data harvesting. I was intrigued, but lost interest quickly.
Echoing others: screenshots, demo that doesn't require data harvesting (ahem, "sign ups").
Personal feedback:
* Docker Compose is sufficient for a Quick Start, but not production installation. Needs substantially more documentation about production-ready setups at the very least, especially security considerations.
* Would also add additional Quick Start guides for Kubernetes.
* Documentation should also cover rationale behind prerequisite choices. RabbitMQ is Broadcom's domain, and there's a lot of sour grapes out there who want to steer clear of them, MPL-licensed or not. If alternatives won't be suggested or offered, then at least explain why a given piece was chosen so other builders can explore contributing alternatives.
All in all, the essentials seem to be coming along nicely. Just take the time to document, document, document now, so you're not treading technical debt later should its use take off.