Hacker News new | ask | show | jobs
by stego-tech 482 days ago
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.

7 comments

I thought they might make their own issue tracker public to show a glimpse of it… But they seem to use GitHub issues instead, which is pretty ironic.
It's an internal tool. How much does your task manager really need to scale?
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.
Or Product Managers/C-Suites/Directors who believe Kubernetes is the future of computing and if it's not in there it's garbage that should be thrown out.

Source: Senior IT Engineer who likes K8s as a concept, but is incredibly disappointed with its unnecessary complexity and everyone's insistence on its use without understanding its role or purpose.

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.
It seems to me that converting docker-compose to kubernetes is fairly straightforward too.
Hey, thank you for the feedback. I have created an issue to add a quick start for Kubernetes as well. Most of my decisions behind this project is to make it super "dumb" and easy to use. Thank you so much for the feedback!
Ah, I was thinking more from the perspective of the consuming party ;)

Though of course it’s nice if you pre-add it, it’s nothing people can’t do themselves.

> * Docker Compose is sufficient for a Quick Start, but not production installation.

As an author of a DevOps tool [1] based around Compose files, I beg to differ! It should be pretty easy to adapt the config from the README to use in medium-scale production setups [2] (the only thing that comes to mind is a reverse proxy perhaps).

I think I’ll add Kaneo to the Lunni Marketplace after some more testing!

[1]: https://lunni.dev/

[2]: Read: small to medium sized businesses, startups without a lot of funding etc.

The example compose file has no database
No external database. It does use SQLite, which is okay unless you’re making a SaaS with thousands of users, and maybe even more, given it uses RabbitMQ for the writes. [1]

The Compose file sets up a volume for it, so the data is persisted correctly.

[1]: If everything’s set up correctly, there shouldn’t be concurrent writes to the SQLite db, and it should scale pretty well then. (The RabbitMQ + SQLite stack is a bit weird, I agree.)

Strange comment about RMQ; a message broker that has been used widely for almost 2 decades
So I bring that up from the perspective of IT, not Product. RabbitMQ isn't something I've seen directly deployed much in the enterprise IT world (not saying it doesn't exist, just that I've not seen it in any prior org myself as a separate component like the Docker Compose cites), but I will say that many Managers/Leaders will just see "Broadcom" on that page and run away screaming like they do from Oracle's stuff.

With documentation on why it was chosen and the function it serves, I (the IT Engineer) am better able to communicate this back to leaders pitching a fit over Broadcom's name on there as well as brief on alternatives. Not saying it's right, just a frustrating reality.

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.
Then just give me a button to try anonymously
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.
I didn't meant for anyone to post their credentials under a fake email, but thinks.

It's the webpage that should be friendlier to people who just want to toy and explore their app before committing to get it running in production.

Hey, thank you for your feedback and I agree. This project is still under heavy development and one of the lovely HN people opened an issue regarding this. I'll get to make the demo accessible without any accounts. Thank you!
You have the button, you just don't like it. I tested it anonymously, and the priorities should not be the anonymous demo login button. They are very far away from that bike shed.
I was onboard before reading RMQ.. less keen on using that, perhaps we can swap it out with somethnig else.
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
I would also add to this list of annoyances that new despicable trend to replace the "See on Github" familiar button into a "Star on Github" button that tries to steal a star.