Usually, one of the first things a Linux/Unix user learns is to create a shell script. The process generally goes like this:

1. Write a script.sh file.
2. Fill it with

   #!/bin/bash
   echo "Hello world"
   

3. Make it executable with chmod +x script.sh
4. And finally, run it with ./script.sh

Nice and simple, and most *nix users are familiar with this. For an average user, the journey ends right then and there, but if you’re interested, you realize that there’s always ways to use and abuse the tooling.

This is going to be a quick post, but it’s still something that I like. I love systemd, and try to (over)use it every time I can.

This is one of those use-cases where I can use ngrok to freely demo my app without having to set up a cloud instance or open up a port in my router. The simple usage of running ngrok is fine for simple cases like hosting a minecraft server for an hour, but if you need to run it in the background you’d need a service. This is all done without the use of sudo or becoming root; you just need to set up ngrok and have a machine with systemd.

When I received my Steam Deck about -checks Steam account- 3 months ago, I was already aware of what it was capable of, considering that I had been browsing r/SteamDeck while waiting for it. What I did not know was its capabilities as a Linux desktop or even server.

You may ask “what is so special about another Switch clone?” if you don’t know what it is, and if you do you may ask “what is so special about a handheld pc?”