DEV Community: Andrei Jiroh Halili

[question] Self-hosting Forem with Docker Compose instead of QEMU VM + Cloud setup

Andrei Jiroh Halili — Thu, 15 Jan 2026 07:49:35 +0000

Hi Forem community! I am considering self-hosting Forem with just Docker Compose instead of following the development setup with QEMU. Does anyone attempted to build that one for use in containerized setups or do I have to poke around the development Compose file from the main repo?

Thanks a lot in advance for those replying.

Boosting this since this also blowing up at Hacker News but on a seperate post by a fellow Hack Clubber.

Andrei Jiroh Halili — Thu, 18 Sep 2025 10:34:42 +0000

Elias

Sep 18 '25

Why i hate salesforce.

#hackclub #hackathon #webdev #programming

Comments 1

1 min read

Late 17th Birthday Thoughts

Andrei Jiroh Halili — Thu, 02 Feb 2023 16:50:29 +0000

Well, hello there 👋! It’s good to be back here on Medium writing for my 17th birthday, although I also cross-posted this in my personal Substack (sorry for this if that’s unexpected to you, read more why) and I do also have a bit of my personal thoughts for this birthday by the way.

Paper cutouts over a blue background by Daniel Enamorado from Pexels with the title of the post for Andrei Jiroh’s blog, made with Canva. Used for social previews and as featured photo when shared within Medium.

So why I stopped writing suddenly in Medium?

You know the drill, school and my busy work as a squad lead and all-rounder software developer/maintainer/DevOps engineer hellscapes at Recap Time Squad and also on my own side projects. I still wrote a bit on my WordPress.com blog lately through before December when I started writing on my personal Substack.

I would like to also bring in The Bloody Hell PH as a separate publication in Medium, but I probably need to pay for subscription just to do that now, and that’s a lot I missed here since the last time I write anything here.

The elephant in the room: Why Substack then

So why Substack over something as holy grail as Ghost? I want subscriptions to be an integral part of my blog/newsletter/future podcast instead of yet another WordPress plugin to set up (which you need a paid plan for WP.com users), and support data portability of my content and my subscriber list. I also want to start with the basics first before blowing things up with the backend pain of self-hosting and Linux homelabs.

Still unconvinced? In the comparison page, both of them are considered as Open Subscription Platforms for bloggers and online writers (tl;dr: data portability and the use of Stripe Connect for payment processing), but the latter can be self-hosted on your own if Ghost(Pro) Starter plan is not for you. In contrast, Medium falls short in data portability and also branding, even if I spotted hints about Stripe on their support articles.

Sure, I could just f**k paywalls and paid subscriptions and publish all of my blog posts as web3 content on mirror.xyz as collectible writing NFTs for Ethereum users (my content minus media and third-party $#!t are licensed under CC BY-SA 4.0 International, IDK if Medium choose to stay at 3.0 Unported if I set the licensing details, sent them a support ticket anyway for clarification, but I might consider do dual-licensing soon) and also immutable over at Arweave, which we might have GDPR related problems (might not be same situation if we forget about blockchains for storage and just use something like Storjor even IPFS), but considering trust issues relating to NFTs (look at Web3 is Going Just Great for examples of this type of internet $#!tf**kery) and also environmental considerations to the hellscape you wish didn’t dig up because of me.

For most writers in Medium, especially for those who writing relentlessly since time emporium, the one-subscription-to-rule-them-all is fine with some drawbacks, including, as mentioned earlier, the data portability hell. I mean, you got your mailing list for your newsletter, but it will be a PITA to completely move out due to networks effect.

The only holdback that I have with Substack right now is that I can’t write posts and manage publications within the mobile app, other than subscriber’s chat (which is also exclusive to their mobile apps if you want to enable it), which is kinda annoying to fire up the browser and painfully edit things in a small factor.

Okay, back to the main topic. How’s your birthday (or week)?

You know, the usual school work (plus the periodical exams) and then some. On January 23 and 24, I did some non-alcoholic recipes in the house, not only for our shop (currently Barista/Bartendering, but I prefer to call it the former for legal reasons related to hard minimum age requirement on alcoholic drinks) but also as a personal treat for that two-day period other than theweekly mixtape I did full of music released under Epidemic Sound while in Spotify Premium Mini. Surely, my shop teacher is slowly being traumatized on how do I use the knife against the mangoes (Don’t worry, I didn’t accidentally cut myself in the process. I know, it’s painful to see the footage, especially for first timers and those who don’t usually prep/cook food at home.).

What do I wish and want to do for myself this year?

As mentioned in my 2022 year-end reflection and what’s in the plan this year, I wish for better mental health, self-esstem and self-confidence for myself, lessen my suffering in silence from my self-hatred and a corrupted self-image (also known as “beating myself up harder every time I f**k things up” and the anxiety + trauma I carry over the years plus the mental “2 Minutes Hate” (reference from George Orwell’s 1984, but it’s longer and more minutely/hourly) if internalized ableism is also considered)

There are also things I want to do this year that are boldly wished I did in the past years but didn’t due to pandemic (among other reasons), but I might need to reprioritize and reconsider things to at least thrive (not just survive) in senior high school, rebalance life and work and also for mental health reasons.

So that’s it, folks!

While it didn’t make it to publish before January 2023 ends because I’m watching the first season of Mr. Robot lately in full (not through the YouTube clips from the official show channel) and some open source project maintenance chores while migrating repos to ~tulir’s GitLab instance + sourcehut (the hosted one) while playing Måneskin‘s DON’T WANNA SLEEP and READ YOUR DIARY on loop, I might start write a bit more for the coming months, but don’t expect anything because life sometimes hit me like a bus, assuming we’re talking about the bus factor. Hopefully I could handle the burnout during the sembreak, so I don’t think about “abandoning the children” (I mean projects and maybe my own community, I’m not ~mikedmoy btw.).

This content is originally written and posted in Medium and also available in Substack and as plaintext in lists.sr.ht. As much as I love to read comments in each of these platforms, I would prefer and even recommend sending me a plaintext email to my public inbox, as mentioned below.

Have any comments on one of my blog posts? Start a new discussion on my public inbox by sending a plaintext-only email to ~ajhalili2006/public-inbox@lists.sr.ht (make sure to read the equities in sending email to a public mailing list) or contact me privately, and I will try to respond to you as much as possible. If you’re receiving this from Substack via email, just hit reply.

How do co-authors can sign commits, for vigilant-mode-enabled GitHub users?

Andrei Jiroh Halili — Sat, 05 Jun 2021 14:03:08 +0000

Since re-writing commit histories that are been public is not only discouraged by the Git Book itself, but also disastrous for downstream (aka fork) maintainers and even can be an nightmare since they need to rebase their work first, how do co-authors can safely sign their commits or do they need to do the chaos management regarding that to ensure that it's Verified not Partially verified when someone visits their?

This question assumes that at least one of the co-authors has Vigilant Mode enabled on their GitHub accounts and has at least one GPG key added into their account.

Introducing Recap Time

Andrei Jiroh Halili — Fri, 05 Mar 2021 14:53:44 +0000

You found out that The Pins Team launched a new Medium publication for Recap Time from one of the recent team updates? Oh, nice!

The quarterly (hopefully bi-monthly) newsletter

We push new newsletter issues bi-monthly (or at least quarterly). That includes what’s happened in the past months, the memes, and the bruh moments, among updates from the Pins team and the community. Please don’t expect that we will be released one newsletter issue per quarter (or twice a month), as yours truly have a life beyond writing the newsletter.

If you want to track our progress, and want to contribute, see our GitLab repo. Contributions are welcome and usually where we start the process of making an new issue.

What it contains in a nutshell?

Tech news, community updates from Hyun’s Dojo Community, and probably open-source community, a compilation of memes we found on the Internet, and then some.

Besides our regular issues, we also share some weird posts here sometimes and even community posts are welcome soon.

Support our work!

We don’t like ads and promotions. If you want to keep the Pins team independent (both financially and editorially), support us on Patreon. If you prefer not to help us financially independent, give us some claps, follow, and share the word. (Referrals and these affiliate links are fine, but we’re not yet another ad-tracking company again.)

Without further ado, follow the Medium publication’s official newsletter to be the first one to know whenever we’ll release our first issue as soon as possible. And of course, follow us on our socials at Twitter and Mastodon.

Sidenote: You knew that I’m usually abandoning other projects like our handbook for newer ones like this, like any other developers out there. Also don’t worry about my mental health after months of lockdown and staying-at-home, I’m fine.

Team Updates — New Twitch channels and more (oh my!)

Andrei Jiroh Halili — Tue, 18 Aug 2020 10:48:28 +0000

Team Updates — A new Medium publication, changed publication URL change, and Twitch channels? (oh my!)

Since we rarely post updates about what we’re doing, many things are the things you missed even before the pandemic starts. Don’t worry, we got you covered!

Heads up! We updated this post on 9–1–2020 8:10PM (PH Standard Time) to fix some grammar and browoken link bugs.

🎊 A new publication for Recap Time

Yes, you heard it. We got a new, separate publication for Recap Time. Also, yours truly had made a new publication logo that used for Recap Time, here on Medium, and will be on Telegram, Twitter (and spoiler: Twitch), soon.

That was designed on Canva. Feel free to send us feedback so we can improve it.

As we speak, we’re busy crafting the first issue that we'll release it on January 2021. But if you want a preview, be one of our patrons on Pateron to get exclusive access to our draft. Feel free to subscribe to the newsletter to be the first to read the first issue once it’s out.

ℹ️ OwO, we changed our publication URL for the team blog.

Months ago, we changed the publication name to The Pins Team Blog. On August 8, we asked Medium Support to change our publication URL into medium.com/thepinsteam-blog and they granted our wish, so we thanked them.

🔓We unlocked a special repository in our GitHub placeholder account.

Our special repository contains a list of team members and links where you can find us outside GitHub.

❔ And, Twitch?

Yes, we got two Twitch channels. One for the main channel, and one for Recap Time. We’ll go live soon in the form of test broadcasts to learn how to broadcast. In a meanwhile, follow us there to be the first to get notified.

💬 Leaving Keybase when?

Ryan Lester from Cyph sent us a message thru our yourfriends@madebythepins.tk address, inviting us to leave Keybase and look for alternatives. We’re not yet ready to move out, but we saved our special invite link for later use.

And, that’s it for now. Follow us on Twitter and Telegram for more updates on what we do next. Have a nice day and stay safe!

Handling requests to delete their account & move to the @ghost account for self-hosted Dev.to instances

Andrei Jiroh Halili — Sun, 31 May 2020 11:12:07 +0000

I have a question on how the admins of Dev Commuity handle these types of account deletion requests. Is there any UI way in the Admin Dashboard to migrate stuff to @ghost and nuke the account in question or should I need database access?