Search
60 results for “irfanhakim”
-
Testing out #Nix on #SteamOS/#SteamDeck, and so far so good! It's been helpful in getting any of the missing non-graphical packages I need, such as to install and get my #KDE/#Dolphin service menu working (https://github.com/irfanhakim-as/kde-service-menu-reimage) - where I needed a couple of missing deps like #ImageMagick and #Exiftool.
Most of the graphical apps I need are easily found/installable on #Flatpak though, except something like #Alacritty. I previously installed it on this system using #Distrobox and it worked great, I thought to test installing a graphical app off of Nix - but it doesn't seem that worked with Alacritty. From my search it's something to do with GL/Vulkan apps outside of #NixOS or something of the like. There were also some apps that aren't available as Flatpaks, are available on #ArchLinux 's #AUR, but aren't available on Nix.
There will also be things that don't work too, I think for reasons that may be obvious to others, such as adding HEIC support to KDE apps like Dolphin (for previews) and #Gwenview (for image viewing). On a 'normal' Linux system, this is done by installinglibheifandkimageformats(pretty sure u need both). Installing them on this SteamOS machine tho off of Nix, doesn't really help the system's Dolphin and Gwenview app to be able to serve/open HEIC files.
Still, I know I'm just barely scratching the surface of what I could do with Nix - even as just a 'package manager'. I understand why maybe #Valve is holding themselves back from pre-installing Nix for now tho (unlike something like #Podman or #Distrobox, which they were surprisingly - in a good way, happy to do) bcos the situation with the Nix project, atm, is a lil confusing.. but as recommended by others on here, I think I'm having a good luck/time with the #Lix project's 'flavour' of Nix.
🔗 https://lix.systems -
I ended up with hosting a repo on #GitLab instead to store the #SMAPI releases from v3.18.6 onwards - don't think anyone else would need it but just in case:
🔗 https://gitlab.com/irfanhakim/smapi-release -
Update
0.1.3
- Added #Bazarr support for automatically acquiring subtitles for #Radarr/#Sonarr media without any or of the desired language.
🔗 https://github.com/irfanhakim-as/charts/pull/62 -
Update
0.1.3
- Added #Bazarr support for automatically acquiring subtitles for #Radarr/#Sonarr media without any or of the desired language.
🔗 https://github.com/irfanhakim-as/charts/pull/62 -
Update
0.1.3
- Added #Bazarr support for automatically acquiring subtitles for #Radarr/#Sonarr media without any or of the desired language.
🔗 https://github.com/irfanhakim-as/charts/pull/62 -
Update
0.1.3
- Added #Bazarr support for automatically acquiring subtitles for #Radarr/#Sonarr media without any or of the desired language.
🔗 https://github.com/irfanhakim-as/charts/pull/62 -
Always wanted to host a #FOSS URL shortener, finally able to using #Kutt. Made a #Helm chart for it too on my chart repo.
✂️ Sample shortened link: https://cut.moekai.com/GrN3JM
🔗 https://cut.moekai.com
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/kutt
🔗 https://github.com/thedevs-network/kutt -
New update to the #Homelab Wiki: Updated the existing guide to set up a #WireGuard #VPN server using #PiVPN, and added a new guide to set up a WireGuard VPN server, with a web UI, using the #wg-easy #Docker container.
PiVPN has been rock solid for me for many years, but after testing out WireGuard Easy - having your deployment containerised and having that web interface is pretty nice!
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/wireguard.md -
New update to the #Homelab Wiki: Updated the existing guide to set up a #WireGuard #VPN server using #PiVPN, and added a new guide to set up a WireGuard VPN server, with a web UI, using the #wg-easy #Docker container.
PiVPN has been rock solid for me for many years, but after testing out WireGuard Easy - having your deployment containerised and having that web interface is pretty nice!
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/wireguard.md -
New update to the #Homelab Wiki: Updated the existing guide to set up a #WireGuard #VPN server using #PiVPN, and added a new guide to set up a WireGuard VPN server, with a web UI, using the #wg-easy #Docker container.
PiVPN has been rock solid for me for many years, but after testing out WireGuard Easy - having your deployment containerised and having that web interface is pretty nice!
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/wireguard.md -
New update to the #Homelab Wiki: Updated the existing guide to set up a #WireGuard #VPN server using #PiVPN, and added a new guide to set up a WireGuard VPN server, with a web UI, using the #wg-easy #Docker container.
PiVPN has been rock solid for me for many years, but after testing out WireGuard Easy - having your deployment containerised and having that web interface is pretty nice!
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/wireguard.md -
New update to the #Homelab Wiki: Updated the existing guide to set up a #WireGuard #VPN server using #PiVPN, and added a new guide to set up a WireGuard VPN server, with a web UI, using the #wg-easy #Docker container.
PiVPN has been rock solid for me for many years, but after testing out WireGuard Easy - having your deployment containerised and having that web interface is pretty nice!
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/wireguard.md -
Was looking for a #FOSS solution for managing/tracking the type of 'assets' I and my family own/have in multiple households - including laptops, chargers, cables, and so on.
This is most definitely overkill considering how this software is outright enterprise material, and not family/personal use - but what I ended up discovering and deploying in my #homelab is #Snipe-IT and it's really good (and as mentioned, super powerful)!
Just published a simple #Helm chart on my repo to get it up and running on your #Kubernetes cluster.
🔗 https://github.com/irfanhakim-as/charts/tree/master/mika/snipe-it -
Update 0.2.1 for Flex 🎉
Added #ErsatzTV support - a platform where you could create "TV" channels that broadcast your own media to your streaming platform i.e. #Jellyfin or #Plex in a "traditional" TV format, with programme scheduling, guides, and all.
I've been wanting to have this for a really long time and it's good to finally have it - eventho I've to rely on CPU transcoding for now, which surprisingly works pretty well with no buffering etc. tho I suspect I couldn't get more than 1 client streaming concurrently lol.
🔗 https://github.com/irfanhakim-as/charts/pull/141
RE: https://sakurajima.social/notes/a69b2hb04o -
As a (temporary) replacement of #GWE so I could configure fan controls for my #NVIDIA GPU on #Linux, I ended up using #LACT and it works perfectly! I still prefer GWE simply bcos it supports #Flatpak but for everyone else, LACT is a solid choice for fan controls or overclocking your GPU since it not only supports #NVIDIA GPUs, but also #Intel and #AMD.
I've updated my Linux wiki with the simple steps on how to get it set up.
🔗 https://github.com/irfanhakim-as/linux-wiki/blob/master/topics/lact.md
RE: https://sakurajima.social/notes/a5hl1wsvck -
Anyway, this was somehow due to #Node.js being upgraded or something like that - which taught me to pin/recommend a specific
nodeversion on my projects. Not really the type of thing I've encountered with #Python before to think about it too much.
This also taught me, perhaps the importance of installing an LTS version of Node. This also led me to discover #nvm, which is a super neat way of managing multiple Node.js versions on a single system.
I've documented in my Wiki how I set nvm up.
🔗 https://github.com/irfanhakim-as/linux-wiki/blob/master/topics/nodejs.md
RE: https://sakurajima.social/notes/a47ygtfrtd -
How does one properly, and safely shutdown an #RKE2 #Kubernetes cluster (and monitor + ensure that is truly the case)? I'm surprised it doesn't seem to be discussed in the official RKE2 docs at all, and the very few discussions I've seen of it on #GitHub kinda return various answers I'm not quite confident/certain of.
I'm trying to fully and properly tackle this so I can incorporate it in my RKE2 management tool so even fools like me can be "proper" about it rather than... idk... shutting the VMs down and hope for the best each time :blobfoxcat:
🔗 https://github.com/irfanhakim-as/orked/issues/25 -
Finally figured out a way to achieve this and the solution is simple enough for me.
The initial guide on my #Linux Wiki was on how to make your #KDEPlasma desktop acquire your #SSH and #GPG passphrases graphically and by also utilising your #Kwallet for a seamless experience of storing/reading them to/from it (i.e. like you'd normally get on #macOS with its #Keychain).
This introduced an unwanted behaviour though whereby it'd still attempt to do that (and fail) even when you have no access to the desktop graphically (i.e. when you're logged into the desktop through a remote SSH connection).
I've now updated my guide on how to address this - ultimately making your system get these passphrases graphically/from the #KDE Wallet when it's able to, otherwise opt to get them from the terminal instead if your user does not currently have access to a graphical session.
🔗 https://github.com/irfanhakim-as/linux-wiki/blob/master/topics/kwallet.md#setup
RE: https://sakurajima.social/notes/9z8et8kvz3 -
Another addition to things I wrote no one cares about, if you're a digital (video) hoarder like me, this thing has made it incredibly easy for me to download videos from just about anywhere. It's based on #youtube-dlp so it's incredibly fast and supports downloading vids from just about anywhere including #YouTube, #Twitter, #Instagram, #TikTok, #Facebook, etc.
You could just useyoutube-dlpdirectly, but I've added a bunch of things to this project in order to make the process of downloading vids as simple and reproducible as possible. Check out the project README for details on its features, installation, and configuration options. Supports #Linux, #macOS, and #Windows (through #WSL).
🔗 https://github.com/irfanhakim-as/ezdl -
Another addition to things I wrote no one cares about, if you're a digital (video) hoarder like me, this thing has made it incredibly easy for me to download videos from just about anywhere. It's based on #youtube-dlp so it's incredibly fast and supports downloading vids from just about anywhere including #YouTube, #Twitter, #Instagram, #TikTok, #Facebook, etc.
You could just useyoutube-dlpdirectly, but I've added a bunch of things to this project in order to make the process of downloading vids as simple and reproducible as possible. Check out the project README for details on its features, installation, and configuration options. Supports #Linux, #macOS, and #Windows (through #WSL).
🔗 https://github.com/irfanhakim-as/ezdl -
Another addition to things I wrote no one cares about, if you're a digital (video) hoarder like me, this thing has made it incredibly easy for me to download videos from just about anywhere. It's based on #youtube-dlp so it's incredibly fast and supports downloading vids from just about anywhere including #YouTube, #Twitter, #Instagram, #TikTok, #Facebook, etc.
You could just useyoutube-dlpdirectly, but I've added a bunch of things to this project in order to make the process of downloading vids as simple and reproducible as possible. Check out the project README for details on its features, installation, and configuration options. Supports #Linux, #macOS, and #Windows (through #WSL).
🔗 https://github.com/irfanhakim-as/ezdl -
Another addition to things I wrote no one cares about, if you're a digital (video) hoarder like me, this thing has made it incredibly easy for me to download videos from just about anywhere. It's based on #youtube-dlp so it's incredibly fast and supports downloading vids from just about anywhere including #YouTube, #Twitter, #Instagram, #TikTok, #Facebook, etc.
You could just useyoutube-dlpdirectly, but I've added a bunch of things to this project in order to make the process of downloading vids as simple and reproducible as possible. Check out the project README for details on its features, installation, and configuration options. Supports #Linux, #macOS, and #Windows (through #WSL).
🔗 https://github.com/irfanhakim-as/ezdl -
Another addition to things I wrote no one cares about, if you're a digital (video) hoarder like me, this thing has made it incredibly easy for me to download videos from just about anywhere. It's based on #youtube-dlp so it's incredibly fast and supports downloading vids from just about anywhere including #YouTube, #Twitter, #Instagram, #TikTok, #Facebook, etc.
You could just useyoutube-dlpdirectly, but I've added a bunch of things to this project in order to make the process of downloading vids as simple and reproducible as possible. Check out the project README for details on its features, installation, and configuration options. Supports #Linux, #macOS, and #Windows (through #WSL).
🔗 https://github.com/irfanhakim-as/ezdl -
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.
Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.
I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner -
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.
Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.
I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner -
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.
Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.
I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner -
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.
Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.
I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner -
I've self-hosted my own #Forgejo server for a while now and it's been such a freaking delight to work with, and gives me some relief that my code/#Git repos have a place outside of #GitHub. When I started this however, I couldn't fully migrate everything I had to Forgejo - as some were still tied to GitHub's actions and their hosted runners. Before I could migrate them, I'd need to set up runners of my own on the Forgejo server.
Seeing GitHub's rapid deterioration lately, I resumed my search on setting up runners on Forgejo the right way, and was initially under the impression that it's gonna be complicated... but as it turns out, it really isn't. I set up a simple runner on a remote #RaspberryPi I had using #Docker (Compose) and it was ready to go. Porting my actions/workflows files were super easy too, unlike doing the same for something like #GitLab. Now all of my repos that were on GitHub and had some CI/CD set up have been migrated to my Forgejo server, using my own runners.
I've updated my #Homelab Wiki topic on Forgejo to include the optional step to set up a Forgejo runner. If you're now only considering deploying Forgejo, feel free to check out the rest of the topic which covers the complete setup, some basic recommended configurations, and even how to migrate your repos to Forgejo and set up push mirroring so they still exist on GitHub (if you choose to).
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/forgejo.md#forgejo-runner -
I think this #Linus/#LTT video makes it very clear this thing I've always thought about #Linux - Linux has been for a while now, extremely ready for Developers and Tinkerers. Ready doesn't mean trouble-free, nope, but usable AND pleasant to use (a big productivity boost even in my case) - but will encounter issues that these groups of people will be able to solve, or, work around them with relative ease.
For normies though, nah, it's def not ready to varying extents depending on who you are. This doesn't mean that they couldn't use Linux, cos it is indeed still usable and pleasant to use for ~90% of use cases - but they will most def encounter issues they absolutely would not be able to solve on their own, and we know how not a small number of people in the Linux user community are useless or even harmful and shouldn't be relied on for help (for these normies).
For normies that still wish to use Linux, they def can but it's def highly recommended for them to only do so if they have someone (IRL) they can rely on for help - like any friends or fam members who are already using Linux, no different than when you're growing up and using #Windows/#macOS for the first time. Also, thanks to #Microsoft, the incentive to ditch Windows for something like Linux has been steadily growing and may even make the learning pains of using/experimenting with Linux more acceptable and worth it, compared to staying on a sinking ship that is Windows.
These people however may also opt for macOS, tho I think the biggest blocker for #Apple from gaining market share in this space is the fact that their OS is locked to their hardware, and their hardware - as amazing as they are, are incredibly locked down and not upgradable/serviceable. Anyway, someday we may see the day where Linux is ~99-100% ready for normies, but today is def not the day. Videos like LTT's and maybe others too are good sources on why that is the case, to us who may already be too familiar with Linux to 'have the eyes' to see these issues. It's also why I started documenting my Linux Wiki in the first place, when I migrated away from Windows - as a reminder on the issues I stumble upon, and how I solved them.
▶️ The Good, the Bad, and the Ugly Side of Linux https://youtu.be/QK02VOGWEv0
🔗 https://github.com/irfanhakim-as/linux-wiki -
Updated #Orked, my collection of scripts to help set up a production-ready #RKE2 #Kubernetes cluster in your #homelab. This update brings general improvements to the scripts, improved documentation, #HAProxy load balancer support for load balancing multiple Master nodes, and upgraded all components including RKE2, #Longhorn, #Nginx Ingress, #Cert-manager, #MetalLB, #Rancher, etc. to their latest versions.
I still hope someday to support more Kubernetes distributions like #k3s, but haven't gotten around to it. I've also been planning to support more #Linux distros as the base too, instead of only #RockyLinux/#RHEL, but that'll have to wait as well for now. Regardless, I am quite happy with how mature and stable these scripts have turned out to be. If you'd like to set up a cluster of your own, maybe check it out!
🔗 https://github.com/irfanhakim-as/orked
🔗 https://github.com/irfanhakim-as/orked/pull/41