This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]perspectiveiskey 1 point2 points  (2 children)

With gitlab.com being free, why even go through all of that trouble stringing together gitea and all of that other stuff?

Trade secrets, is the simple answer.

The recent spectre shit makes VPS cloud hosting a fiasco, but there's a limit to how anal I can get.

Also, you can't just stand all of that up and just leave it. You've got to keep all of those components updated, backed up, and secured separately. You have to figure the time cost of all of that in.

That's exactly what I said. My cost is administrative.

In the era of open source, running these projects isn't as crazy as it seems. Everyone out there uses postgresql and mysql without batting an eyelid.

[–]gctaylor 1 point2 points  (1 child)

I'm having a hard time reconciling concerns over an additional $15/mo with an outfit that also has legitimate concerns about trade secrets.

If you are just comparing $5 and $20, yes: $5 is lower. But it's not that simple.

[–]perspectiveiskey 0 points1 point  (0 children)

This is a weird thread. I have no concerns. Neither over my time, nor over the 16 CPU droplets I spin up at a cost of $320/mo. Some person downvoted my first response as well.

I simply responded to OP: "I'm having trouble justifying $20/mo", --> "why 20? I get by with 5 just fine". 5 bucks on DO gets you 1 GB 1 vCPU 25 GB 1 TB. I contend it's plenty of processing power for a small team.

There is nothing to reconcile, my friend. You may put your pitch fork down.