Blog on Søren's Blog

Run Hugo Blog on uberspace

Sun, 11 Jan 2026 06:00:00 +0000

Back in 2019, I wrote an article on how to run a hugo blog on uberspace (🇩🇪). The magic is not to bring the static files on a webhoster, that’s easy, but that uberspace allows building and publishing the blog for you on your domain. Like GitHub or Netlify, but with a small German hoster.

I use this setup ever since. Although I struggle every now and then.

Robert reached out, because he was facing error messages when trying to implement the same. I couldn’t help him directly, because that article is five years old and I was not sure if things have changed in the meantime.

Luckily, the holidays came with a bit of spare time to test this myself and to provide an updated version.

I was very careful to collect all commands I sent to the terminal and am thus very sure that this works on an U7 uberspace.

Prepare your machine

You need to have the git and hugo available on your machine. Please follow their installation guides.

git
hugo

You also need access to a terminal. That’s standard if you’re on Linux or Mac. You may want to checkout Putty if you’re using Windows.

Create a new asteroid

Now let’s create a new asteroid (= account) on uberspace. Surf to https://dashboard.uberspace.de/register and fill out the form. It has 3 fields. Should take less than a minute.

Let me say it again: I am super happy with uberspace as a hoster. They provide all you need, have a great service and company values. If you don’t know them yet, check out their about-us page.

Once the account is created, nagivate to Dashboard –> Login and set a new password for the SSH access.

Remember the host name on which your asteroid is created. You can find that in the email they write you, or on the Datasheet.

The nerdy stuff

So far, so fancy. From now on, no more UI, but terminal commands only.

First, we connect to your new Asteroid using SSH. Please replace batman with your user name and helium with your host name. You need the SSH password you defined in the previous step to log in.

ssh batman@helium.uberspace.de

Next, we install Hugo. We download the latest release. Check GitHub and replace the url in the wget if necessary.

Wondering what the commands do? wget will download the compressed hugo release, tar will unzip it, mv moves the extracted directory, and rm deletes the file we downloaded.

cd ~

wget https://github.com/gohugoio/hugo/releases/download/v0.154.4/hugo_0.154.4_Linux-64bit.tar.gz

tar -xvf hugo_0.154.4_Linux-64bit.tar.gz hugo

mv hugo ~/bin

rm hugo_0.154.4_Linux-64bit.tar.gz

With mkdir we create a directory that holds our repository. This is where we will push to. Within the folder, we initialize an empty repository (--bare) and create the main branch.

cd ~

mkdir batblog.git

cd batblog.git

git init --bare

git branch -m main

Brace yourself, because now we add the magic 🧚

We tell git to run a few commands every time an update is made on the repository, e.g. when we push a commit holding a new blog post. This is done by changing the content of the post-update hook.

Run these commands to open the file in the nano editor

cd ~/batblog.git

nano hooks/post-update

Copy the following script into the file, change GIT_REPO to match your repository.

What the script does:

define path to the repository we created before (GIT_REPO)
define path to a temporary directory to clone into (TMP_GIT)
define path to your public folder, where the built blog shall be moved to (PUBLIC_WWW)
clone the repository to the temporary folder
change into that temporary folder
build the blog and move the output to the public folder
delete the temporary folder

#!/bin/sh

echo "Start hook magic"

# path to repository
GIT_REPO=$HOME/batblog.git

# path to tmp
TMP_GIT_CLONE=$(mktemp -d)

# path to publich URL
PUBLIC_WWW=/var/www/virtual/$USER/html

# clone repository
git clone $GIT_REPO $TMP_GIT_CLONE
cd $TMP_GIT_CLONE

# build
~/bin/hugo --cleanDestinationDir --destination $PUBLIC_WWW

# clean
rm -Rf $TMP_GIT_CLONE

Save the changes with control + o and exit the editor with control + x.

It’s important to run one more command, letting the machine know that this script is executable.

cd ~/batblog.git

chmod +x hooks/post-update

We’re done on the server. The rest happens on your local machine.

Create and publish your blog

On your machine, we clone the repository that we created on uberspace. Adjust the path to your needs, by replacing batman with your user name, helium with your host name, and batblog.git with whatever you called the repository. You need the SSH password that you defined above.

git clone ssh://batman@helium.uberspace.de/home/batman/batblog.git

This will create a directory called batblog. We open this directory, create a new blog in there, commit the changes and push them to the server.

cd batblog

hugo new site . --force

git add .
git commit -m "initial"
git push origin main

Wait a few seconds and then open your uberspace URL. If you want to make your blog available at your own domain - you just need to add the domain to your uberspace and adjust the DNS records (A, AAAA). A guide how to do this is here: https://manual.uberspace.de/web-domains/

Enjoy your new blog 👏

Update: We can include a repeated execution of the script to allow for scheduled posts.

This week I wanted to tinker on the blog machinery. Scheduled posts have been on the agenda for a while - not because it’s complicated, but because I barely needed it.

With the above setup, this is very simple. Add one row to the crontab.

Assuming you‘re logged in the server (ssh batman@helium.uberspace.de), run

crontab -e

And in the editor, add

@hourly /home/batman/batblog.git/hooks/post-update

Save the changes with control + o and exit the editor with control + x.

This will run the script on an hourly basis and publish scheduled jobs the latest 60min after the planned release.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

On Blogging Platforms

Tue, 30 Dec 2025 06:00:00 +0000

Over the holidays, I was thinking about my blogging workflow. Looking at my statistics for 2025, I got the feeling that my setup is too complex and that it prevents me from writing more.

I thought about moving away from my self-hosted hugo blog on uberspace to a hosted service, where I could focus solely on writing text.

While looking around at the different options, Bear Blog and Micro.Blog quickly became my favorites. They both come with their own pros and cons, but neither is a perfect fit for me.

I read Robert’s blog (and if you don’t yet, you should), and he recently switched from Micro.blog to Bear — or at least, that’s what I thought.

I wrote him a message, and within a couple of hours I got a reply. He didn’t respond directly via email but instead published his answer as a blog post. (Love it 🧡)

Now I know, he didn’t switch, but is using both platforms for different purposes — a perfect setup for him.

Carlos jumped in on the conversation.

Reading both their posts, helped me a lot. I want something where I can easily create a draft and publish it from every device. Often, that will be a mobile device. And while that is possible for Bear, it requires me to open their website. There’s no app or indirect way to publish. I haven’t tested that properly, but it feels cumbersome. I won’t write in the web interface and having to open another app and copy stuff over … I know myself. This won’t work - unfortunately.

Because on the other hand, I liked the look & feel, the possibilities and clarity of Bear more than Micro.Blog. MB has a mobile app and thus a convinient way for publishing, photo posting is simple, but it lacks - I guess on purpose - features. Micro.Blog includes a strong “social” aspect — something I’m glad I reduced. I feel this could become a trap for me.

What does that mean to me? Both are wonderful services. Thinking about it, I assume my challenge is not the tech, it’s finding that regular slot between family, work, and volunteering to sit down and write. Thank you Robert and Carlos for helping in that decision.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

My Blogging Workflow as of mid 2025

Sun, 08 Jun 2025 05:00:00 +0000

Recently, Robert wrote about his updated blogging workflow. A good opportunity to update mine, too.

I wrote about my blogging workflow in 2020 and 2023.

Not much has changed since 2023. I use hugo for this blog, hosted in a repository on uberspace.

To create a new article, I …

take my iPhone. I would love to write more on the Mac but noticed that after long working days I barely want to spend more time in front of a „computer“.
go through Reminders & Notes. The 2023 article mentioned that I‘ll try out obsidian for draft creation - which I did and dumped again. Apple Notes is available on all my devices, convenient and thus my choice for creating drafts for blob articles. Reminders came in recently. An article from flip.de recommended using an iOS Shortcut in combination with a reminders list as an alternative to Pocket (the meanwhile shut-down read-later app). When I find something interesting on web, I use the shortcut to create the „read-later-reminder“ and when I am in the mood for writing, I go through that list and create a draft in Notes.
create bullet points in German. Within the note, I start by creating bullet points in German. Although the blog is in English, I find it easier to create the initial draft in German. The 2023 version mentioned that a draft can stay multiple days, weeks or even months in this state - but this is no longer the case, as long as I am not interrupted during the flow.
write paragraphs. Once the initial idea for the type is layer out, I copy them over to iA writer, create the front matter (title, tags, etc.) and start writing - English - paragraphs. I do one (!) proof read iteration.
start the git magic. iA saves the markdown in the local version of the git repository created by the Working Copy app. I open Working Copy, hit „commit & push“ and wait a few seconds. Here, I wrote about the post-hook that builds the blog after every commit.
Done

For me, this works and I noted that more complex (proof-reading and validation) procedures lead to not writing at all. A downside of this process is that the first time I see how the post will look is when it‘s available on the website. Thus, there is often a second iteration of steps 4 and 5, where I fix typos, add missing links or headings. Then, it’s really done 😅

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

CO2 consumption

Wed, 21 Aug 2024 12:00:00 +0000

I recently wrote about how much energy we consume at home. And while I was in the mood, I started looking for similar statistics for running this blog.

I couldn’t find reliable information about the entire energy consumption, but I stumbled upon a CO2 calculator. Not exactly what I was looking for, but interesting nonetheless (especially since I saw some cool kids typeing this on their websites, too).

According to websitecarbon.com, this website is cleaner than 99% and uses only 0.01g of CO2 per page visit. You can check the result here.

It feels good to be on the greener side. ♻️

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

New Theme

Wed, 26 Jun 2024 19:00:00 +0100

I had my first blog in 2007, almost 20 years ago. Since then, I always „owned" a blog but didn’t necessarily update it regularly.

Over the years, URLs changed (I remember four), focus changed (travel, photo, personal), technology changed (Wordpress, Ghost, Jekyll, Hugo), …

This blog is online since 2019. In 2020, when I had lots of free weekends, I created the first theme myself. Before that, I was always using themes developed by others.

„My" theme came with all monospace fonts and a minimal design. However, I imported the Bootstrap CSS (because I knew it from another project), to have something to start with. This was way too much for my small blog. Total overkill. But no dark mode.

I wanted a change (at least since March). So I googled, visited many of the blogs I read regularly to get some inspiration, and stumbled upon Kev‘s Simple.css.

I liked it. Simple design. Important stuff included, but not overloaded.

For example, the minified CSS for the Bootstrap framework is 144KB in total. By comparison, Simple.css is around 10KB. (Simple.css)

The last rainy weekend was the opportunity I needed to create a new Hugo theme, also going through old types, correcting broken links and fixing typos.

I will push the new theme to production in the next days and hope that your feed readers won’t pull the whole history. But if so, I am sorry for the spam 😅

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

Do I need tags?

Thu, 20 Jun 2024 18:00:00 +0100

This blog is based on Hugo and comes with built-in tags. It even provides a page with a list of all tags used on this blog. Mine is not very polished, because I barely used it.

One of the reasons is me having a hard time coming up - not to speak of sticking with - a taxonomy. If I am being honest, I just type some random tags in the front matter when I start writing a new type. Pure gut feeling.

Question is: should I invest time streamlining this?

Hm. I think the answer depends on the potential benefit of a well structured taxonomy. On this blog, it’s mainly used to populate the „if you liked this, you may want to read …“ section below each type. I use it to find an older type - if I remember the tag - because scrolling through the tag page with less entries is faster. Apart from that? Good question.

Current plan is, since I am anyway working on a new theme for this blog (on the list since March), I will give the tags overview page a facelift and use the opportunity - assuming motivation lasts - to structure the tags, at least once.

In a few months, I will check if I was able to follow the structure or if chaos is back. And if the latter happens - does someone has a better idea how to solve this? 🤔

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

My Default Apps as of mid 2024

Wed, 19 Jun 2024 19:00:00 +0100

Last year, we all shared our default apps. Robb compiled a list of all responses. Thank you. This helped a lot.

Today, roughly seven months later, I wanted to give an update. What apps did I exchange and why?

📨 Mail Client: Mail.app This hasn’t changed. I am happy with Apples build in mail app, although it could get a facelift and a new feature or two. However, not the ones promoted by Apple on this years keynote.¹

📮 Mail Server: uberspace.de No update on this one. Scrolling through the other responses, I thought about trying Fastmail or Migadu but was too lazy to do so until today.

📝 Notes: Obsidian Obsidian has replaced Apple Notes. I like the markdown syntax and theming. It allows me to focus more on writing. Need to improve sticking to my journaling.

✅ To-Do: Reminders.app No update. I don’t like paying for a todo-app. This should come out of the box. And reminders is ok-ish.

📷 iPhone Photo Shooting: Camera.app No update. Looked at the camera app from Leica once, saw the price and was healed immediately.

🟦 Photo Management: Synology Photos No change, although I was thinking about upgrading the NAS under the desk to a more powerful version.

📆 Calendar: Calendar.App & ? I used Calendars 5 as my main calendar app but it will become end of support in a few days. I didn’t find a replacement yet. What Apple showed at the WWDC may be enough for me, but not sure. Coloring events (one calendar, multiple colors) is a must and I don’t saw that in Apple’s presentation.

📁 Cloud File Storage: Synology Drive No update, but maybe new machine.

📖 RSS: Reeder + iCloud Reeder stayed. Still the best RSS reading app from my perspective, but miniflux has been replaced with iCloud. It has more hiccups, for sure, but I don’t need to maintain it.

🙍🏻‍♂️ Contacts: Contacts.app No update.

🌐 Browser: Arc Last year, Safari was my default browser. This event introduced me to Arc. And while I needed a couple of trials - I am now convinced that Arc is my new standard, once two things are shipped: an iPad app and the Noir extension.

[Update - 2024-06-20]:Arc has a dedicated iPad version now ✅

💬 Chat: Signal, WhatsApp No change. I have Telegram Threema, and Matrix - but barely use them.

🔖 Bookmarks: currently everywhere. Need help 🫠 Unfortunately no update. May need to investigate more.

📑 Read It Later: Omnivore Omnivore replaced Pocket. It comes without ads. Nothing else to add.

🛒 Shopping Lists: Reminders.app No change. Reminders works perfectly for us. No need to load another app.

🍴 Meal Planning: no app Still, no dedicated app. I tried Mela for recipes. It has a planning function. We may try it one day.

💰 Budgeting and Personal Finance: python + Excel Currently, trying to come up with a new standard. Probably a Python or R script populating an Excel or Dashboard.

📰 News: Sueddeutsche Zeitung No change but smaller subscription.

🎵 Music: Spotify To save costs, I am back on the Spotify Family Plan. I miss Apple Music.

🎤 Podcasts: Castro No change. Love the app.

🔐 Password Management: Enpass No change - but I like that Apple is building a dedicated app for this. I will try it out once released.

Anything changed on your defaults?

I don’t need AI writing, nor auto-sorting. ↩︎

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

I'll read it

Fri, 29 Dec 2023 19:00:00 +0000

Manuel Moreale wrote a helpful article for everyone thinking about starting a blog. He identified two issues soon-to-be-bloggers have:

not knowing what to write about, and
worrying that nobody will read it

For the first issue, I suggest to read either this article by Manuel, this one by Meadow, or this one by alienlebarge. All three offer inspirations on what to write about and to not overthink it.

Concerning the second issue, Manuel offers to be your first reader. I like the idea and want to join the party. If you’re starting a blog or published something already, let me know. I will read it. Just reach out, I am only one email away.

Currently, I read more than 100 blogs regularly. Some of them type daily, others only once a month or year. They also cover a bouquet of topics. All of them are interesting and I am convinced that yours will be, too.

There are only two conditions:

your blog needs to be written in either German or English, and
your blog needs to have an RSS feed so that I will be informed about new types in my preferred reading app.

Long story short: if you want another regular reader of your blog - send it to me.

Looking forwards to read even more great blogs soon!

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

My blogging workflow as of late 2023

Wed, 29 Nov 2023 20:00:00 +0100

In 2019 I wrote an article about the technical background of this blog, and in 2020 there was a type about how I blogged using iPad. Neither of these articles mentioned the complete workflow, starting by how I capture ideas and how they slowly form into larger articles.

The idea of this type is to give this comprehensive overview. Not for you to replicate it, because it is so cool & smooth, but for me to see how things change over time. I feel ok with the current setup. If you have suggestions on how to improve it, please email me (using the button on the bottom of this page).

Collecting ideas

First step is idea collection. Without an idea, there won’t be a blog type. In the past, I used Pocket as a read-later app and pasted interesting articles or podcasts in there. It took some until I realised that links will remain there. I never found the time and commitment to go through the list again. Something simpler was needed. That’s when I switched to „Apple Notes“. The app is available on all my devices, it is fast, easy to use, and has the ability to paste almost anything in it. From the workflow perspective this means that I create a new note for every interesting topic I want to write about, paste links, pictures, and my thoughts into it and then leave it. I don’t care about formatting or well written text at this moment. The only purpose is to collect the ideas I have, when I have them, in an as easy as possible way.

Formulating ideas

Next step is the draft creation. Within my Notes app, I start formulating the raw notes into a text draft. Usually, I re-do this step a couple of times, slightly changing the text with every iteration. Formatting is still typeponed.

Transfer to markdown

Once the text is in a good enough state, I copy it over to a markdown file, add the front matter (proper title, tags, etc.) and links. Using the markdown syntax, the text is formatted for the first time. This goes hand-in-hand with another round of rephrasing sentences or even paragraphs.

Publish

The final step is publishing. This blog is maintained in a git repository, so in order to publish content, the markdown file needs to be added to the repository. If I blog from the MacBook, I just paste the file in the respective directory, run git add . and git commit -m …. If I publish from a mobile device, I add the file to the repository using Working Copy.

The git repository is hosted on uberspace, which allows some magic (aka a git hook), when something is pushed to it. Each time I push changes to the remote server, a small script runs that builds the static site and makes it available at my domain. No need to build the site manually each time - a big time and frustration safer 🙂

Once an article is published, I read it in the browser … and will definitely find some typos, broken links or formulations I don’t like. Ergo, switching apps, fixing it, and then re-publish the changes.

Ideas for the future

From the default-apps event, I learned that many people use obsidian for note taking. I will give it a try and see if it can replace my Notes and Markdown system break.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

Spring cleaning

Mon, 13 Nov 2023 16:00:00 +0100

Although quite late in the year, I did some spring cleaning on this blog today. Using the „default apps 2023“ as an opportunity, I finally took the time to implement some changes that were on the todo list for quite some time.

Comments are finally gone. I used as self hosted version of „isso“ but found myself not updating the software in several years. Additionally, forcing users to leave personal data (name and email) on this site just to get in touch didn’t feel much GDPR‘ly. Like on many cool blogs these days, there is now a „reply via email“ button below each type.

The default language switched to English. I was thinking about this for quite a while. Why should I write in a foreign language on default? For me, there are mainly two reasons. 1) Posts on this blog are often inspired by articles I read on the Internet. Many of them being in English. Giving credit to the authors and building upon them feels easier if the content does not have to be translated. And 2), although I am not looking to build a huge audience here, I still have the feeling that connecting with fellow bloggers is easier if there is no language barrier. The older types on this blog that are still in German may get an English version soon.

Finally, some smaller changes: I refined the „privacy“ site and combined it with the license information in the new „good to know“ page. And I added an „about“ page. It does not have much content yet, but I am willing to fill it soon.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

My default apps at the end of 2023

Sun, 12 Nov 2023 20:00:00 +0100

I stumbled upon this by reading Kev’s great blog but it seems there are a bunch of people currently sharing their default apps.

For me, always looking for a new app to improve my workflow, this is great. However, I had to notice that many people - like myself - stick with the default apps of their operating system. But, I will scroll through most of the other contributions to check if there is something to try out for me.

I won’t let you wait any longer - here is my list:

📨 Mail Client: Mail.app

📮 Mail Server: uberspace.de

📝 Notes: Notes.app, and just trying out Obsidian.md

✅ To-Do: Reminders.app

📷 iPhone Photo Shooting: Camera.app

🟦 Photo Management: Synology Photos

📆 Calendar: Calendar.App & Calendar 5

📁 Cloud File Storage: Synology Drive

📖 RSS: miniflux + Reeder

🙍🏻‍♂️ Contacts: Contacts.app

🌐 Browser: Safari

💬 Chat: Signal, WhatsApp

🔖 Bookmarks: currently everywhere. Need help 🫠

📑 Read It Later: Pocket

📜 Word Processing: Word

📈 Spreadsheets: Excel

📊 Presentations: PowerPoint

🛒 Shopping Lists: Reminders.app

🍴 Meal Planning: no app, discussions over dinner

💰 Budgeting and Personal Finance: Excel

📰 News: Sueddeutsche Zeitung

🎵 Music: Apple Music

🎤 Podcasts: Castro

🔐 Password Management: Enpass

You can get the full list of participants from here: https://defaults.rknight.me/ and also use the opportunity to add some new blogs to your RSS reader.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

Publish to Blog from iPad

Mon, 28 Dec 2020 12:00:00 +0100

Unfortunately, ideas for new blog posts often fizzle out because I find it too much of an effort to boot up my laptop in the evening and organize my thoughts. I am therefore always on the lookout for ways to lower the inhibition threshold as much as possible.

A good approach would be to remove the laptop from the equation and blog from a device that I have in my hand all the time anyway: Smartphone or tablet, for example. But because the cell phone display is perhaps a bit small, I’m going to see if I can blog well from an iPad today. And yes, this article was written entirely on the iPad.

I use Hugo as the foundation for my blog, which I run (as described here) on a uberspace. This has the advantage that I can outsource some of the magic to the server. Specifically, I have set up a post-update hook in the Git repository on the server. This automatically creates the static files after each commit.

So I don’t need to have Hugo installed on the i-Device, I just need a Git client and a text editor. I found both in Working Copy.

The app costs a bit, but in my opinion it’s worth every penny. Especially because it is perfectly integrated into iOS. For example, the repository can be accessed via the Files app - so I can edit the content with many different apps.

My workflow is now as follows:

within Working Copy, I duplicate an existing Markdown file as the basis for the new article and adapt the YAML header.
open the new file in the integrated text editor and write the article. For a little more syntax highlighting, you can also open the file in an external editor (e.g. Textastic).
if I want to include screenshots or other files, I save them directly to the static folder of the repository via the iOS Files app.
when I’m done, I use Working Copy to commit the changes and then push them to the repository. The uberspace then automatically updates the blog.

It could hardly be easier.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

Hugo mit Git auf dem uberspace nutzen

Fri, 06 Sep 2019 00:00:00 +0000

Vorgeschichte

Vor gar nicht allzu langer Zeit bin ich mit diesem Blog von Ghost zu Jekyll gewechselt. Ghost hat mir eigentlich sehr gut getaugt, auch wenn ich nicht der größte Fan davon war, dass bloggen mit Markdown mit den neueren Versionen einen Klick weiter entfernt war. Außerdem war es für mich immer eine kleine Herausforderung bei neuen Versionen die Abhängigkeiten auf dem Betriebssystem auf dem neusten Stand zu halten und die Datenbank zu migrieren.

Bloggen mit einem Static-Site-Generator schien mir da der nächste logische Schritt. Ich habe also kurz Jekyll ausprobiert und bin schließlich bei Hugo gelandet. Hugo gebe ich aktuell den Vorzug, weil es sich leichter auf einem Windows-PC nutzen lässt und wesentlich schneller ist.

Der geneigte Leser wird wissen, das ich bezüglich Webhoster ein großer Fan der Jungs und Mädels von uberspace bin. Im folgenden also eine kleine Anleitung, um zu meinem aktuellen Setup zu kommen.

Dafür werden wir …

Git und Hugo lokal installieren
Einen neuen Hugo-Blog anlegen
Einen ersten Blog-Artikel schreiben
Den uberspace vorbereiten
Den Blog vom uberspace erstellen lassen
Uns über einen neuen Blog freuen :)

Git und Hugo lokal installieren

Eine Anleitung zur Installation von git findet ihr hier: https://book.git-scm.com
Wie man Hugo installiert, steht auf der Hugo-Webseite: https://gohugo.io/getting-started/installing/

Solltet ihr, wie ich aktuell, an einem Windows-PC sitzen hilft euch vielleicht auch dieses Video weiter. Gleiche Videos gibt es auch für andere Betriebssysteme.

Hugo-Blog anlegen

Ist Hugo installiert, könnt ihr mit hugo new site <sitename> einen neuen Blog anlegen. Wir erstellen das fiktive Blog hugoblog.com.

P.S. Ich nutze auch auf Windows meist die Git-Bash als Konsole. Die kennt auch Befehle wie ssh :)

[Batman@lokal ~]$ hugo new site hugoblog.com

Eine Hugo-Website kommt ohne Theme. Das müssen wir also als nächstes herunterladen. Ich mag das Base16-Theme. Falls euch das nicht zusagt, findet ihr hier aber sicher ein oder zwei Alternativen.

Das Theme müsst ihr in den Ordner themes eurer eben erstellten Seite herunterladen.

[Batman@lokal ~]$ cd hugoblog.com/themes
[Batman@lokal themes]$ git clone https://github.com/htdvisser/hugo-base16-theme.git base16

Und schließlich müssen wir Hugo noch mitteilen, dass ihr dieses Theme verwenden wollt. Dazu passen wir die Konfiguration an.

[Batman@lokal ~]$ cd ~/hugoblog.com
[Batman@lokal hugoblog.com]$ cat <<EOF>> config.toml
theme = "base16"
pygmentsuseclasses = true
EOF

Erster Artikel

Zeit für den ersten Artikel. Mittels touch erstellen wir unter content/posts/ ein neues Markdown-File und befüllen es mit ein ein bisschen Inhalt.

[Batman@lokal hugoblog.com]$ touch content/posts/cooler-artikel.md
[Batman@lokal hugoblog.com]$ cat <<EOF>> content/posts/cooler-artikel.md
+++
title = "Hello World"
date = "2019-09-06"
layout = ["article"]
author = "Batman"
tags = ["uberspace", "hugo", "blog"]
+++

# Lorem Ipsum

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.

EOF

Mal drauf schauen, wie der Artikel aussieht? Das geht ganz leicht mit hugo serve. Hugo erstellt dann einen lokalen Server und lässt euch eure Seite unter folgendem Link betrachten: localhost:1313.

[Batman@lokal hugoblog.com]$ hugo serve
Building sites …
                   | EN
+------------------+----+
  Pages            | 37
  Paginator pages  |  2
  Non-page files   |  0
  Static files     |  6
  Processed images |  0
  Aliases          | 14
  Sitemaps         |  1
  Cleaned          |  0
[...]
Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop

Wenn alles gut aussieht, können wir auf dem uberspace weitermachen.

uberspace vorbereiten

In diesem Schritt können wir uns am Tutorial auf https://lab.uberspace.de/ orientieren. Danke an Christian, luto und Julian.

Domain anlegen

Falls ihr eine eigene Domain verwenden wollt, lest im uberspace-Wiki noch einmal nach wie das geht. Hier gehen wir davon aus, dass ihr eine Domain aufgeschaltet habt und diese auf euren Document-Root (html/) verweist.

Hugo installieren

Um Hugo auf dem uberspace zu installieren, laden wir als erstes die neuste Version von Github als tar herunter. Prüfe im Hugo Repository auf GitHub noch einmal welches die neuste Version ist und passe die Befehle entsprechend an. Anschließend entpacken, nach bin verschieben und aufräumen. Fertig.

[batman@helium ~]$ wget https://github.com/gohugoio/hugo/releases/download/v0.58.1/hugo_0.58.1_Linux-64bit.tar.gz
[batman@helium ~]$ tar -xvf hugo_0.58.1_Linux-64bit.tar.gz hugo
[batman@helium ~]$ mv hugo ~/bin
[batman@helium ~]$ rm hugo_0.58.1_Linux-64bit.tar.gz
[batman@helium ~]$ hugo version

Sollte es mal eine neuere Version von Hugo geben, wiederholt einfach diesen Schritt, um wieder up to date zu sein :)

Git-Repository für Hugo-Blog anlegen

Als nächstes legen wir uns im Home-Verzeichnis einen neuen Ordner an, in dem wir das Git-Repository für unseren neuen Hugo-Blog ablegen.

[batman@helium ~]$ mkdir hugo_websites
[batman@helium ~]$ mkdir hugo_websites/hugoblog.git
[batman@helium ~]$ cd hugo_websites/hugoblog.git
[batman@helium hugoblog.git]$ git init --bare

Git Hook anlegen

Wir möchten, das der uberspace mit jedem push in unser eben erstelltes Repository den Blog neu erstellt und auf der Domain verfügbar macht. Sagen wir ihm das. Dafür passen wir den post-update-hook wie folgt an.

[batman@helium hugoblog.git]$ touch hooks/post-update
[batman@helium hugoblog.git]$ cat <<EOF>> hooks/post-update
#!/bin/sh

# los geht's
echo "Start hook magic"

# hier definieren wir den Pfad zu unserem Git-Repository
GIT_REPO=$HOME/hugo_websites/hugoblog.git

# hier definieren wir ein temporäres Verzeichnis zum clonen des Repositorys
TMP_GIT_CLONE=$(mktemp -d)

# hier definieren wir den Pfad zu unserer öffentlichen Domain
PUBLIC_WWW=/var/www/virtual/$USER/html

# jetzt clonen wir das Repository in den temporären Ordner
git clone $GIT_REPO $TMP_GIT_CLONE
cd $TMP_GIT_CLONE

# Hugo anschmeißen
~/bin/hugo --cleanDestinationDir --destination $PUBLIC_WWW

# aufräumen
rm -Rf $TMP_GIT_CLONE
EOF

Push auf den uberspace

Damit ist alles vorbereitet. Wir sollten jetzt nur noch unser auf dem uberspace erzeugtes Git-Repository als remote zum lokalen Ordner hinzufügen, unseren Artikel committen und das ganze hochladen.

[batman@lokal ~]$ cd hugoblog.com
[batman@lokal hugoblog.com]$ git init
[batman@lokal hugoblog.com]$ git remote add origin ssh://batman@helium.uberspace.de/hugo_websites/hugoblog.git
[batman@lokal hugoblog.com]$ git add .
[batman@lokal hugoblog.com]$ git commit -m "Initial commit"
[batman@lokal hugoblog.com]$ git push origin master

Und das war’s dann auch schon. Auf den ersten Blick ist das ein bisschen länger geworden, aber diese Schritte müsst ihr ja nur einmal vornehmen.

Da ich viel von unterwegs blogge, genieße ich es, auf dem iPad zu schreiben und nur einmal git push eingeben zu müssen, um die Änderungen zu veröffentlichen. Wie ich von unterwegs blogge, werde ich vermutlich demnächst mal aufschreiben.

Und jetzt viel Spaß mit eurem neuen Blog.

Thank you for subscribing to this RSS feed. https://soeren.one/ is søren's personal blog. If you want to get in touch, please reply to this post via email.

Blog on Søren's Blog

Run Hugo Blog on uberspace

Prepare your machine

Create a new asteroid

The nerdy stuff

Create and publish your blog

On Blogging Platforms

My Blogging Workflow as of mid 2025

CO2 consumption

New Theme

Do I need tags?

My Default Apps as of mid 2024

I'll read it

My blogging workflow as of late 2023

Collecting ideas

Formulating ideas

Transfer to markdown

Publish

Refinement

Ideas for the future

Spring cleaning

My default apps at the end of 2023

Publish to Blog from iPad

Hugo mit Git auf dem uberspace nutzen

Vorgeschichte

Git und Hugo lokal installieren

Hugo-Blog anlegen

Erster Artikel

uberspace vorbereiten

Domain anlegen

Hugo installieren

Git-Repository für Hugo-Blog anlegen

Git Hook anlegen

Push auf den uberspace