Category: Daily Musings (page 1 of 58)
2020/01/09 – Today’s vlog features a voice-over and footage of me walking because it’s quite cold & windy in Toronto. I’m talking about how I’m going to start streaming at https://mixer.com/eeebil whenever I’m working on my hour of power.
So all of my projects will be streamed at https://mixer.com/eeebil and you can join in the fun!
As well, I talked a bit about the Geetech A10M 3D printer we bought. Let me know if you want to see that assembly video or the review.
Hi there! I am going to take a hiatus from posting vlogs for the next 2 weeks while the holidays are upon us. I have a lot to do, as usual, so I’ll be spending my free time with my cutie and our families.
I hope the holiday season has treated you well and that you have a fantastic 2020!
What have you accomplished this year? Don’t feel bad if you can’t come up with an answer straight away. Most people can’t. It can be hard to pat yourself on the back for all of the things you managed to do, especially if you struggle with mental or other health issues.
It’s enough that you’ve made it through the year. There certainly is a lot about the state of the world to worry about. Sometimes we have to focus our efforts on the things we can do, rather than what feels out of our control.
As for myself, I think I’ve accomplished a decent amount this year.
- First group game-jam submission
- Finally got Tenk Werz to a state I can feel happy calling done
- Learned a lot about the platforms I use at work
- Went to the UK for the first time and blogged each day!
- Drove on the left side of the road for the first time
- Started my medical transition (a long time coming!)
- Picked a name! (I will be Lilithe, but I plan to make a more comprehensive post about that in the future.)
- Coded a 3D engine from scratch in C++ (with the help of onelonecoder.com, of course!)
- Ripped my first famiclone and learned about the weird world of NES clone hardware
I’m sure there’s more in there, but that’s a quick list for now. As you can see, it’s easy to start coming up with things once you really think about it. Be proud of yourself for making it through 2019 and extra proud for all of the little things you did, for yourself or for others.
Have a happy holiday! 💜 𝓛𝓲𝓵
Gitlab helpfully lets you know it’s making backups of the database each time it does an upgrade, but trying to find information on where those files are stored by default on the web is an exercise in futility. Most links lead to Gitlab themselves and they sure as hell aren’t telling you.
Well I hope to help someone else (and possibly myself in the future) by listing a few useful ones here.
Step 1: Needed files
To restore from a boot / OS failure, or after a fresh install, you’ll need the following files:
- the entire /var/opt/gitlab/git-data folder
- the file you want from /var/opt/gitlab/backups
- install the exact same version of gitlab you were previously running before the failure
So hopefully you were able to rescue those files as they contain your settings, secrets, the db backup and the repositories themselves.
Step 2: Install Gitlab
Having gathered all of these things, you’ll need to first install the relevant version of Gitlab. I needed the version before current so the command in Xubuntu (using apt) is:
sudo apt install gitlab-ce=12.5.3-ce.0
12.5.3 is the version the restore process told me I needed. The
-ce.0 part is important if you’re using gitlab-ce.
If you’ve already installed a prior version before coming here, you can look at the output of that command for clues on how to get it to continue despite you already having a database.
Step 3: Restore the database
Now copy the backup files from where you have them into
sudo cp -R <source folder goes here> /var/opt/gitlab/backups/
Now that you have the right version installed, you can restore the backup. Make sure you set the permissions on
/var/opt/gitlab/backups so the user
git can access it.
# Allow the git user to access the backups sudo chown -R git:git /var/opt/gitlab/backups # List the backups to see what we can restore! sudo ls -alF /var/opt/gitlab/backups
You should get a listing of the different backups that were made. Usually you’ll want to pick the most recent one, which will be listed last.
Next you type in the command to actually restore the backup database. My backup file was
We need to take the _gitlab_backup.tar part off of the end and use that as our file to restore:
sudo gitlab-backup restore BACKUP=1576180022_2019_12_12_12.5.3
If you have any problems, the fix is usually in the error output. You may run into an issue if you have the wrong version installed. Go back to Step 2: Installing Gitlab and fetch the version it tells you to.
Step 4: Restore the repositories
After the db is restored, you may still need to copy the repositories over too. Those are located in the
sudo cp -R <source folder goes here> /var/opt/gitlab/git-data/ # Allow Gitlab to access the files sudo chown git:git /var/opt/gitlab/git-data/
I’ve had some luck simply copying them over but sometimes that doesn’t work. So you may need to import those repositories manually. That fix is outside the scope of this short how-to, but keep at it and you’ll get things back up and running in no time!