IngeniousRocks (They/She)

I have opinions. Some of them are terrible. For this I am sorry.

Don’t DM me without permission please

  • 1 post
  • 84 comments
Joined 2 years ago
Cake day: December 7th, 2024
  • It can be a lot, I’m a year in and still feel like a noob. I’ve only just now moved from being behind a cloudflare tunnel to being behind a proper reverse-proxy. That doesn’t mean anything to you yet, it will!

    There’s plenty of guides to get started. Louis Rossman did a 12hr guide on selfhosting your entire life (I still haven’t watched the whole thing).

    I started here with this guide: https://youtube.com/watch?v=IuRWqzfX1ik It’s short, sweet, easy to digest.

    If you wanna start super easy.

    1. Buy a domain
    2. Set up a cloudflare tunnel
    3. Roll out whatever using docker
    4. Point your tunnel to the docker ports.

    This works around CGNAT, and bypasses the need for port forwarding BUT it keeps you reliant on a corpo and keeps all your data moving through their servers, which means low upload limits and your traffic could (see: will) be monitored.

    Anything your exposing to the internet should be considered disposable until you know enough to keep a server online safely. Keep backups, offsite. If you have 1 backup, you have no backups. If you only have onsite backups, you have no backups.

    Most servers you’re gonna want to run will come with relatively detailed documentation for rolling things out, but when it comes to security you’ll be on your own. This is because the optimal security configuration for your needs depends on your threat model. Until learning proper network security, I’d recommend paying for a VPS to host your servers on and connecting via proxmox or a similar tool, lest you risk leaving gaping security holes in your home network.

    Have fun, happy selfhosting, feel free to DM me if you need assistance, I’m not on lemmy often anymore but my inbox goes to my RSS aggregator so I’ll see it.

    oh, and PS. Don’t selfhost your email, it’s not worth the hassle.

  • For the future regarding Flash drives. The different filesystems used by Mac and Windows (APFS and NTFS) can be used on Linux.

    APFS support is sometimes built in, but if not can be installed by following the guide here(github). Note that this will require building from source, which can be scary if you haven’t done it before, but is pretty easy if a bit tedious. This repo in particular has a good guide.

    For NTFS support, you can install the read-only ntfs package, or the read-write ntfs-3g package. This utilizes the FUSE so you’ll need the ‘fuse’ tools as well.

    For the older Apple HFS+ filesystem you’ll need hfsprogs. This is available from the AUR on Arch based distros, or in the Bookworm repo for Debian distros. For other distributions you may need to compile from source which you can find from the Debian package page.

  • This is a fantastic approach.

    I wanted to learn web-dev so I built a blog and a web hostable 5e character generator. Ended up learning authentication, HTTP stuff, database management, and learned CSS and HTML to handle the frontend (backend is Python).

    They’re not production ready, there’s not even a proper server built in, just a basic wsgi dev server, but I’m proud of it and it taught me a ton!

  • Just an example:

    I’m a programming student. In one of my classes we had a simple assignment. Write a simple script to calculate factorials. The purpose of this assignment was to teach recursion. Should be doable in 4-5 lines max, probably less. My coed decided to vibe code his assignment and ended up with a 55 line script. It worked, but it was literally %1100 of the length it needed to be with lots of dead functions and ‘None->None(None)’ style explicit typing where it just simply wasn’t needed.

    The code was hilariously obviously AI code.

    Edit: I had like 3/4 typos here