abcsun

November 2nd, 2013 Setting up Push-to-Deploy with git

I first set up a push-to-deploy system with git and puppet for a side project a few years back. It worked so well I transitioned NMC's development process onto it for all of our new projects starting last year. It offers the simplicity of the "push-to-deploy" model Heroku pioneered, with full control and flexibility over the operating system environment.

I've started thinking about my next iteration of this system for Didsum, and using pushing for more than just deployment purposes. The Push-to-______ pattern is powerful and easy to use, once you know how the pieces fit together. In this post, I'll walk through the setting up Push-to-Deploy from the ground up.

(I'm assuming a working knowledge of: terminal, git, and a scripting language.)

	queryset = Garage.objects.filter(user=user).exclude(status=Garage.TEMPLATE).order_by("-created_at")
	page = self.paginate_queryset(queryset)
	serializer = GarageViewSerializer(page, many=True)
	return self.get_paginated_response(serializer.data)

	<?php

	namespace App\Http\Controllers;

	use Tymon\JWTAuth\JWTAuth;
	use Illuminate\Http\Request;
	use Tymon\JWTAuth\Exceptions\JWTException;

	/**
	* Class AuthenticationController

	DB::listen(
	function ($sql) {
	// $sql is an object with the properties:
	// sql: The query
	// bindings: the sql query variables
	// time: The execution time for the query
	// connectionName: The name of the connection

	// To save the executed queries to file:
	// Process the sql and the bindings:


	/**
	* Parse token from the authorization header.
	*
	* @param string $header
	* @param string $method
	*
	* @return false\|string
	*/
	protected function parseAuthHeader($header = 'authorization', $method = 'bearer')

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console