Seth Horsley sethhorsley

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.

Add gem 'rails_12factor' to your Gemfile. This will add error logging and the ability for your app to serve static assets.
bundle
Run RAILS_ENV=production rake db:create db:migrate db:seed
Run rake secret and copy the output
From the command line: export SECRET_KEY_BASE=output-of-rake-secret
To precompile your assets, run rake assets:precompile. This will create a folder public/assets that contains all of your assets.
Run RAILS_ENV=production rails s and you should see your app.

Remember to clobber your assets (rake assets:clobber) and re-precompile (rake assets:precompile) if you make changes.

In the below keyboard shortcuts, I use the capital letters for reading clarity but this does not imply shift, if shift is needed, I will say shift. So ⌘ + D does not mean hold shift. ⌘ + Shift + D does of course.

Tabs and Windows

Function	Shortcut
New Tab	`⌘` + `T`
Close Tab or Window	`⌘` + `W` (same as many mac apps)
Go to Tab	`⌘` + `Number Key` (ie: `⌘2` is 2nd tab)
Go to Split Pane by Direction	`⌘` + `Option` + `Arrow Key`

Contributing

When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Pull Request Process

Ensure any install or build dependencies are removed before the end of the layer when doing a

Integrate Gem/Engine and main Rails app

Overview

Paths
Routes
Add functionality to controller
Improving (Extending or overriding) Engine functionality
Helpers
Assets

Requirements

no upfront installation/agents on remote/slave machines - ssh should be enough
application components should use third-party software, e.g. HDFS, Spark's cluster, deployed separately
configuration templating
environment requires/asserts, i.e. we need a JVM in a given version before doing deployment
deployment process run from Jenkins

	#include <iostream>
	#include <string>
	#include <cmath>
	using namespace std;


	int main() {
	int userDay = 0;
	int userYear = 0;
	int userMonth = 0;

	#include <iostream>
	#include <string>
	#include <cmath>
	using namespace std;


	int main() {
	int userDay = 0;
	int userYear = 0;
	int userMonth = 0;

	#!/bin/bash

	# Check if script is being run by root
	if [[ $EUID -ne 0 ]]; then
	printf "This script must be run as root!\n"
	exit 1
	fi

	DIVIDER="\n***************************************\n\n"

	# This is a very basic benchmark of Mustache (1.0.2) vs.
	# Liquid (3.0.6) rendering. It does two sets of benchmarks: One with
	# "precompiled" templates (i.e. the Mustache::Template or
	# Liquid::Template object is kept between runs) and one without (a new
	# Template object is instantiated for each run). This benchmark tests
	# a basic loop; no other features e.g. partials or conditionals
	# are tested.

	require "benchmark/ips"
	require "mustache"