If you're trying to load a private repository with Composer/Laravel, we'll need to generate a GitHub Personal Access Token (similar to OAuth token) to access the repository during a composer install without entering credentials.
If you have used other Github packages from
{my-org}before, you may be able to skip this step.
Click Generate new token.
| stages: | |
| - build | |
| test: | |
| stage: build | |
| environment: | |
| name: staging | |
| script: | |
| - git submodule update --init --remote #if you don't have submodules in your project you can remove this line | |
| - SET BDS=C:\\Program Files (x86)\\Embarcadero\\Studio\\15.0 |
This gist assumes you are migrating an existing site for www.example.com — ideally WordPress — to a new server — ideally Ubuntu Server 16.04 LTS — and wish to enable HTTP/2 (backwards compatibile with HTTP/1.1) with always-on HTTPS, caching, compression, and more. Although these instructions are geared towards WordPress, they should be trivially extensible to other PHP frameworks, other FastCGI backends, and even non-FastCGI backends (using proxy in lieu of fastcgi in the terminal Caddyfile stanza).
Quickstart: Use your own naked and canonical domain names instead of example.com and www.example.com and customize the Caddyfile and VCL provided in this gist to your preferences!
These instructions target Varnish Cache 4.1, PHP-FPM 7.0, and Caddy 0.10. (I'm using MariaDB 10.1 as well, but that's not relevant to this guide.)
| <?php | |
| // script to convert local git commit log history into JSON format | |
| // usage: cd git-repository && php git-log-to-json.php > commits.json | |
| // script might take a while to execute | |
| $tags = [ ]; | |
| $lines = shell_exec('git show-ref --tags'); | |
| foreach (array_filter(explode("\n", $lines)) as $line) { | |
| list($commit, $ref) = explode(" ", $line, 2); |
| <?php | |
| // find your api key on the bottom of page @ https://webapp.imgix.com | |
| define('IMGIX_API_KEY', ''); | |
| // pass the url you want to purge | |
| function imgix_purge($url) { | |
| $headers = array( | |
| 'Content-Type:application/json', | |
| 'Authorization: Basic '. base64_encode(IMGIX_API_KEY.':') |
| <?php | |
| function import_csv_to_sqlite(&$pdo, $csv_path, $options = array()) | |
| { | |
| extract($options); | |
| if (($csv_handle = fopen($csv_path, "r")) === FALSE) | |
| throw new Exception('Cannot open CSV file'); | |
| if(!$delimiter) | |
| $delimiter = ','; |
There's no shortage of good resources for learning laravel. So instead of the usual introductory tutorial were just gonna learn Laravel by building a project from scratch and that's gonna be a User Management System.
I don't know if my definition of a User Management System is correct but here's my idea of what's it's capable of doing:
| // | |
| // BPUUID.h | |
| // Skates | |
| // | |
| // Created by Jon Olson on 2/3/10. | |
| // Copyright 2010 Ballistic Pigeon, LLC. All rights reserved. | |
| // | |
| #import <Foundation/Foundation.h> |
