4 ms·

Out of curiosity, why did you move from self-hosted to gitlab.com? I run self-hosted and I've been quite happy with it. Cloud anything just seems like begging

• nico 10y ago
  Great question :) We are a small team so we prefer focusing on writing code than managing our infrastructure. Keeping even just one server secure and up to date is no small task. Additionally, in this particular case, given Gitlab pushes changes pretty often, we wanted to have access to the latest stuff without having to update the self-hosted instance every time (with the added risk of screwing up in the process). I guess there's a trade off for everything.
  • lloeki 10y ago
    Did you consider GitLab's githost.io?
    • problems 10y ago
      GitHost seems incredibly expensive. For $150/mo for their most basic plan I could easily rent a basic dedicated server or VPS from for $10-40/mo. In my experience this takes about a 1 day investment up front then 1 hour/mo (basically just update the box or replace a failing drive once in a while) to maintain indefinitely if you keep it behind LAN/VPN. It's a fairly small time investment with a big reward for security, privacy and stability in my experience. Then you have control of backups too, which seems like a pretty good thing to me given the recent GitLab fiasco.