2 ms·

The idea of switching from one company that holds your data to another doesn't make sense to me. What does make sense and is worth working for is being able to

The idea of switching from one company that holds your data to another doesn't make sense to me. What does make sense and is worth working for is being able to host my own code on my network. That's where GitLab really comes in for my work. I have no reason to switch from one platform to another if I can't host it in my own network. GitLab was a great idea but from my experience it's been built on an extremely frustrating method of deployment. I'm not a dev ops person nor do I want to be. I want things to be as simple as "run this and it will work" without me needing to do much of anything. I tried to setup a GitLabs instance but after running a simple update command (apt-get update && apt-get upgrade) it broke. It seemed to have something to do with something called Sidekick at the time or something along those lines. It was just frustrating that the automated update scripts from their deb BROKE their own system. That just should never be a possibility in a system, I have near no tolerance for dealing with crap like that. After messing around with it for a while I gave up and tried Gogs. It was easier to use but using go's build tools yielded similar problem for me. It's not the easiest thing to setup and takes a bit of know how to get Gogs and golang's build tools working (I know someone is going to tell me I'm wrong and that this did not happen to me). I settled on GitBucket [1] and I have to say I'll not be switching to anything else. It was simple: download and run a single jar file. I setup an unprivileged user, it's own opt folder, and a small init.d script to do everything I needed. To update I download the latest version and I do a drop in replacement with the .jar. Nothing difficult. (Sadly GitHub seems to have put legal pressure on them to change their 'look' so they've done that but before that it was perfectly stable in appearance unlike GitLabs). If anyone is interested in the self-hosting aspect of this, I'd say don't look at GitLabs, Gogs, or any of the other systems out there. Look at GitBucket. [1] - https://gitbucket.github.io/ https://gitbucket.github.io/

dijit 10y ago
I'm surprised you're not running the docker instance, it's literally "run this and it will work" in fact, most of their instructions are rather on the nose.
- gravypod 10y ago
  Getting docker working for me has always been a pain. I've still not gotten as docker install working across updates or dist-upgrades. Again, I'm as much of a sysadmin/debops is a neurologist in the way that I'm in no way a neurologist. If I cut open someones head, maybe messed around with some things, and closed it up they might be ok. That's how my servers 'run'. Anything outside securing the system (ssh key auth, non-root user, etc) to a standard good enough for me is not doable.

dijit 10y ago

I'm surprised you're not running the docker instance, it's literally "run this and it will work" in fact, most of their instructions are rather on the nose.

gravypod 10y ago
Getting docker working for me has always been a pain. I've still not gotten as docker install working across updates or dist-upgrades. Again, I'm as much of a sysadmin/debops is a neurologist in the way that I'm in no way a neurologist. If I cut open someones head, maybe messed around with some things, and closed it up they might be ok. That's how my servers 'run'. Anything outside securing the system (ssh key auth, non-root user, etc) to a standard good enough for me is not doable.