scp and proxy

With scp you can use -J directly. Like scp -J user@hiddenhost:/directory/some/ . for example. As usual, the 'user' part can be left out if the user is the same on the hosts in question.

sshfs with proxy

The ssh command has the useful '-J' option which allows you to connect via a proxy host. Very useful for hosts which are not directly reachable from the current network you are on. Since '-J' corresponds to the ProxyJump directive, you can achive the same goal with sshfs like this: sshfs ~/mountpoint/ -o this is very useful.

Setting up ssh-agent from cmdline

Sometimes I write content via a ssh connection, using vi as my editor. In order to deploy new content, it is useful to have ssh-agent running. Ony way to do that is like this:

[nikola] tingo@kg-core2:~/personal/projects/nikola % eval `ssh-agent -c`
Agent pid 65221

This command sets the environment variables SSH_AUTH_SOCK and SSH_AGENT_PID, and you are ready to add keys with ssh-add. When you are finished, you just use ssh-agent -k to kill the agent.

Nikola - beware of the slug!

Nikola uses the slug of a post or page to generate the output files and directories. So if you (for any reason) decide to rename a source file, remember to rename the slug also. Or else you will spend frustrating time wondering why nikola persists in rendering something at an old location. Perhaps you will try clearing the cache, removing the doit database, or even clearing the output directory and getting even more frustrated when it doesn't help.

Deployment with Nikola

I now have manual deployment working. So now I set up a series of deployment commands in and try the out

    'default': [
        'cd output; git add .',
        'cd output; git commit -q -m "content added"',
        'cd output; git push web',

Will it work? Update: yes it works nicely. Nikola scores again!

Read more…