Team Role Middleware For Laravel Spark
Makes it simple to use Spark's role feature on routes
Route::group(['middleware'=>'role:owner'], function(){
// owners only
});
Route::group(['middleware'=>'role:member'], function(){Makes it simple to use Spark's role feature on routes
Route::group(['middleware'=>'role:owner'], function(){
// owners only
});
Route::group(['middleware'=>'role:member'], function(){| # Set composer folder for this command and update | |
| commands: | |
| 01updateComposer: | |
| command: export COMPOSER_HOME=/root && /usr/bin/composer.phar self-update | |
| option_settings: | |
| # Add environment variable to set composer home folder | |
| - namespace: aws:elasticbeanstalk:application:environment | |
| option_name: COMPOSER_HOME | |
| value: /root |
| # The following script will deploy a Laravel 5 applicaion on AWS Elastic Beanstalk. | |
| # Add to .ebextensions at the root of your application and name your commands file (e.g., commands.config) | |
| # -------------------------------- Commands ------------------------------------ | |
| # Use "commands" key to execute commands on the EC2 instance. The commands are | |
| # processed in alphabetical order by name, and they run before the application | |
| # and web server are set up and the application version file is extracted. | |
| # ------------------------------------------------------------------------------ | |
| commands: | |
| 01updateComposer: |
| # Let's Encrypt | |
| # Install Process | |
| cd ~ | |
| git clone https://github.com/letsencrypt/letsencrypt | |
| cd letsencrypt | |
| sudo ./letsencrypt-auto certonly --standalone --agree-tos --redirect --duplicate --text --email [email protected] -d EXAMPLE.COM -d WWW.EXAMPLE.COM | |
| # Nginx Configuration | |
| # https://github.com/h5bp/server-configs-nginx/blob/master/h5bp/directive-only/ssl.conf | |
| # Path to Certificates | |
| # /etc/letsencrypt/live/EXAMPLE.COM/privkey.pem |
| <?php | |
| namespace App\Http\Middleware; | |
| use Closure; | |
| use Illuminate\Auth\Access\AuthorizationException; | |
| class VerifyTenants | |
| { | |
| /** |
| # Installation: | |
| # Copy to ~/.config/fish/completions/magento.fish | |
| # Open new or restart existing shell session | |
| # Commands based on Magento 2.0.0-rc and the command | |
| # bin/magento --raw --no-ansi list | |
| # It is a static list since you probably do not have the magento shell script | |
| # in your path. | |
| complete -f -c magento -a --help; | |
| complete -f -c magento -a -h; |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <ruleset name="Laravel and similar phpmd ruleset" | |
| xmlns="http://pmd.sf.net/ruleset/1.0.0" | |
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
| xsi:schemaLocation="http://pmd.sf.net/ruleset/1.0.0 http://pmd.sf.net/ruleset_xml_schema.xsd" | |
| xsi:noNamespaceSchemaLocation="http://pmd.sf.net/ruleset_xml_schema.xsd"> | |
| <description> | |
| Inspired by https://github.com/phpmd/phpmd/issues/137 | |
| using http://phpmd.org/documentation/creating-a-ruleset.html | |
| </description> |
| # This is a template .gitignore file for git-managed WordPress projects. | |
| # | |
| # Fact: you don't want WordPress core files, or your server-specific | |
| # configuration files etc., in your project's repository. You just don't. | |
| # | |
| # Solution: stick this file up your repository root (which it assumes is | |
| # also the WordPress root directory) and add exceptions for any plugins, | |
| # themes, and other directories that should be under version control. | |
| # | |
| # See the comments below for more info on how to add exceptions for your |
| alias gl="git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit" |