78
Thinking of getting into self hosting but I'm a complete noob (lemmy.zip)
submitted 8 months ago by SuperSpruce@lemmy.zip to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments

I think of myself as technically inclined. I have installed Linux multiple times and have basic command line knowledge, and I've programmed in many languages, with the most experience making a static website game using HTML/CSS/JS.

Additionally, I own the superspruce.org domain (my registrar is Dynadot), but I don't really know how to wield the power of owning a domain. I also have some spare computers to be used for hosting, a 2009 laptop running Lubuntu and a 3900X+32GB RAM desktop other running KDE Neon, but I'm also open to experimenting with cloud hosting too (I know, sacrilege here).

However, I don't know much about the TCP/IP protocol or other networking protocols. I'm happy to learn, but the curve would need to start gently.

I would want to try hosting my websites, and also a personal non-federated Lemmy instance to serve as a archivable forum for my games. Even if it's not very useful, it's great experience.

you are viewing a single comment's thread
view the rest of the comments
[-] breadsmasher@lemmy.world 11 points 8 months ago

Some things, or points, to consider.

  1. Do you want whatever you’re hosting to be internet accessible? Or local network only? As it being able to access from anywhere
  2. If its something you want to be able to use full time, youll eventually want a dedicated machine. I have an *arr stack etc, which I share with a private group. Eventually downtime was an actual consideration and interrupted my normal usage of my main machine. I picked up a secondhand elitedesk mini Pc for £150 and its doing really well.
  3. Potentially make use of tools like Zerotier for private networking (others hopefully will chime in with alternatives, but I have had good success with zerotier.
  4. How do you want to host it, and are you willing to learn? Get a bit of knowledge on docker or podman but this is hardmode as most examples will be docker specific. Using containers will make things simpler. The most complicated part IMO is networking but even then its more docker networking stuff than general TCP/IP - (like you mentioned in your post)
  5. OS - you mentioned using Linux? I personally use Ubuntu just out of defaulting to what i’ve previously used. But Im currently using Manjaro on my non host PC, which I am liking
  6. Keep things secure - the more you expose to the internet, the more risk. Keep exposure as small as possible, use letsencrypt or alternatives for anything you want to access over the internet etc

good luck have fun!

[-] SuperSpruce@lemmy.zip 2 points 8 months ago
  1. I want it to be internet accessible. A friend taught me how to use nginx for the local network, although I've forgotten that now.
  2. My previously mentioned computers are computers I don't use that much, especially the old laptop. My main computer is a 2021 ROG Strix G15 Advantage Edition. I won't be hosting from that.
  3. Private networking is just hosting over a LAN, right?
  4. Does Docker work well on old hardware and is Docker easy to learn?
  5. I have the most knowledge on Ubuntu based distros. I don't think Manjaro, a bleeding edge rolling distro, is good for hosting.
  6. How do I use let's encrypt or something to boost my security?
[-] HumanPerson@sh.itjust.works 3 points 8 months ago* (last edited 8 months ago)

Not who you're replying to but here are some answers:

  1. For internet accessibility there will be things to consider. Do you want non-techy friends or family on it? If so you may need to port forward or use a vps. Some ISPs don't allow port forwarding, but there are a million solutions to this. Otherwise you can use a VPN to connect to your network and have access to your server that way.
  2. Old laptops are great for hosting. They are typically more power efficient than desktops, although the expansion options aren't great if you don't like jank.
  3. Not sure.
  4. Yes and kinda. It is super light unless you're running it on really old stuff. It is easy once you learn. I recommend docker compose to keep everything in a single config file. You can use watchtower to keep things automatically updated.
  5. I like Debian. I too use a rolling distro on my desktop, and some people do like rolling distros for servers. The idea of stable release distros like Debian are that they are consistant and you don't have to worry about updates breaking things. The idea of rolling distros on a server is that you will only ever have to deal with small updates rather than giant ones that may break everything (like between Debian versions). I would not recommend manjaro on a server, or at all really. They have a habit of holding back packages for no real reason and causing dependancie issues. If you like rolling I would try Tumbleweed or Arch with Archinstall. There is also Endeavor OS which is basically easier Arch.
  6. Letsencrypt is for https certificates. You can use self signed certificates, meaning they are made by your computer rather than letsencrypt's servers, but you will get warnings in your browser and app interfaces for your services may not work. They are just as secure for personal use. Don't do http on the internet. That is bad. You know the VPN ads that say hackers can steal all your bank passwords if you don't buy their VPN, well that is not true because your bank uses https. If you access your services through http over the internet, someone will get your password eventually. Do whatever you want on home network though.
[-] SuperSpruce@lemmy.zip 1 points 8 months ago

Maybe I should just cloud host, as it costs the same as a VPN. But then again, a VPN will also protect my privacy. Do I need to use let's encrypt if I use a VPN or cloud host if I want to be secure?

this post was submitted on 26 Feb 2024
78 points (97.6% liked)

Selfhosted

40183 readers
401 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz