• 0 Posts
  • 44 Comments
Joined 11 months ago
cake
Cake day: July 14th, 2024

help-circle
  • I submitted a response but if i may give some feedback, the second portion brings up:

    I am willing to pay a substantial amount for hardware required for self-hosting.

    This seemed out of place because there were no other value related questions (iirc). Such as:

    • I believe self hosting saves me money in the short term
    • i believe self hosting saves me money in the long run

    I’m sure you could also think of more. But i think it’s pretty important because between cloud service providers and any non-free apps you want to use, it can be quite costly compared to the cost of some hardware and time it takes to set things up.

    The rest of my responses don’t change but if you’re wanting to understand the impact of money in all of this, i think some more questions are needed

    Best of luck!




  • Foundry was the 2nd thing i started self hosting (the first being pihole). Have had it running for 5 years now.

    Other than that i only recently started expanding my self hosting:

    • tandoor recipes
    • navidrome (for music, mentioning it since it isn’t the typical media server recommendation)
    • personal knowledge management (pkm) static website that i build with hugo
    • umami analytics
    • Remark42 for comment system on one of my internal static websites
    • a few smaller things that i built. One is a discord bot from before i started hating discord, and then a few web apps that i haven’t open sourced yet












  • This is something that doesn’t really need to be self hosted unless you’re wanting the experience. You just need:

    1. Static website builder. I use hugo but there’s a few others like jekyll, astro
    2. Use a git forge (github, gitlab, codeberg).
    3. Use your forges Pages feature, there’s also cloudflare pages. Stay away from netlify imo. Each of these you can set up to use your own domain

    So for my website i just write new content, push to my forge, and then a pipeline builds and releases the update on my website.

    Where self hosting comes into play is that it could make some things with static websites easier, like some comment systems, contact forms, etc. But you can still do all of this without self hosting. Comments can be handled through git issues (utteranc.es) and for a contact form i use ‘hero tofu’ free tier. In the end i don’t have to worry about opening access to my ports and can still have a static website with a contact form. All for free outside of cost of domain.


  • Im not familiar with doku wiki but here’s a few thoughts

    • privacy policy is good to have regardless of what you do with rest of my comments
    • your site is creating a cookie “dokuwiki” for user tracking.
    • cookie is created regardless of user agreement, rather than waiting for acceptance (implied or explicit agreement). As in i visit the page, i click nothing and i already have the dokuwiki cookie.
    • i like umami analytics for a cookieless google analytics alternative. They have a generous free cloud option for hobby users and umami is also self hostable. Then you can get rid of any banner.