Search results for tag #selfhosting
How am I only learning about mini_httpd now? Obviously not the most ideal for multi-site hosting, but still very cool!
Hello my name is Elena and I'm addicted to #selfhosting.
2 MINUTES after receiving confirmation that my self-hosted Ghost blog is finally working perfectly (newsletter sending included) - something that took 84 DAYS of trial and error and troubleshooting - I've started thinking: "what now?"
Could I be... bored?
Yes.
In a way having a running list of problems to fix was keeping me distracted (by the world at large) and somewhat entertained.
Thank goodness I have another big self-hosting project coming up: #PeerTube.
But maybe I should enjoy this BIG accomplishment for like 5 minutes... or a couple of weeks. No point in installing PeerTube while my 4-year-old has just started a 14 day school holiday. My parents are a huge help but I am basically getting interrupted every 10 minutes... so I can't really dive into something complex 😆
A HUGE THANK YOU to everyone who helped me with Ghost - I owe you big time!!! ❤️❤️❤️❤️❤️
🏕️ my adventures in #selfhosting - day 118 (daredevil edition) 😈
Good morning Fedi friends!
Guess what? The amazing blogging platform #Ghost has just released an update which adds new features: https://ghost.org/changelog/custom-content-for-every-subscriber/
I am about to update my Ghost installation FOR THE FIRST TIME using command lines - aaaaaarghhhhhhh. Not gonna lie, my heart is beating fast.
But first! I'm taking a snapshot of the whole VPS in case something goes wrong.
As usual, wish me luck 😅
I just migrated my first repository from github to my own forgejo instance on my new dedicated Hetzner server. Wow, that's liberating! A few more repositories will follow today!
#forgejo #github #UnplugTrump #UnplugUSA #FreeSoftware #SelfHosting #Hetzner
Yo! You #datahoarders Do y'all really back up your 'linux iso's". I like wanna keep them, but I can always just get them back....right! Save space or OCD shit!
Good morning Fedi friends!
I'm finally ready to test if my new self-hosted Ghost blog can withstand the infamous "Mastodon hug of death".
Here's a quick blog post about what I've been up to: https://news.elenarossini.com/what-im-up-to-march-april-2025-edition/
(Apparently Mailgun thinks I'm a spammer, so I couldn't send it as a newsletter - that's a whole other story).
Wishing you all a lovely day + weekend 🌸
🏕️ my adventures in #selfhosting - day 115 (am I a spammer? edition) 🧌
Hello Fedi friends,
I've been a little quiet this week because I have been dealing with an onslaught of unpleasant things over the past 6-7 days. Some are small things, some are really serious and I'm totally exhausted as a result. I'm just being completely transparent here because often life on the internet is based on a big lie and only highlight reels. My week has majorly sucked. But! In the words of Eckhart Tolle: "Realize deeply that the present moment is all you have. Make the NOW the primary focus of your life." Today, right this minute, things are good.
Self-hosting and learning Linux are the things that typically keep me distracted and uplifted. I'm afraid my recent messages have turned into a litany of complaints. I didn't mean to - sorry about that!
Yes, attempts to self-host my Ghost blog have been mired with difficulties at literally every turn. Botched installations, the Mastodon Hug of Death once my blog was ready for its debut... and now? I cannot send a single blog post as a newsletter because Mailgun (the company providing the newsletter integration to Ghost) has flagged me as a spammer and has frozen my account. I have an open ticket and hope this will be resolved soon.
How did this happen? I have no clue. I tried to send a blog post as a newsletter to 210 people (yes ONLY 210 people), it didn't work, the Ghost interface suggested I try again... I did it twice, but I got a "failed to send a newsletter" message. Oddly in the Ghost interface there were stats that the newsletter was sent to 210 people with 0% open rate (it's my personal newsletter that had 65% open rate last time around). I'm subscribed to it for testing and didn't receive anything. Something that works seamlessly is sending test blog posts to my own address. But truly sending blog posts as newsletters fails every time.
Now Mailgun thinks I'm some kind of awful spammer keen on sending marketing messages to strangers. Ouf. They sent me a really long questionnaire about my intentions, my expected monthly volume, etc. Again, the ticket is open and I hope they will unfreeze my account soon. My sending volume is so tiny, it's a bit ridiculous to be dealing with this.
I had to re-activate my Ghost (Pro) account before its expiration on April 18th just to be on the safe side and have a plan B.
It's frustrating to be honest. But c'est la vie.
On the upside, I had reached out to Ghost's founder John O'Nolan to report the JSON code bug (in their documentation) and the maxAge cache issue on the default self-hosted plans... he sent me the nicest email thanking me for the feedback and said they will immediately fix the JSON instructions and implement a new maxAge setting (higher than zero) in the next Ghost release. I'm so excited and grateful for this! Newbie me - with your help!!! - managed to create some positive changes for Ghost. It's the best feeling.
The silver lining in all the self-hosted Ghost troubles is that I'm learning A TON. If every step had gone smoothly the first time around, I would not have learned so much about command lines, Nginx configurations, cache settings or DNS records.
I'm staying curious and very grateful for all the lessons.
And I want to thank you once again for your generosity, helping out as soon as I have a question / report a problem. I'm really touched by your kindness.
Wishing you all a lovely day and weekend.
🏕️ my adventures in #selfhosting - day 111 (quiet edition) 💤
Good morning Fedi friends!
I hope you had a nice weekend.
After backing up my two VPSs I am now staring at my #YunoHost dashboard thinking: now what?
It feels a little odd not to have to tackle any pressing self-hosting issues. Everything seems to be working well, including my manual installation of Ghost on a second (Ubuntu) VPS.
I'm now in maintenance mode.
I must confess in the past 24 hours I have spent some time browsing @yunohost 's app catalogue. So many fascinating things in there! But I am exercising restraint (for now, LOL!)
I'm very grateful for all the software I'm currently self-hosting.
On Debian (via YunoHost):
- #Fail2Ban
- #Friendica -> https://elenarossini.fr/profile/ele/
- #GoToSocial (this account!)
- #LinkStack -> https://elena.social
- #Pixelfed -> https://photos.elenarossini.com/ele
On Ubuntu:
- Fail2Ban
- My #Ghost blog/newsletter -> https://news.elenarossini.com
- #Varnish cache
I'm highly aware of my privilege and how lucky I am to be doing all this. But can I confess I'm a little bored? Thankfully I may have another big project on the horizon: upgrading my VPS and installing / self-hosting #PeerTube. But that will be for another week. Resting now and enjoying this sense of empowerment / digital sovereignty. Very grateful to be in this position.
Wishing you all a fantastic week!
What kind of issues or concerns might I have if I shut down one kind of AP server software and then set up a different AP server on the domain previously occupied by the now decommissioned first AP server?
(I don’t think the soon-to-be-shutdown server has a self-destruct.)
Nextcloud: Round 3 (or 4 or 5)
I’ve once again started the process of installing and setting up Nextcloud on one of my servers. It occurs to me that my Nextcloud instances always die a slow death. Something about that piece of software, I think, sort of just falls apart over time. This time I’m attempting to future proof it a little bit more than the previous times, but honestly I fully expect it to go about the same as usual. Then again, historically I have installed all kinds of plugins (or apps) and was running it on fairly low powered hardware. Setting it up on some decently powerful hardware on this go around though. I’ll also try to be more conservative with the app installs as well.
I might actually set up two separate instances and federate them together. Perhaps if I maintain multiple servers they’ll survive a bit longer? Or I’ll just be creating twice the amount of tinkering and maintenance for myself.