luismts

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

mr4torr

# Entrar no servidor e fora da pasta do projeto

$ cd /home/webmaster/
$ mkdir repository && cd repository
$ mkdir site.git && cd site.git
$ git init --bare

$ cd hooks
$ vim post-receive

holmberd

Adjusting child processes for PHP-FPM (Nginx)

When setting these options consider the following:

• How long is your average request?
• What is the maximum number of simultaneous visitors the site(s) get?
• How much memory on average does each child process consume?

Determine if the max_children limit has been reached.

• sudo grep max_children /var/log/php?.?-fpm.log.1 /var/log/php?.?-fpm.log

lucaslz

<?php

namespace Mocks;

use Doctrine\DBAL\Driver\Statement;

/**
 * Doctrine DBAL Statement implementing \Iterator.
 *
 * This class has been created because of a bug in PHPUnit Mock Objects.

lucaslz

#!/bin/sh

# Sublime Text 3 install with Package Control (last update: 25 September 2016)
#
# No need to download this script, just run it on your terminal:
#
#  $  curl -L git.io/sublimetext | sh


# Detect the architecture

mreschke

# This config will host your main [Laravel] GUI application at /, and any additional [Lumen] webservices at /api/v1 and /api/v2...
# This also works perfectly for all static file content in all projects
# This is full of debug comments so you can see how to print debug output to browser! Took me hours to nail this perfect config.

# Example:
# http://example.com - Main Laravel site as usual
# http://example.com/about - Main Laravel site about page as usual
# http://example.com/robots.txt - Main Laravel site static content as usual
# http://example.com/api/v1 - Lumen v1 api default / route
# http://example.com/api/v1/ - Lumen v1 api default / route

spalladino

# Backup
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

# Restore
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE

chrisblackwell

#!/bin/sh
WEBROOT=/srv/www/apps.legendboats.com
GIT_WORK_TREE=$WEBROOT git checkout -f

cd $WEBROOT

# Check if a composer.json file is present
if [ -f composer.json ]; then
    # Install or update packages specified in the lock file
    composer install

vool

#!/bin/bash

echo "********************"
echo "Post receive hook: Updating website"
echo "********************"

#set the git repo dir
GIT_REPO_DIR=~/git/<repo>.git
echo "The git repo dir is $GIT_REPO_DIR"

plentz

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048