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
I currently have a alpine linix VM where I had one time SSH'd into the remote server to exchange logon keys.
This means I can run my scripts without username and login credentials I just need to point to a key file instead.
I might be overthinking it like you said.
Though essentially I am trying to build a docker image of this same setup and can see I will need llfp and cron. Just not sure how to handle the key file at this point.
What do you mean by handling the keyfile?
You can generate your ssh keys outside of docker and make them available in the container through a mounted directory. You will need to manually copy the public key to your remote host
authorized_keysfile anyway.Ahh yes that's what I was looking to do.
I was thinking if I already have a key file on the remote and local servers then I may not need shh installed on the docker container to do this setup.