Jason DeWitt jasondewitt

Serving multiple webapps from different folders

November 29, 2011 developmentNginx

Few days ago I had to add a wordpress installation within the same environment where a Codeigniter app was already running happily and undisturbed.

It took me a while to figure out how to keep separate folders on the filesystem, and serve the blog from a subfolder of the main domain:

Nginx FastCGI response buffer sizes

By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk.

This process is outlined at the Nginx ngx_http_fastcgi_module page manual page.

Introduction
Determine actual FastCGI response sizes
Setting the buffer size
Verifying results

Useful commands

You may find these commands useful when adjusting file and directory permissions.

To recursively chmod directories only:

find /your/site/root -type d -exec chmod 755 {} \;

To recursively chmod files only:

	var nodecast = require('nodecast');
	var stream = nodecast.find();

	stream.on('device', function(device) {
	console.log('Found device', device.name);

	var youtube = device.app('YouTube');

	// you can change this video to anything you want
	youtube.start('v=oHg5SJYRHA0', function(err) {

	<?php
	/*
	+----------------------------------------------------------------------------------------------+
	\| Windows Cache for PHP \|
	+----------------------------------------------------------------------------------------------+
	\| Copyright (c) 2009, Microsoft Corporation. All rights reserved. \|
	\| \|
	\| Redistribution and use in source and binary forms, with or without modification, are \|
	\| permitted provided that the following conditions are met: \|
	\| - Redistributions of source code must retain the above copyright notice, this list of \|

	# Configure the reverse-proxy on port 443
	server {
	# general configs
	keepalive_timeout 30;
	listen 127.0.0.1:443 ssl;
	server_name api.example.com;

	# ssl configs
	ssl_certificate /path/to/api.crt;
	ssl_certificate_key /path/to/api.key;

	source: http://www.markbrilman.nl/2011/08/howto-convert-a-pfx-to-a-seperate-key-crt-file/

	`openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]`

	What this command does is extract the private key from the .pfx file. Once entered you need to type in the importpassword of the .pfx file. This is the password that you used to protect your keypair when you created your .pfx file. If you cannot remember it anymore you can just throw your .pfx file away, cause you won’t be able to import it again, anywhere!. Once you entered the import password OpenSSL requests you to type in another password, twice!. This new password will protect your .key file.

	Now let’s extract the certificate:

	`openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]`

	server {
	listen 80; ## listen for ipv4
	listen [::]:80; ## listen for ipv6
	server_name domain.com;
	access_log /var/log/nginx/domain.com.access.log;
	error_log /var/log/nginx/domain.com.error.log;

	root /folder/with/wordpress/installation/;

	# Include wordpress config file

	import SoftLayer.API
	from pprint import pprint as pp

	apiUsername = 'set me'
	apiKey = 'set me'

	client = SoftLayer.Client(
	username=apiUsername,
	api_key=apiKey,
	)

	# ================================================================================
	# ObjectStorageUploader.py
	# © Copyright IBM Corporation 2014.
	# LICENSE: MIT (http://opensource.org/licenses/MIT)
	# ================================================================================

	import argparse
	import os
	import math
	import http.client