| <?php | |
| namespace App\Providers; | |
| use Illuminate\Database\Query\Builder; | |
| use Illuminate\Support\Facades\Request; | |
| use Illuminate\Support\ServiceProvider; | |
| class EloquentSortableServiceProvider extends ServiceProvider | |
| { |
| image: ubuntu:zesty | |
| services: | |
| - mariadb | |
| variables: | |
| MYSQL_DATABASE: smsclub_old | |
| MYSQL_ROOT_PASSWORD: root | |
| before_script: |
This is a 2-part technique to share named routes between Laravel and Javascript. It uses a custom artisan command to export your named routes to JSON, and a Javascript route() helper to lookup the route and fill in any parameters. Written for Laravel 5.3; not tested in 5.4.
Copy RouteJson.php into your app as app/Console/Commands/RouteJson.php
| <?php | |
| /** | |
| Thanks stackoverflow | |
| */ | |
| function getOS($user_agent) { | |
| $os_array = array( | |
| '/windows nt 10/i' => 'Windows 10', | |
| '/windows nt 6.3/i' => 'Windows 8.1', | |
| '/windows nt 6.2/i' => 'Windows 8', | |
| '/windows nt 6.1/i' => 'Windows 7', |
| [ | |
| { | |
| "name": "New Years Day", | |
| "date": "01/01/2017", | |
| "states": [ | |
| "Kuala Lumpur", | |
| "Labuan", | |
| "Malacca", | |
| "Negeri Sembilan", | |
| "Pahang", |
| [ | |
| { | |
| "ID": "1", | |
| "Bank or Institution": "AFFIN BANK BERHAD", | |
| "City": "KUALA LUMPUR", | |
| "Branch": "", | |
| "Swift Code": "PHBMMYKL" | |
| }, | |
| { | |
| "ID": "2", |
| 1. Installing Informix Client SDK for Linux x86_64 | |
| 1.1 Download Informix Client SDK 3.70 for Linux x86_64 from IBM website, https://www-01.ibm.com/marketing/iwm/tnd/search.jsp?rs=ifxdl | |
| 1.2 Extract the file, `cd /opt/informix; tar -xvf clientsdk.3.70.FC8DE.LINUX.tar` | |
| 1.3 Start installation, `./installclientsdk`, install all | |
| 2. Installing PDO Informix |
| Model:: | |
| /*Select*/ | |
| select('col1','col2') | |
| ->select(array('col1','col2')) | |
| ->select(DB::raw('businesses.*, COUNT(reviews.id) as no_of_ratings, IFNULL(sum(reviews.score),0) as rating')) | |
| ->addSelect('col3','col4') | |
| ->distinct() // distinct select | |
| /*From*/ |
| <?php | |
| return Symfony\CS\Config\Config::create() | |
| ->level(Symfony\CS\FixerInterface::SYMFONY_LEVEL) | |
| ->fixers([ | |
| 'short_array_syntax', | |
| 'ordered_use', | |
| ]) | |
| ; |
Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.
“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”
Matt Bridges' answer in full:
The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing
