[Article] [Draft] SSH workflow best practices

Hackerspace
#1

https://www.joyent.com/blog/automatic-dns-updates-with-containerbuddy

http://www.macadamian.com/2017/01/24/docker-machine-basic-examples/

https://awesome-docker.netlify.com/

http://www.tldp.org/HOWTO/ppp-ssh/

https://nathanleclaire.com/blog/2015/11/10/using-ansible-with-docker-machine-to-bootstrap-host-nodes/

https://uisapp2.iu.edu/confluence-prd/pages/viewpage.action?pageId=280461906

http://dustwell.com/how-x-over-ssh-really-works.html

1 Like
#2

Oh FYI, this is one of the end goals we should be striving for with computing:

#3

Step 1. Purchase SSH Tectia
Step 2. Install and configure
Step 3. Share keys
Step 4. Profit! (I mean collect underpants)

Yes yes i know, precompiled lack of trust expensive blah blah. Bottom line, it works, its repeatable and some very large businesses responsible for insane amounts of money are making good use with no casualties.

#4

Step 1. Purchase SSH Tectia

SFTP/SCP cannot do recursion well. Nor does one need to “purchase ssh”.

You want repeatable use ansible:

Don’t want to use ansible to sync between 1:n^th size clusters then use rsync:

local to remote

rsync -avH /home/localuser/testfile1 -e ssh [email protected]:/home/adam/testfile1

remote to local

rsync -avHe ssh [email protected]:/home/adam/testfile1 /home/localuser/testfile1

https://calomel.org/rsync_tips.html

#5

My post was part sarcasm part experience and most definitely one no likely to be implemented :slight_smile:

1 Like
#6

ah. well humorist sarcasm never really comes off in text so no worries. :smiley: