I think I was a little over ambitious with this project. I am fine using git in a terminal but when working with markdown files, I like to have a preview pane so I chose to try to do everything in VSCode. Installing the app wasn’t an issue, but I had a lot to learn in terms of using it with github and gitlab. This was mistake #1, better the devil you know when trying something new I guess. I now have VSCode working as intended and feel pretty confident when pushing to the main linuxlemming repository.I run KDE and there was an issue with token authentication and I had to install gnome keyring in order to get things to play nice.
I REALLY struggled getting the website in a functional state and being new to VSCode certainly didn’t help. At one point I accidently tried to push changes to a repo I had forked from (woops) and when I made and committed changes and pushed to my own repo, I wasn’t seeing the expected changes on the gitlab site.
I think I need to still figuring out pulling/rebase or something because when there are conflicts I am completely lost on how to properly fix them. I still have A LOT to learn with git.
I am still very confused about the finer details of Hugo. I spent hours building, modifying and nuking site after site, repo after repo, desperately trying to figure out what the heck I was doing wrong. After a few hours of sleep I came up with a systematic approach.
While that looks pretty straight forward, it sure as heck wasn’t when I started. See ado-devops uses a theme called castanet which is what I found first. I just wanted that and thought (still am not sure) that it could be used as a standalone item. A bit hiccup I had though was that outside of the “exampleSite” there was just all this extra stuff. I have no idea what any of it does, but it is important. Trying to run
hugo server outside of the exampleSite didn’t work (that made sense to me) but when I put all my own stuff in and started tweaking things got weird and I was getting module errors and had to put a copy of the castanet folder in my home folder to get it to work. This was one of those cases where I should have just stopped and done other things and wait for that AH HA! moment when you randomly think of a possible solution, but I was being stubborn. I wanted to figure this out!
To someone who knows Hugo well, I am sure that all of this makes sense, but for a beginner like myself, I was making some misguided choices.
So here is what I’ve learned:
I recently decided to purchase my domain of
linuxlemming.com from register4less after hearing about it on The Ask Noah Show. They seem like a good company but there user interface is like taking a trip back to 2002. I needed to have my domain pointing to my gitlab page so I was following gitlab’s documentation but was getting confused again and was super fatigued by this whole process. I hopped into the matrix room for Ask Noah and awesome community member rwaltr helped me get things sorted. After my website was verified, I have two urls:
Now that the site is up, more things don’t work! HOORAY!
So here is the main issue, If my baseURL is set to different options, the theme breaks but the links all go to the correct location or the theme works but none of the links move accordingly. Here it is laid out:
#baseurl = "http://localhost:1313" #baseurl = "https:www.linuxlemming.com/" baseurl = "https://rastacalavera.gitlab.io/linuxlemming/" #relativeURLs = true languageCode = "en-us" title = "The Linux Lemming" theme = "castanet" googleAnalytics = "" paginate = "9" buildFuture = true [taxonomies] category = "categories" series = "series" tag = "tags" [permalinks] page = "../..:filename/" about = "../..:filename/" episode = "../..:filename/"
I had tried everything and was out of my depth. I wasn’t sure where to turn next. GitLab community support forums? A group from DLN or JB? My problem was pretty unique to me and it seemed like a big ask to jump in a random public group asking for help.
I had previously posted an issue on the castanet github page and the developer, Matt Stratton was super friendly and quick to respond! I figured it was worth another shot to open an issue and detail everything that I had tried.
Well, Matt returned and again was super helpful and friendly! Together we solved the issue and also fixed a larger setting in the theme that may benefit others in the future! If felt really good to close issue 342 not only because it solved my problem but because I had a great community interaction. I really hope I can contribute back to the project by helping to close some of the “chore” issues for him.
My interaction with Matt just reaffirmed how great open source can be. To get hands on with the actual dev and have a positive interaction is priceless. I’m sure most of his Arrested DevOps Podcast is over my head, but I’ll be sure to give it a listen and if it sounds interesting, you should too!