kuya-joe

<!--
   Copyright 2017 Vinzenz Feenstra, Red Hat, Inc.

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software

kuya-joe

# Change to the project directory
cd $FORGE_SITE_PATH

# Turn on maintenance mode
php artisan down || true

# Pull the latest changes from the git repository
# git reset --hard
# git clean -df
git pull origin $FORGE_SITE_BRANCH

kuya-joe

https://sourcelevel.io/blog/7-git-best-practices-to-start-using-in-your-next-commit

6. Rebase your working branch frequently. It’s crucial always to keep your branch rebase with the latest code. Writing new code upon obsolete one is useless. It is as meaningless as fixing a bug that may already be fixed. You should rebase your working branch frequently to prevent bugs, rework, and the tedious job of resolving conflicts with the upstream branch. You can do it easily by running these commands:

git checkout 

kuya-joe

Using git you can just diff between branches. So you have the diff between the destination branch from your feature branch and you just want to "put your code changes" together Accordin to https://stackoverflow.com/a/22390257/1345527

To create the patch : git diff dev > master.patch To apply it : patch < master.patch

In theory, if diff and git diff are similar you could do the following to put your code changes on top of a target branch (usually when doing a MR to master).

1. git checkout master (or other target branch)
2. git diff (your-source-branch ) > final-destination.patch

kuya-joe

<?php
/* from StackOverflow: https://stackoverflow.com/a/52662522/1345527 */
function fetch(string $method, string $url, string $body, array $headers = []) {
    $context = stream_context_create([
        "http" => [
            // http://docs.php.net/manual/en/context.http.php
            "method"        => $method,
            "header"        => implode("\r\n", $headers),
            "content"       => $body,
            "ignore_errors" => true,

kuya-joe

alias v='fd --type f --hidden --exclude .git | fzf-tmux -p --reverse | xargs nvim'

kuya-joe

<?php

namespace App\Providers;

use Illuminate\Support\Collection;
use Illuminate\Pagination\LengthAwarePaginator;

class AppServiceProvider extends ServiceProvider
{
    public function boot()

kuya-joe

<?php

namespace App\Http\Utilities;

use Illuminate\Http\Request;
use Illuminate\Pagination\LengthAwarePaginator;
use Illuminate\Support\Collection;

class ArrayPaginator
{

kuya-joe

This is a simple way of importing MySQL database in Docker.

1. In you Dockerfile you must have a shared folder. Shared folder is a directory in your host machine that is mounted to Docker instance.

2. Put the exported sql file in the shared folder.

3. Login to your Docker instance via docker exec -it DOCKER_CONTAINER_ID bin/bash.

4. Login to MySQL via mysql -u USERNAME -p. Use -P/--port to specify the port if your exposed port of your docker mysql service is different.

kuya-joe

# vim style tmux config

# use C-a, since it's on the home row and easier to hit than C-b
set-option -g prefix C-a
unbind-key C-a
bind-key C-a send-prefix
set -g base-index 1

# Easy config reload
bind-key R source-file ~/.tmux.conf \; display-message "tmux.conf reloaded."