$ sudo apt-get install libguestfs-tools
$ guestfish --rw --add testserver-rootdisk
Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.
Type: 'help' for help on commands
'man' to read the manual
'quit' to quit the shell
><fs> run
100% ⟦▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒⟧ 00:00
><fs> list-filesystems
/dev/sda1: ext4
><fs> mount /dev/sda1 /
><fs> emacs /etc/resolv.conf
><fs> exit
Edit: Disk image pre-allocation can be done with
QEMU-provided tools, which may or may not be a more kosher approach.
Must investigate.
description "Your App"
author "Your Name "
start on (net-device-up and local-filesystems)
stop on shutdown
respawn
script
export HOME="/root/of/django/app" # i.e. where "manage.py" can be found
export PATH="$PATH:/root/of/django/app/env/bin" # "env" is our virtualenv
export DJANGO_SETTINGS_MODULE="settings"
export LANG="en_US.UTF-8"
cd $HOME
exec $HOME/env/bin/gunicorn -b 127.0.0.1:8000 -w 1 --log-file /var/log/gunicorn/yourapp.log app
end script
app.py:
import os, sys
sys.path.insert(0, '/root/of/django/app/')
path = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
if path not in sys.path:
sys.path.append(path)
import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()
Like the title says, the point of this post is getting autossh up when Ubuntu boots. Place this in e.g. /etc/init/autossh.conf, after which you will be
able to says things like sudo start autossh and sudo stop autossh.
description "autossh tunnel"
author "Joni Kähärä "
start on (local-filesystems and net-device-up IFACE=eth0 and net-device-up IFACE=eth1) # assuming we have multiple interfaces
stop on runlevel [016]
respawn
respawn limit 5 60
exec autossh -M 0 -N -R 10000:192.168.1.1:22 -o "ServerAliveInterval 60" -o "ServerAliveCountMax 3" -o "StrictHostKeyChecking=no" -o "BatchMode=yes" -i /home/user/.ssh/id_rsa username@hostname
The “start on” line ensures that autossh won’t start before all network interfaces are up, and “stop on” will stop autossh (if it’s running) on runlevels 0, 1 and 6 (halt, single user and reboot, respectively). The “respawn limit” line will ensure that if autossh goes crazy, it will not be started again. Note that the plain “respawn” line is still needed to actually respawn the process.
Of the command line options only the first one (-M 0) is for autossh, the rest are regular ssh options.
-M 0 denotes that autossh should not set up it’s own monitoring channel and should instead rely on ssh terminating itself when it decides that the connection’s been lost (see ServerAlive* options below).
-N means “Do not execute a remote command”, i.e. just set up the connection and port forward.
-R 10000:192.168.1.1:22 means that we want TCP port 10000 on the remote host forwarded to port 22 on local host (192.168.1.1).
-o "ServerAliveInterval 60" send “keepalive” messages every 60 seconds
-o "ServerAliveCountMax 3" terminate ssh if three consecutive ServerAliveInterval inquiries fail (and thus respawn)
-o "StrictHostKeyChecking=no" don’t fail if remote server’s identity changed
-o "BatchMode=yes" don’t attempt to use a passphrase if public key login fails
-i /home/user/.ssh/id_rsa the private key we’ll use for the tunnel
username@hostname connect to this host with this username