I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.
These are the steps I went through to set up an SSL cert.
I hereby claim:
To claim this, I am signing this object:
!DOCTYPE html> | |
<html> | |
<head> | |
<link rel="stylesheet" href="http://netdna.bootstrapcdn.com/bootstrap/3.0.2/css/bootstrap.min.css"> | |
<title>Today</title> | |
<script src="http://code.jquery.com/jquery-1.10.2.min.js"></script> | |
<style type="text/css"> | |
body { | |
font-family: "HelveticaNeue-UltraLight", "Helvetica Neue UltraLight", "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif; | |
background-color: #B2E6FF; |
After the success of our last meetup, Hack Night, we are continuing the trend with a different kind of meetup, Office Hours.
This is a casual "geek gathering", where you can hack on a node.js project, get help/advice, or ask questions about anything node.js related. Anyone working with node.js at any level (or anyone wanting to work with it) is welcome.
Our meetups are always filled with a mix of people and skills present, and I expect this to be the same. So feel free to bring your questions pertaining to system admin/dev ops, best practices, installation issues, etc.
We are also looking for food/drink sponsors in exchange for five to ten minutes of air time to announce your product/hiring/etc. Contact Josh Finnie for details.
Attendance is free, and food and drink will be provided if we have found some sponsors. For this reason, it is mandatory that you keep your RSVP up to date. The deadline for changing your mind will be one day before the event.
$ cd /tmp | |
$ curl -O http://python.org/ftp/python/X.Y.Z/Python-X.Y.Z.tgz | |
$ tar zxf Python-X.Y.Z.tgz | |
$ cd Python-X.Y.Z | |
$ ./configure --prefix=/usr/local/python/X.Y.Z | |
$ make | |
$ make install | |
$ wget https://bitbucket.org/pypa/setuptools/raw/bootstrap/ez_setup.py -O - | /usr/local/python/X.Y.Z/bin/python | |
$ /usr/local/python/X.Y.Z/bin/easy_install pip | |
$ /usr/local/python/X.Y.Z/bin/pip install virtualenv |
#!/usr/bin/env python | |
import os | |
import sys | |
import app | |
try: | |
from setuptools import setup | |
except ImportError: |
function testWebGL() { | |
try { | |
return !!window.WebGLRenderingContext && !!document.createElement('canvas').getContext('experimental-webgl'); | |
} catch(e) { | |
return false; | |
} | |
} | |
Modernizr.load([ | |
{ |
Lately, I have been looking into Python CMSs. There are many out there, but for some reason or another Mezzanine stuck out as one I should try. Installing it is easy enough, but getting it up on running on my new favorite host, Heroku, was a bit of a challege.
Below you will find the steps that I took to get Mezzanine up and running on Heroku. Please let me know in the comments below if anything didn't work for you.
Heroku is shortly depricating Django's standard DATABASES
dictionary in favor for a package which takes OS Environment Variables and builds the required dictionary for you. This is a good thing because it makes setting up a database on Heroku very easy. The package is called dj_database_url
and it makes short work of getting a PostgreSQL database up and running with Mezzanine. Below is the code that you want to put in Mezzanine's DATABASES
section:
import dj_database_url
DATABASES = {'default': dj_database_url.config(default='postgres://localhost')}