vamuigua

Setup a custom pre-commit script for a Laravel Project

Here's how you can set it up:

1. First, make sure your pre-commit file is in the correct location. It should be in the .git/hooks/ directory of your project. If it's not there already, move it:

mv pre-commit .git/hooks/pre-commit

vamuigua

# Based on this answer: https://stackoverflow.com/a/61859561/1956278

# Backup old data
Rename-Item -Path "./data" -NewName "./data_old"

# Create new data directory
Copy-Item -Path "./backup" -Destination "./data" -Recurse
Remove-Item "./data/test" -Recurse
$dbPaths = Get-ChildItem -Path "./data_old" -Exclude ('mysql', 'performance_schema', 'phpmyadmin') -Recurse -Directory
Copy-Item -Path $dbPaths.FullName -Destination "./data" -Recurse

vamuigua

public function assertHasPagination($response, $values = [])
{
    $response->assertJsonStructure([
        'links' => [
            'first',
            'last',
            'prev',
            'next',
 ]

vamuigua

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.

vamuigua

To install php7.4 on Ubuntu run the following commands in order:

sudo apt-get update

sudo apt install -y software-properties-common ca-certificates lsb-release apt-transport-https

vamuigua

Method 1:

mysql -u <username> -p <database_name> < import.sql

Method 2:

1. Open mysql on cmd

vamuigua

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

vamuigua

<?php

namespace App\Providers;

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

class AppServiceProvider extends ServiceProvider
{
    public function boot()

vamuigua

name: Laravel Vapor CD
on:
  release:
    types: [ published, deleted ]
    branches:
      - master
jobs:
  deploy_release:
    runs-on: ubuntu-20.04

vamuigua

#!/bin/sh
set -e

vendor/bin/phpunit
npm run prod

git add .
(git commit -m "Build frontend assets for deployment to production") || true
(git push) || true