chris

joined 2 years ago
[–] chris@programming.dev 2 points 1 week ago

The final thing I’ll say on this - as it directly ties back to your initial post. Don’t become paralyzed and neglect to start. Flip a coin, dartboard, whatever to pick your first one - there are no wrong answers. The truth is you’ll likely tear it down and redo it a half-dozen times before you are satisfied.

[–] chris@programming.dev 2 points 1 week ago (2 children)

Well, if you like sandboxing, Docker is absolutely for you!!

With regards to the self-hosted aspect, pick one that really interests you, and get it up and running. That will give you experience and confidence going forward. The remaining items will be mostly cookie-cutter additions. If I also host that same item, I’d be happy to share samples of how I did it.

[–] chris@programming.dev 3 points 1 week ago

Comma’s save lives…

[–] chris@programming.dev 5 points 1 week ago

Agreed.

On a separate note, do we need to discuss your water adhesion issues? 🤣🤣

[–] chris@programming.dev 2 points 1 week ago

Nor is it brain science… :)

Yeah, I guess over my life I’ve acquired a lot of knowledge in a very niche field. I think of it as relatively easy, but I know it isn’t easy for everyone. But, hey, that’s why there are so many of us willing to teach you how to fish.

[–] chris@programming.dev 2 points 1 week ago

Agreed - answering the first questions - and deciding where you are willing to accept risk is a huge portion of the process.

Raspberry Pi’s are a huge gateway drug. :) My kubernetes cluster is 4 pi 4B’s in a rack. Great for learning and polishing skills.

[–] chris@programming.dev 6 points 1 week ago (8 children)

Self hosting what? I assume a piefed instance, but knowing for sure would be good. I host mastodon, but not piefed. The differences between those should be relatively minor.

The basics are similar:

  1. Chose a backend platform (a vm in someone else’s cloud, your own network, etc.)
  2. Spin up a vm
  3. load docker or similar (I use both docker and k3s)
  4. Instantiate your containers
  5. get a domain chosen and ssl certs in place
  6. put a reverse proxy in place
  7. open everything up to the world
  8. profit

I’d start simple and grow as you become more confident in your skills. It’s not rocket surgery - if you have advanced skills, you’ll be fine. Even playing with 1-6 above would be good for skill building.

There is nothing illegal about what you’ve stated thus far - so I’m not sure why you are approaching this from a secretive “throw away” standpoint. Why do you think secrecy is needed?

Your number 1 question can be quite involved, so that probably needs to be probed the most.

For 2 I’d do docker - very simple and straightforward.

For 3 it’s just getting your vm setup right. I’d probably recommend Ubuntu server and then put docker on that. Tons of guides for doing that. You could use other OS flavors, but Ubuntu is a good first choice.

[–] chris@programming.dev 30 points 1 month ago (2 children)

Ye olde hornograph attack, you mean…

[–] chris@programming.dev 6 points 1 month ago

The comments say everything. Buy anything other than a Brother printer and you are a chump.

[–] chris@programming.dev 10 points 1 month ago

Pretty smooth sailing at the moment. I’ve got:

  • sonarr
  • radarr
  • jackett
  • bazarr
  • transmission
  • kuma uptime
  • grafana
  • promethius
  • blackbox
  • mastodon
  • traefik
  • authelia
  • forgejo
  • immich
  • syncthing

All running on a 4 node raspberry pi kubernetes cluster.

[–] chris@programming.dev 5 points 8 months ago

WITAH is wrong with his hands?!?!?!

[–] chris@programming.dev 1 points 8 months ago

I use 7zip on my Mac every day. Whatchu talking’ ‘bout, Willis?

view more: next ›