Allen Chun ChunAllen

Terminology

View: Also called a "template", a file that contains markup (like HTML) and optionally additional instructions on how to generate snippets of HTML, such as text interpolation, loops, conditionals, includes, and so on.
View engine: Also called a "template library" or "templater", ie. a library that implements view functionality, and potentially also a custom language for specifying it (like Pug does).
HTML templater: A template library that's designed specifically for generating HTML. It understands document structure and thus can provide useful advanced tools like mixins, as well as more secure output escaping (since it can determine the right escaping approach from the context in which a value is used), but it also means that the templater is not useful for anything other than HTML.
String-based templater: A template library that implements templating logic, but that has no understanding of the content it is generating - it simply concatenates together strings, potenti

A Capistrano Rails Guide

by Jonathan Rochkind, http://bibwild.wordpress.com

why cap?

Capistrano automates pushing out a new version of your application to a deployment location.

I've been writing and deploying Rails apps for a while, but I avoided using Capistrano until recently. I've got a pretty simple one-host deployment, and even though everyone said Capistrano was great, every time I tried to get started I just got snowed under not being able to figure out exactly what I wanted to do, and figured I wasn't having that much trouble doing it "manually".

This guide explains the way to setup a production server using Capistrano.

Setup Capistrano on LOCAL

Capistrano is a development gem which assist the developer to run commands on the production server (something like a Heroku toolbelt)
Hence, it is installed and configured on developer's computer

# Gemfile

# Use Capistrano for deployment

Change your database RDS instance security group to allow your machine to access it.
- Add your ip to the security group to acces the instance via Postgres.
Make a copy of the database using pg_dump
- $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
- you will be asked for postgressql password.
- a dump file(.sql) will be created
Restore that dump file to your local database.
- but you might need to drop the database and create it first
- $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

the database is restored

	/**
	* This gist was inspired from https://gist.github.com/homam/8646090 which I wanted to work when uploading an image from
	* a base64 string.
	* This code is used in my startup, Zired.
	* Web: http://zired.io
	*/

	// You can either "yarn add aws-sdk" or "npm i aws-sdk"
	const AWS = require('aws-sdk')

	var debug = process.env.NODE_ENV !== "production";
	var webpack = require('webpack');

	module.exports = {
	context: __dirname,
	devtool: debug ? "inline-sourcemap" : null,
	entry: "./js/scripts.js",
	output: {
	path: __dirname + "/js",
	filename: "scripts.min.js"

	Backup:
	docker exec -t -u postgres your-db-container pg_dumpall -c > dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql

	Restore:
	cat your_dump.sql \| docker exec -i your-db-container psql -Upostgres

	#!/bin/bash
	#
	# PostgreSQL Backup Script Ver 1.0
	# http://autopgsqlbackup.frozenpc.net
	# Copyright (c) 2005 Aaron Axelsen <[email protected]>
	#
	# This script is based of the AutoMySQLBackup Script Ver 2.2
	# It can be found at http://sourceforge.net/projects/automysqlbackup/
	#
	# The PostgreSQL changes are based on a patch agaisnt AutoMySQLBackup 1.9

	upstream myapp_puma {
	server unix:/tmp/myapp_puma.sock fail_timeout=0;
	}

	# for redirecting to https version of the site
	server {
	listen 80;
	rewrite ^(.*) https://$host$1 permanent;
	}

	namespace :deploy do

	desc "Runs test before deploying, can't deploy unless they pass"
	task :run_tests do

	puts "--> Running tests, please wait ..."
	test_log = "log/capistrano.log"
	unless system "bundle exec rake > #{test_log} 2>&1" #' > /dev/null'
	puts "--> Tests failed. Run `cat #{test_log}` to see what went wrong."
	exit