Josh jvillama

	command	usage
	git init	Creates an empty Git repository in the specified directory.
	git clone <repository name>	Clones a repository located at <repository name> onto your local machine.
	git add <directory>	Stages only the specified changes for the next commit. Replace <directory> with a <file> to change a specific file.
	git add .	Stages new files and modifications without deletions
	git add -A	Stages all changes
	git add -all	Equivalent to git add -A
	git add -u	Stages modifications and deletions without adding new files
	git add --update	Equivalent to git add -u
	git commit -m ”<message>”	Commits the staged snapshot. replace <message> with the commit message.

Simple automated GIT Deployment using GIT Hooks

Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.

How it works

You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.

Backend Development

node.js
- Installation paths: use one of these techniques to install node and npm without having to sudo.
- Node.js HOWTO: Install Node+NPM as user (not root) under Unix OSes
- Felix's Node.js Guide
- Creating a REST API using Node.js, Express, and MongoDB
- Node Cellar Sample Application with Backbone.js, Twitter Bootstrap, Node.js, Express, and MongoDB
- JavaScript Event Loop
Node.js for PHP programmers

One-line Tree in Python

Using Python's built-in defaultdict we can easily define a tree data structure:

def tree(): return defaultdict(tree)

That's it!

	import requests
	import pandas as pd
	from bs4 import BeautifulSoup
	import random


	reviewlist = []

	def getRandomProxy():
	# Using Proxy

	"scripts": {
	"dev": "node .dev/webpack.dev.server.js",
	"dev-prod": "node .dev/webpack.dev.server.js --production",
	"build": "rimraf ./dist && webpack --config .dev/webpack.config.production.js --colors",
	},
	"devDependencies": {
	"@babel/core": "7.0.0-beta.38",
	"@babel/plugin-proposal-class-properties": "7.0.0-beta.38",
	"@babel/plugin-proposal-decorators": "7.0.0-beta.38",
	"@babel/plugin-transform-classes": "7.0.0-beta.38",

	// Lefalet shortcuts for common tile providers - is it worth adding such 1.5kb to Leaflet core?

	L.TileLayer.Common = L.TileLayer.extend({
	initialize: function (options) {
	L.TileLayer.prototype.initialize.call(this, this.url, options);
	}
	});

	(function () {

	heroku addons:add pgbackups --remote staging
	heroku addons:add pgbackups --remote production
	heroku pgbackups:capture --remote production
	heroku pgbackups:restore DATABASE `heroku pgbackups:url --remote production` --remote staging

	1) backup production database:
	heroku pgbackups:capture --expire --remote production

	2) obtain url string to backup from step 1:
	heroku pgbackups:url --app production_app_name --remote production_app_branch_name

	3) transfer backup from production to staging app:
	heroku pgbackups:restore DATABASE 'production_app_backup_url_string_from_step_2' --app production_app_name --app staging_app_branch_name

	var myApp = angular.module('myApp').config(function($httpProvider) {
	$httpProvider.defaults.headers.post['X-CSRFToken'] = $('input[name=csrfmiddlewaretoken]').val();
	});