4 ms·
Congrats! I used to use Firefly III, this looks similar but more polished. Am I correct, self-hosting is only possible with the $520 lifetime license?
by mcsniff 3y ago
Congrats!
I used to use Firefly III, this looks similar but more polished.
Am I correct, self-hosting is only possible with the $520 lifetime license?
- scubakid 3y agoHey thanks! And yeah that's currently the case. Most of the folks who initially asked for a self-hosted version wanted a way to pay once and then know their deployment could operate offline indefinitely. I hoped there might be a bit less piracy risk that way too. If others would be more interested in a recurring model for self-hosting though, I'd definitely consider it.
- aaronscott 3y agoI would be very interested, depending on cost. For pricing models, JetBrains (PyCharm) has a nice setup, although it could be more user friendly. After 12 months of payments you get a perpetual fallback license[0]. The more user friendly version would be getting perpetual access to the current version of software after 12 months of payments, rather than the backdated version. But I understand their reasoning. 0 - https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-perpetual-fallback-license- https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
- mcsniff 3y agoThis is backwards to what I am used to; self-hosting is normally the free option and hosted is paid, this is common among many projects. We also certainly hear about companies or individuals looking for an easy way to send money for FOSS projects they rely on, so hopefully it works out for you!
- milesvp 3y agoBe warned, most of the comments I’ve heard on HN are that self hosting options are disproportionately expensive to support. Charge accordingly
- scubakid 3y agoLuckily the current self-hosted version has not been much of a burden to support so far. But I do wonder if/how that might change with an alternate licensing model. In the examples you've heard about, do you recall where the most significant support costs oftened stem from?
- milesvp 3y agoI think it was dealing with the myriad different environments they could be deployed in. I’ve done a lot of sysadmin work, and I can tell you that a lot of companies just don’t have a repeatable environment. That said, my suspicion is these days, with a good container type solution, if you maintain that, and support just what’s inside that boundary, that can go a long way to mitigate calls. Of course, I love containers until they break, especially when they break because of some implied dependency changes.
- scubakid 3y agoAh, makes sense. This one is containerized and orchestrated with Docker Compose. At this point, I can barely imagine trying to create and maintain a cross-platform self-hostable product the old school way.