A VPS, a reverse proxy, a password manager, and a DNS zone full of forgotten history. The autonomous stack begins to take shape.

This post is part of a series explaining the authour’s steps into self-hosting again. The earlier posts were more focused on the authour’s specific priorities and why it’s important to them. This informed both what they are deciding to self-host and the order of deployment/how things are set up. This post is the first one that takes a more technical angle, and the initial steps they took setting things up.

I enjoyed this post, and the series by the authour, because what really comes through is the sense of why they are configuring things certain ways and what their priorities are. Many other blog posts I’ve read jump straight into this step - how they configured the server. But throughout this series, I really get a sense of why the authour decided to configure it a certain way and I find that enjoyable to read. They were very systematic and thorough in building an inventory of what dependencies they have and their priorities for replacements.

This post is by Tara Tarakiyee, who works at the Sovereign Tech Agency. For avoidance of doubt, I am not the authour of the blog post.

  • Otter@lemmy.caEnglish
    2·
    6 hours ago

    Is ambitiousslab@feddit.uk also the author of the blog?

    A blurb about the article is nice and helps to convince people to click on the article, but it isn’t necessary. From what I can tell, ambitiousslab seems to be sharing things that they find interesting and doesn’t follow the pattern of the usual bot spam we deal with

    • SuspiciousCarrot78@aussie.zoneEnglish
      3·
      6 hours ago

      No idea because they failed to mention it.

      Spam isn’t just automated spam bots posting. It’s unsolicited, unexplained content. A “hey, I found this interesting because X” goes a long way towards humanising things like this but YMMV.

      • ambitiousslab@feddit.ukOPEnglish
        3·
        4 hours ago

        Hi, I’m choosing this comment to reply to everyone at once, since there’s a lot of overlap in the comments.

        I’m sorry for not following the etiquette of the community. I’ve updated the post to contain a blurb to explain why I liked the article. I hope it’s ok but if there are any problems I’m happy to amend it or change the focus of the blurb.

        I was careful to check the rules before posting, and in all other communities I actively participate in, link-only posts are completely fine, so I didn’t even stop to think it could be a problem. I now appreciate that this is not the followed norm of this community though. I can see that it could be easily misinterpreted as self-promotion, since I didn’t state I wasn’t the authour of the post. I have subscribed to this community for a while and made a couple of comments, but this is my first post here and with the posts mixed in the rest of the feed, I guess I didn’t build a good sense of the unwritten norms of the community.

        I am not the authour of the blog post. This is the personal blog post of someone who works for the Sovereign Tech Agency. I appreciate their posts because they took a very thoughtful approach to why they are self-hosting certain things. Their technical approach is an extension of the “why” they are doing it and this is very clearly and explicitly laid out. This is something I quite like, and at least in the blogs I follow, relatively unique.

        I am based in the UK. I always catch up on my RSS feeds before i go to bed, and if I see something interesting, I tend to share it on lemmy. I only woke up again now because of the heatwave here. Another lesson learned, if posting to this community again, do it while I’m available for the next few hours.

        • localghost@lemmy.todayEnglish
          2·
          3 hours ago

          Hey I appreciate you posting this. I enjoy reading through people’s thought processes when doing stuff like this to see if there’s anything I can do better. Wouldn’t have known about this author otherwise, cheers