71–80 of 85 posts
This is not even an article, it is an ad for a company (ungleich.ch) that provides github-like hosting services.
Since their product is "Private Gitlab Hosting", they only seem to provide the hosting. This is not inherently bad, but they make it look like they are much better than Gitlab.
Personally I'd rather give my money to Gitlab so support their development.
This is not even an article, it is an ad for a company (ungleich.ch) that provides github-like hosting services.
I’m not entirely sure why people are freaking out at this point. This is not the Microsoft of the 90s. How many of these folks are happy to use VSCode and then turn around and panic at this acquisition?
MS may not be dreadful across the board any more, correct, but they absolutely have it in them to wreck a perfectly serviceable product once acquired.
I’m not entirely sure why people are freaking out at this point. This is not the Microsoft of the 90s. How many of these folks are happy to use VSCode and then turn around and panic at this acquisition?
On the comparison with GitLab you mention we don't support IPv6. We do if you host your own. We will enable it for GitLab.com once we're done with the migration to GCP [0]. Our pricing is per user, tiered. Not per-user and then per feature. Although I understand that's not far off from each other.[1] [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/47216 [1]: https://about.gitlab.com/pricing/
With that said: What's so much better about ungleich than rolling your own VM somewhere? For a hackathon and as an experiment I recently setup Gitlab on a fresh Arch Linux VM using the Arch gitlab package and setup was very easy. I suppose using the official way of installation makes it even easier. Do you keep the VM, OS and gitlab up-to-date? Do you do backups?
Hm, I wouldn't migrate my FOSS stuff to ungleich, simply because I don't earn money with it and while I am willing to invest my free time I feel different on throwing money into it. (Company wise I can't make the decision, but I suppose the benefit over our current git-on-NFS + bugzilla + custom distributed, reproducible build system would be negligible, especially given the price for the license). With that said: Wh…
In terms of maintenance: we ensure that the system and installation is up-to-date.
We offer offsite backup as an addon, too.
On the comparison with GitLab you mention we don't support IPv6. We do if you host your own. We will enable it for GitLab.com once we're done with the migration to GCP [0]. Our pricing is per user, tiered. Not per-user and then per feature. Although I understand that's not far off from each other.[1] [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/47216 [1]: https://about.gitlab.com/pricing/
What could anybody need IPv6 on a website for? Users who don’t have IPv4 connectivity or what?
Earlier quoted context omitted.
Just out of curiosity why did you decide to use GCP rather than Azure or AWS?
We currently run on Azure. GitLab integrates deeply with Kubernetes and specifically GKE, so it makes sense to run GitLab.com there: https://about.gitlab.com/2018/04/05/gke-gitlab-integration/
On the comparison with GitLab you mention we don't support IPv6. We do if you host your own. We will enable it for GitLab.com once we're done with the migration to GCP [0]. Our pricing is per user, tiered. Not per-user and then per feature. Although I understand that's not far off from each other.[1] [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/47216 [1]: https://about.gitlab.com/pricing/
Is IPv6 a driver for anyone?