Mar 1st 2019
I've done some more testing with cgit, but overall it's a little too barebones for me. I'm going to get #gitea installed instead.
I found in the full list of settings that I can disable all markdown rendering, and can make it so avatars for users are only ones that they upload to the server. It's nice to turn off gravatar!
I'm hoping to have this running in a couple days.
Last night, Tara and I were reminiscing about vhs movie rental places. Like... that used to be a fun event! You'd get your friends, all pile in a car, and drive to Video hut or something. Pick out 2-3 movies for the Friday night, then swing by a pizza place to get a couple pies. Head home, and burn through the movies. That was a fun outing. I kinda miss that.
Feb 28th 2019
I am running Debian 9, and it wasn't immediately obvious how to get cgit running.
I found this good piece of reference material that got me to the finish line! Of at least getting it installed. I took what was shared to make my own vhost config for nginx, and eventually that worked. (I am testing it on a different domain before using
allthe.codes for it.)
Reading further though.. do I really need to manually edit
/etc/cgitrc to add a repo? I wanted this to be a place where people could fairly easily create a new repo. Hm.
I will be attempting to utilize cgit first!
It is comforting to me that raindrops on a window look exactly the same as they did when I was a kid. It's a constant decoration throughout my life.
Serious perk of working remotely is the occasional break with our kids. Today our littlest one fell asleep next to me on the couch.
This is always pesky. You have a project and you're using #git as your version control. You have a well manicured
.gitignore file to handle certain things out of your repo.
But! then you need to push everything via #rsync somewhere. Maybe that's your deploy strategy, I don't know. I'm not a doctor. I do know that using the rsync
--exclude to call out each single directory and file you don't want pushed over is a super pain. And you already have this
.gitignore just sitting there, that holds that kind of list already!
If you do something like:
rsync -avz --filter=':- .gitignore' dir/ user@server:/path/to/destination
It will only push over the items that your
.gitignore would allow to be pushed up to your repo. Excellent, yes?
Our littlest one keeps waking up at 4:30am, and that's getting a little rough. At least I'm definitely getting up on time?
Just a quick update, I ported my blog over to a new web content engine I wrote, and so far so good. It'll also support my old Wordpress permalink structure, so I didn't break the web, yay!
More to come.
So, I'm an old man. I love soundtracks from games from older consoles. While yes, you can get mp3s or stream the soundtrack from YouTube, in my opinion the best way is to listen to the original files.
I don't pretend to know how it all works, but talented people can take the game music out of console games into a native-ish format. When you listen to it, the codec basically perfectly recreates the synth/music. For Super Nintendo, it's the
spc file. For Playstation 1 and 2, it's a combination of
Anyway, I have lots of these original soundtracks. In my Windows OS days long, long ago I would load up WinAmp with all kinds of output plugins to play these kind of media files. Good times.
Then, for various reasons I started using Apple products. There is no WinAmp for OSX, and I could find no way to play my soundtracks of choice. I sighed, grumbled, and moved on.
Then! Then! Like 10 years later I've figured it out, and it's super simple. Audacious is an open-source audio player, and it supports all these older codecs no problem. When you go to their site, it isn't obvious that there's a way to get it to run in OSX, but there is.
You'll need to have Homebrew installed, but you probably should anyway because it's super helpful. Then it's just a matter of:
brew install audacious
And it works!!