Sha256: 27f0441bff3be0b31ab614ab3e0d0a5623e305ce06be0cd80c1f6794a427c543

Contents?: true

Size: 1.63 KB

Versions: 2

Compression:

Stored size: 1.63 KB

Contents

# Cap::Laravel

A collection of tasks for deploying a Laravel app via Capistrano.

## Installation

Add this line to your application's Gemfile:

    gem 'cap-laravel'

And then execute:

    $ bundle

Or install it yourself as:

    $ gem install cap-laravel

## Usage

Add it to your Capfile:

	require 'cap/laravel'

Bask in the glory of Capistrano.

## Seeding

If you want to seed your database, you have a few options.

The basic task is `cap env artisan:db:seed` which will runn your bog standard seeding process.

If you want to seed a specific class do the following:

	$ cap env artisan:db:seed[SeedClassHere]

`env` is a placeholder for the environment you are deploying to, so it will likely be `staging` or `production`.

## Settings

### Migrations

If you are creating an app that doesn't have any migrations, e.g. an API client, you can ignore migrations by setting the following in your `deploy.rb` file:

	set :run_migrations, false
  
### Assets

If for some reason you do not want to run NPM & Grunt, e.g. you're on a Unilever server that won't resolve NPM requests, you can prevent them:

	set :run_assets, false

This means even if a package.json or Gruntfile.js exist on the server, they will not be executed by their package manager.

You will probably want to set this if you are comitting compiled stylesheets to your repo, or uploading them in a compiled state.

### Grunt

By default, the `grunt` task will be run when compiling CSS, etc. To alter the command that is run set the following:

	set :grunt_cmd, "grunt task here"

This could be something like `grunt:prod`, or whatever you want it to be if it doesn't follow the normal practice.

Version data entries

2 entries across 2 versions & 1 rubygems

Version Path
cap-laravel-0.0.8 README.md
cap-laravel-0.0.7 README.md