Let's say you want to host domains first.com
and second.com
.
Create folders for their files:
const https = require('https') | |
exports.handler = async (event) => { | |
const sns = event.Records[0].Sns.Message | |
let color = '' | |
let message = '' | |
if (sns.includes('build status is FAILED')) { | |
color = '#E52E59' | |
message = 'Release to My Company **production** failed.' | |
} else if (sns.includes('build status is SUCCEED')) { |
<?php | |
namespace Acme\BlogBanner; | |
use System\Classes\PluginBase; | |
use Event; | |
/** | |
* Class Plugin | |
* |
# Setup symlinks in local development copy of Winter to the local development copy of Winter.Workshop | |
ln -s ~/LocalRepositories/WinterCMS/Themes/Winter/Workshop ~/LocalRepositories/WinterCMS/Core/winter/themes/workshop | |
# Setup external symlink (for mac, outside of vagrant) to the local development copies of my plugins | |
ln -s ~/Repositories/WinterCMS/Themes/Winter/Workshop ~/Repositories/WinterCMS/Core/winter/themes/workshop-src | |
# Setup symlinks in local development copy of Winter to the local development copies of my plugins | |
ln -s ~/LocalRepositories/WinterCMS/Plugins ~/LocalRepositories/WinterCMS/Core/winter/plugins | |
# Setup external symlink (for mac, outside of vagrant) to the local development copies of my plugins |
{ | |
"vars": {}, | |
"css": [ | |
"grid.less", | |
"responsive-utilities.less" | |
], | |
"js": [] | |
} |
#make a folder for your app | |
mkdir /var/www | |
mkdir /var/www/laravel | |
#nginx config for laravel app | |
server { | |
listen 80 default_server; | |
root /var/www/laravel/public/; | |
index index.php index.html index.htm; |
<?php | |
$loop = new WP_Query( array( | |
'post_type' => 'Property', | |
'posts_per_page' => -1 | |
) | |
); | |
?> | |
<?php while ( $loop->have_posts() ) : $loop->the_post(); ?> |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
<?php | |
/** | |
* A helper file for Laravel 5, to provide autocomplete information to your IDE | |
* Generated for Laravel 5.5.13 on 2017-09-28. | |
* | |
* @author Barry vd. Heuvel <[email protected]> | |
* @see https://github.com/barryvdh/laravel-ide-helper | |
*/ | |
namespace { | |
exit("This file should not be included, only analyzed by your IDE"); |
{ | |
"AL": "Alabama", | |
"AK": "Alaska", | |
"AS": "American Samoa", | |
"AZ": "Arizona", | |
"AR": "Arkansas", | |
"CA": "California", | |
"CO": "Colorado", | |
"CT": "Connecticut", | |
"DE": "Delaware", |