abhishekkhaware

# Laravel Artisan Commands Shortcut 

function art($arg1,$arg2,$arg3,$arg4,$arg5) { php artisan $arg1 $arg2 $arg3 $arg4 $arg5}

Set-Alias a art

#### Use as by default Alias  #####

#  ge:r => generate:resource
#  ge:c => generate:controller

kevin-smets

Default

Powerlevel10k

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

lesstif

#!/bin/bash
#
# tomcat
#
# chkconfig: 345 96 30
# description:  Start up the Tomcat servlet engine.
#
# processname: java
# pidfile: /var/run/tomcat.pid
#

aczietlow

Webdriver PHP API workthough

• Open a browser

  # start an instance of firefox with selenium-webdriver
  
  $browser_type = 'firefox'
  $host = 'http://localhost:4444/wd/hub'
  

$capabilities = array(\WebDriverCapabilityType::BROWSER_NAME => $browser_type);

lesstif

#!/bin/sh

killproc() {
    local servicename=$1
    local user=$2
    local signal="TERM"

    if [ "$#" = 0 ] ; then
        echo $"Usage: killproc {servicename} {user} {signal}"
        return 1

jrmadsen67

Quick tip for handling CSRF Token Expiration - common issue is when you use csrf protection is that if 
a form sits there for a while (like a login form, but any the same) the csrf token in the form will 
expire & throw a strange error.

Handling it is simple, and is a good lesson for dealing with other types of errors in a custom manner.

In Middleware you will see a file VerifyCsrfToken.php and be tempted to handle things there. DON'T! 
Instead, look at your app/Exceptions/Handler.php, at the render($request, Exception $e) function.

All of your exceptions go through here, unless you have excluded them in the $dontReport array at the 

fevangelou

# === Optimized my.cnf configuration for MySQL/MariaDB (on Ubuntu, CentOS, Almalinux etc. servers) ===
#
# by Fotis Evangelou, developer of Engintron (engintron.com)
#
# ~ Updated December 2021 ~
#
#
# The settings provided below are a starting point for a 8-16 GB RAM server with 4-8 CPU cores.
# If you have different resources available you should adjust accordingly to save CPU, RAM & disk I/O usage.
#

Nihisil

...

action_with_slack_notification = %(banaction)s[name=%(__name__)s, port="%(port)$
                                 slack[name=%(__name__)s]
                                 
action = %(action_with_slack_notification)s

...

lesstif

#!/usr/bin/env bash

## Installation
## curl -o /usr/local/bin/serve-php.sh https://gist.githubusercontent.com/lesstif/82c107282241c7a52ad9/raw 
## chmod +x /usr/local/bin/serve-php.sh

SA="/etc/nginx/sites-available/"
SE="/etc/nginx/sites-enabled/"

test=0