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
Nextcloud to replace Google drive/docs. Jellyfin or plex for media. The arrs to aquire media (if you have the patience). A blog? A game server to play with friends.
I suggest using docker and docker-compose as it makes everything way easier. It does still take time and it can be frustrating but it is very rewarding.
Crosspost from the duplicate
Years ago I selfhosted Nextcloud and found this interaction just as clunky as using google drive. Now I'm just using SFTP which has much less overhead and it integrates beautifully with just about any file manager on Linux. Then again, using it on windows is a pain as far as I know.
Do you happen to know if it can be installed on Docker for Windows?
probably, docker is docker, should work independently of the host OS
Thanks, figured as much. My main issue is Docker is annoying on Windows and trying to give it sufficient storage and configuring that with Docker has always been something I just never figure out.
While there is a docker version for windows (server I believe) the last time I checked it could only run windows containers (so basically none). The Linux support never got out of beta. I think now they are just saying use windows subsystem for Linux (WSL) for that.
I have been quite happy with docker on a Linux virtual machine hosted on a windows server (I know not the "normal" way to do it but since I am a windows Server admin at work it worked best for me).
The reason that you cannot run Linux containers on windows by default is that docker is no full fledged virtualization Software it sill uses the kernel of the host system. And a Linux container needs a Linux host system.
Here is a forum thread from the docker forum. You might find some valuable insights there: https://forums.docker.com/t/docker-run-linux-container-in-windows-2019/128196
WSL2 is Linux on a virtual machine. Docker for Windows is running in a VM.
I'm also a weirdo though, I'm using podman instead (and may switch to nerdctl).
Never hears of nerdctl. What is the feature that would make it better than podman for you?
I using and deploying to kubernetes. Nerdctl has a docker API but it's completely backed by k8s. So, for regular dev I'd just need a k8s cluster and not k8s + something else to build the images and push them into the k8s image repository.
I think there are two "Docker for Windows" one is docker desktop used on windows client OS where you can switch between windows and linux containers. This is the one where it runs a VM for the Linux containers but it's designed for development and not so much for hosting (at least I have not get it to work for this)
And there is the docker that's included in Windows Server wich can only run windows containers but those natively and suitable for hosting dotnet web services on scale.
Docker is definitely worth the time investment.
If OP wants to go one level deeper: Ansible.
Does ansible make sense for a single server? I like the concept but I don't know if It makes sense for my purpose.
It makes sense in terms of reproducibility.
Imagine if your server gets compromised, you accidentally break it, or you just want to move to a cheaper provider or a different server. Do you want to have to tweak it all over again, and fix bugs that you figured out how to fix 6 months ago and you don't remember?
I'd rather have some yaml files that do it for me. And it's a new skill as well.
That makes sense thanks. I did have trouble figuring out where to start with ansible, do you have any advice about that?
You're welcome!
I'm still an ansible newbie myself. I first heard about it in this video; https://m.youtube.com/watch?v=Z7p9-m4cimg&pp=ygURV29sZmdhbmcgYW5zaWJsZSA%3D
Then I just figured out by googling and reading the docs / stack exchange.
I started by doing something simple, e.g. write an ansible playbook to update a raspberry pi on my network. Then went from there to launch a small VPS, googling each step that I'd normally do to configure a server, and run them all one after the other on ansible.
I love Wolfgang. His videos are so high quality