cap-laravel 0.0.5 → 0.0.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +10 -8
- data/lib/cap/laravel/defaults.rb +1 -0
- data/lib/cap/laravel/version.rb +1 -1
- data/lib/cap/tasks/assets.rake +2 -2
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 8da3eddd4099be9c7fdedb2666c1700006385eff
|
4
|
+
data.tar.gz: f60651f824f36b29b74b1dcc40f51fc34b454f7a
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: b72b06aa766566179994049ac9cf93f9189d21cf46266a72d11c8dd0aa48d5dedaf957df7b8c17ed4855ca8d1729dde355404c44a96a29b4e8b84334c030bfed
|
7
|
+
data.tar.gz: 50674e569cec9b25751ec22acd692a1986346b17a716a6d435c70c8cbee750cb2416249dd28d2db12b169188658d4728b42dfbf2e10bc3d93ecaf5acbaa90f17
|
data/README.md
CHANGED
@@ -31,6 +31,16 @@ Bask in the glory of Capistrano.
|
|
31
31
|
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:
|
32
32
|
|
33
33
|
set :run_migrations, false
|
34
|
+
|
35
|
+
### Assets
|
36
|
+
|
37
|
+
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:
|
38
|
+
|
39
|
+
set :run_assets, false
|
40
|
+
|
41
|
+
This means even if a package.json or Gruntfile.js exist on the server, they will not be executed by their package manager.
|
42
|
+
|
43
|
+
You will probably want to set this if you are comitting compiled stylesheets to your repo, or uploading them in a compiled state.
|
34
44
|
|
35
45
|
### Grunt
|
36
46
|
|
@@ -39,11 +49,3 @@ By default, the `grunt` task will be run when compiling CSS, etc. To alter the c
|
|
39
49
|
set :grunt_cmd, "grunt task here"
|
40
50
|
|
41
51
|
This could be something like `grunt:prod`, or whatever you want it to be if it doesn't follow the normal practice.
|
42
|
-
|
43
|
-
## Contributing
|
44
|
-
|
45
|
-
1. Fork it ( https://github.com/[my-github-username]/cap-laravel/fork )
|
46
|
-
2. Create your feature branch (`git checkout -b my-new-feature`)
|
47
|
-
3. Commit your changes (`git commit -am 'Add some feature'`)
|
48
|
-
4. Push to the branch (`git push origin my-new-feature`)
|
49
|
-
5. Create a new Pull Request
|
data/lib/cap/laravel/defaults.rb
CHANGED
data/lib/cap/laravel/version.rb
CHANGED
data/lib/cap/tasks/assets.rake
CHANGED
@@ -4,7 +4,7 @@ namespace :assets do
|
|
4
4
|
task :npm do
|
5
5
|
on roles(:app) do
|
6
6
|
within release_path do
|
7
|
-
if test("[ -e #{release_path}/package.json ]")
|
7
|
+
if fetch(:run_assets) && test("[ -e #{release_path}/package.json ]")
|
8
8
|
execute :npm, :install, "--quiet"
|
9
9
|
end
|
10
10
|
end
|
@@ -15,7 +15,7 @@ namespace :assets do
|
|
15
15
|
task :grunt do
|
16
16
|
on roles(:app) do
|
17
17
|
within release_path do
|
18
|
-
if test("[ -e #{release_path}/Gruntfile.js ]")
|
18
|
+
if fetch(:run_assets) && test("[ -e #{release_path}/Gruntfile.js ]")
|
19
19
|
execute fetch(:grunt_cmd)
|
20
20
|
end
|
21
21
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: cap-laravel
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.6
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Gareth Bishop
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2014-04-
|
11
|
+
date: 2014-04-24 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: capistrano
|