Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).
| from django import forms | |
| class PhotoForm(forms.Form): | |
| image = forms.ImageField() |
| from mincepie import mapreducer, launcher | |
| import gflags | |
| import glob | |
| import leargist | |
| import numpy as np | |
| import os | |
| from PIL import Image | |
| import uuid | |
| # constant value |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| __author__ = "Adrien Pujol - http://www.crashdump.fr/" | |
| __copyright__ = "Copyright 2013, Adrien Pujol" | |
| __license__ = "Mozilla Public License" | |
| __version__ = "0.3" | |
| __email__ = "[email protected]" | |
| __status__ = "Development" | |
| __doc__ = "Check a TLS certificate validity." |
| -- just the city resource | |
| SELECT DISTINCT ?citylabel ?countrylabel ?pop | |
| WHERE { | |
| ?city rdf:type dbpedia-owl:City. | |
| ?city rdfs:label ?citylabel. | |
| ?city dbpedia-owl:country ?country. | |
| ?country rdfs:label ?countrylabel. | |
| ?city dbpedia-owl:populationTotal ?pop . | |
| FILTER ( lang(?countrylabel) = 'en' and lang(?citylabel) = 'en' and ?pop>10000) |
| pre { | |
| font-family: monospace; | |
| white-space: pre-wrap; /* css-3 */ | |
| white-space: -moz-pre-wrap; /* Mozilla */ | |
| white-space: -pre-wrap; /* Opera 4-6 */ | |
| white-space: -o-pre-wrap; /* Opera 7 */ | |
| word-wrap: break-word; /* Internet Explorer 5.5+ */ | |
| /* | |
| padding: XX; | |
| margin: XX; |
Using pg.connect is the way to go in a web environment.
PostgreSQL server can only handle 1 query at a time per conenction. That means if you have 1 global new pg.Client() connected to your backend your entire app is bottleknecked based on how fast postgres can respond to queries. It literally will line everything up, queuing each query. Yeah, it's async and so that's alright...but wouldn't you rather multiply your throughput by 10x? Use pg.connect set the pg.defaults.poolSize to something sane (we do 25-100, not sure the right number yet).
new pg.Client is for when you know what you're doing. When you need a single long lived client for some reason or need to very carefully control the life-cycle. A good example of this is when using LISTEN/NOTIFY. The listening client needs to be around and connected and not shared so it can properly handle NOTIFY messages. Other example would be when opening up a 1-off client to kill some hung stuff or in command line scripts.
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
| upstream discourse { | |
| #fail_timeout is optional; I throw it in to see errors quickly | |
| server 127.0.0.1:4578 fail_timeout=5; | |
| } | |
| # configure the virtual host | |
| server { | |
| # replace with your domain name | |
| server_name discourse.example.com; | |
| /** | |
| * Object.prototype.watch polyfill | |
| * @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/watch | |
| * | |
| * Known limitations: | |
| * - `delete object[property]` will remove the watchpoint | |
| * | |
| * Based on Eli Grey gist https://gist.github.com/eligrey/384583 | |
| * Impovements based on Xose Lluis gist https://gist.github.com/XoseLluis/4750176 | |
| * This version is optimized for minification |
