Install the thing:
|
1 |
aptitude install ftp-proxy |
Edit /etc/proxy-suite/ftp-proxy.conf and set your destination:
|
1 |
DestinationAddress proxy-me.to-this.server.com |
Run it in daemon mode (as root of course):
|
1 |
ftp-proxy -d |
Note it will run on port 2121 by default.
Have a vm? Added a disk? Disk not visible? Check your hosts:
|
1 |
% ls -l /sys/class/scsi_host/ |
Rescan one:
|
1 |
echo "- - -" > /sys/class/scsi_host/host2/scan |
Works like a charm.
OwnCloud is a neat gadget for putting your files up somewhere and getting them back in a nicer interface than the usual directory index + it has document versioning and a bunch of other features. This post is basically just a huge nginx configuration file which shows the config that works for me using a self-signed certificate.
This seems like a good place to jot down what and how I configured on this newly installed Debian 7 so here’s notes.
Continue reading
Condensed steps to create the certificate:
|
1 2 3 4 5 6 7 8 9 |
mkdir my-ssl-certificate cd my-ssl-certificate (umask 077 && touch host.key host.cert host.info host.pem) openssl genrsa 2048 > host.key openssl req -new -x509 -nodes -sha1 -days 3650 -key host.key > host.cert ...[enter *.domain.com for the Common Name]... openssl x509 -noout -fingerprint -text < host.cert > host.info cat host.cert host.key > host.pem chmod 400 host.key host.pem |
Now put those files somewhere (feel free to rename “host” to anything else like “mydomain.tld”). Here’s the nginx config for an ssl certificate with forcing https:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
server { listen 80; server_name thedomain.com; rewrite ^ https://$server_name$request_uri? permanent; # enforce https } server { listen 443 ssl; server_name thedomain.com ssl_certificate /etc/nginx/ssl/host.cert; ssl_certificate_key /etc/nginx/ssl/host.key; access_log /var/log/nginx/stuff-access.log main; error_log /var/log/nginx/stuff-error.log info; root /var/www; } |
Courtesy of Justin Samuel:
This is a very trivial function which I realized I need. Frequently. So instead of rewriting it a jillion times might as well put it here. All that it will do is print out an array of arrays in the same way MySQL does it:
|
1 2 3 4 5 6 |
+-------+--------+-------------------------------+----------------+ | width | height | desc | file | +-------+--------+-------------------------------+----------------+ | 200 | 150 | Lorem ipsum dolor sit ametist | /var/www/file | | 600 | 250 | Lorem ipsum dolor sit ametist | /var/www/file2 | +-------+--------+-------------------------------+----------------+ |
I’ve seen more than one frontend developer getting baffled by the fact that, once they package their vagrant box and try to load it to another developer’s computer the network doesn’t work. First noticeable clue is that eth0 becomes eth1.
Every once in a while, searching for solutions will give you a more interesting problem. Yesterday, while looking SQLite data types I ran across an interesting exploit which can be used to fetch the /etc/passwd file on a UNIX filesystem.
The functionality that /etc/hosts offers is immensely useful when you happen to do web development stuff. Thing is that sometimes you need to make other machines utilize these very simple DNS redirections. For example, today I had to make an iPad open a website from my local development VM. You can’t edit an iPad’s hosts file (at least not without some serious jailbreaking and whatnot). Hence, dnsmasq to the rescue!
Since July 2012 I’ve been using an iMac as my primary workplace computer. There was some friction in the beginning since Macs have some concepts slightly different from PCs but eventually I got used to it, even up to a point where I genuinely liked some ideas. The sloppy-focus mode of the mouse for example: you need to click on a window once to get focus and second time to click on a link in the window (for example). Initially I thought this a bad idea but as it turns out, with 20 windows spread across your desktop, accidental clicks are largely prevented by this.
Today I noticed that, in fact, Mac OS X really has a thought out filesystem layout. While GNU/Linux draws from its UNIX background (and BSD and OS X to some extent at some areas), OS X has essentially the layout below.