Hacker Newsnew | past | comments | ask | show | jobs | submit | kyrylo's commentslogin

We Use Rails is a directory of Ruby on Rails web apps. I launched it a year ago, and since then it has received over 150 submissions.

Christmas is special for all Rubyists thanks to the annual Ruby release, so I decided to tag along and join the Xmas party. This is my humble contribution to the ecosystem. Enjoy!


What specifically draws you to Sentry over self-hosting or smaller players? Would an indie-hosted alternative (with similar privacy guarantees but more personalized support) appeal more?


Self host whn you need . Indie alternative would need to release codebase and allow export in any time.


Would you rather pay a big corp or an indie business to host your errors?


Wouldn’t it be cheaper to just pay for a ONCE-style product like Campfire? It’s not that expensive compared to what companies spend on Slack. Then when the time comes, you can switch to Teams (having saved thousands in the meantime).


It uses SQLite as its database.


SQLite is really fast. There's no way that's the bottleneck.


What’s your experience with SQLite? It’s a bit hard to talk about performance without sharing code.


I've used it a fair bit. My biggest use was for a computer processing system that recorded gigabytes of data. If it was limited to 60 inserts per second it would have taken months to run!

I do recall having to change some settings to make it really fast, but it wasn't 60/second slow.

See the "update" in this answer.

https://www.sqlite.org/faq.html#q19


Appreciate the answer! You’ve probably worked with raw SQLite drivers. I’m using a framework, which likely runs more transactions by default. I’m fairly confident that with a bit of digging, I can improve the ingestion speed. Good to know and thanks for sharing your experience!


I follow 37signals updates on ONCE, but I don’t recall them mentioning sustainability issues. Could you share a link?

Thanks for the suggestion! A hosted solution could definitely be an option. That said, some people have mentioned that having an indie dev behind it can be a turn-off. I’ll keep exploring ideas that make sense, though.


I want to vaguely recall that they had like 4 products in planning stages for ONCE, released Campfire, then released Writebook for free, and then made Campfire free.

Lately on the podcast I only hear about Fizzy and one other unannounced SAAS that they're putting dev energy behind, nothing about other ONCE products.

I suspect that without a critical mass of usage driving word of mouth the long tail of sales was basically nil, and long-term even fairly small products weren't looking to recoup dev costs any time soon.


Fizzy uses SQLite for multitenancy. I suppose that’s why it takes up so much of their time. Being a fan of SQLite, I hope this approach succeeds. P.S. I know Campfire has made “six figures”


I appreciate the feedback. I’ve updated the information to remove the WordPress reference and clarified that the OS must support containerization. Thanks!


Yeah, I used it as a starting template. But beyond the layout, the copy and product are completely different. It just helped me get started faster, and I’ve always been open about that. Everything else (including the installer) is fully self-made.


Thank you!


Not at the moment, but I’m open to it! If you have something in mind, feel free to email me at kyrylo@telebugs.com and we can work something out.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: