kkbt

#!/bin/zsh
set -e  # exit on error

# zsh running an a Mac


new_server_dir='server_mwe'

# Create fresh Laravel installation
rm -rf $new_server_dir

lfbn

<?php

namespace App\Services\Dto;

abstract class AbstractDto
{
    /**
     * AbstractRequestDto constructor.
     * @param array $data
     */

earth774

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use Laravel\Lumen\Routing\Controller as BaseController;

class Controller extends BaseController
{
    public function uploadImage(Request $request)

Agoreddah

// load variables
require('dotenv').config();

// load dependencies
const crypto = require('crypto');

'use strict';

const APP_KEY = process.env.APP_KEY;

tim545

Structuring a large jQuery application

This document assumes you are building a traditional backend-heavy application as opposed to a frontend-heavy appliction which would typically use a framework like Angular or React. The use of these frameworks make this document irrelevant, however also require a change to your application architecture and a much larger overhead in order to get content onto a page, so as a simple way to build interactive web content a simple jquery based js stack will do fine.

Directory structure

It's important you use a directory structure which is impartial to your development environment, chosen server language (Python v. Java v. C# ...), and styling framwork (Twitter Bootstrap etc). This layer of separation means you can swap out the styles or the backend with minimal changes to the Js, simple and maintainable.

Here's an example from the project root:

RuGa

/**
* Mass (bulk) insert or update on duplicate for Laravel 4/5
* 
* insertOrUpdate([
*   ['id'=>1,'value'=>10],
*   ['id'=>2,'value'=>60]
* ]);
* 
*
* @param array $rows

IsaacVanName

/*
new MyClass->my_method() isn't possible. However, there are a couple of solutions, of which the best seems to be the most unlikely as well.

****
Note: Make sure you read/skim to the end, even if you figure out the first solution quickly 
(which you should). The second solution has a bit of brief research to go along with it! :-)
****

At times, it can be useful to have a class that maintains state long enough to complete a 
cycle, but doesn't get stored in memory. No extra baggage needed, right?