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
Install wsl for windows Ubuntu default.(can install wsl in PowerShell).
Install Ansible in wsl, create ssh keys to your VPS, follow those instructions.
On my Ubuntu server I did literally nothing but the ssh key generation.
I think this is one of the more sensible answers here. If your workstation is windows, then utilize WSL for ansible and deploy onto a ubuntu or debian host (I'm assuming it works fine on debian, I used ubuntu). You might run into some issues with ansible dependencies as the readme doesn't seem to cover everything from what i remember, but once ansible works and has the correct configs, deployment is super easy.
Yeah Ansible I had to set the path variable and did the ssh key generation. Other than that my lemmy was up and running in like 10 minutes all automated. You can go back and change the config by rebuilding the yaml. It's not bad at all.
I ran into some dependency issues(needed to install ansible-collection-community-docker on my fedora workstation), but after that it ran fine and installed everything first run. I made some adjustments to the inventory config afterwards, but aside from that it just worked.
sadly, none of these is worth implementing. Remember, Windows is designed to break. MS has millions of tiny levers to flick, and they don't care if their mindless flicking fucks up your work. Worse of all, the law protects them from flicking to destroy you out of spite. Best thing to do is just use linux. Or design our own OS. Since Linux itself is slowly collapsing under the weight of MS bullshit. And god forbid that shithole IOS.
Following the instructions using wsl and I get met with the following error after running the playbook:
"fatal: [[email protected]]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host example.com port 22: Network is unreachable", "unreachable": true}"
Where do I enter my ssh info?