Cahyadi Triyansyah SunDi3yansyah

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

Rails with PostgreSQL

This gist was created based on the following guide: upgrading to postgresql 11 on centos 7

Create a backup:

sudo -Hiu postgres pg_dumpall > mybackup.sql

Install PostgreSQL 11:

Serving Static Content

location ~ \.(jpg|jpeg|gif|png|css|js|ico|xml|txt|gz)$ {
  expires 30d;
  log_not_found off;
  access_log off;
}

Set BUNDLE_PATH / BUNDLE_SYSTEM on the system, not on the project

bundle config set system 'true'

Cross-origin resource sharing (CORS) for AWS S3

[
    {
        "AllowedHeaders": [
            "*"
        ],
        "AllowedMethods": [
 "GET",

Rails naming conventions

General Ruby conventions

Class names are CamelCase.

Methods and variables are snake_case.

Methods with a ? suffix will return a boolean.

1C
1.PAK
2.PAK
20-GATE
3APL
473L Query
51-FORTH
4D
Kez Barnes Basic

	server {
	listen %ip%:%web_port%;
	server_name %domain_idn% %alias_idn%;
	location / {
	rewrite ^(.*) https://%domain_idn%$1 permanent;
	}
	}

	jQuery(document).on 'turbolinks:load', ->
	u = $("#current_user").val()
	window.current_user = JSON.parse(u)
	messages = $('#messages')
	user_is_typing = $('#user_is_typing')

	App.global_chat = App.cable.subscriptions.create {
	channel: "ChatRoomsChannel"
	chat_room_id: messages.data('chat-room-id')
	},