Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
In case of Raspbian, you can create a
wpa_supplicant.conf
in the boot partition with:and a empty
ssh
file.For the user config, since bullseye you need to make an account on first boot, that can be done with a
userconf
file, but it's a bit more involved. You can see how to do it at the end of This blog postIm planning on putting debian on it, so I think its slightly different because e.g. theres no raspberry pi user
Why not use Raspberry Pi OS? It's based off of Debian.
If you're planning on using plain Debian and the challenges that come with it, you probably should start with one of the pre-built images from the Debian foundation. You can mount the root partition with either a running linux box or WSL2. Then you can chroot into it to setup the wpa_supplicant.conf in the /etc/ folder and ensble sshd.
Thats something like what I'll be trying. I am on a linux laptop so I can do all that.