56
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jun 2023
56 points (100.0% liked)
Selfhosted
60177 readers
466 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
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!
founded 3 years ago
MODERATORS
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.
Following the instructions using wsl and I get met with the following error after running the playbook:
"fatal: [myuser@example.com]: 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?