Permalink
Browse files

it's not good name though, change the custom recipe name

  • Loading branch information...
banyan committed Mar 18, 2013
1 parent aa2b613 commit 90e4491f49e7802bc52902118e3a065416238bb9
@@ -1,7 +1,7 @@
name "rails-development"
description "setup for ruby on rails core development"
run_list(
"recipe[base]",
"recipe[preinstall]",
"recipe[git]",
"recipe[sqlite]",
"recipe[mysql::client]",
@@ -14,4 +14,5 @@
"recipe[rbenv::system]",
"recipe[rbenv::vagrant]",
"recipe[database]",
"recipe[postinstall]",
)
@@ -0,0 +1,12 @@
# CHANGELOG for postinstall

This file is used to list changes made in each version of postinstall.

## 0.1.0:

* Initial release of postinstall

- - -
Check the [Markdown Syntax Guide](http://daringfireball.net/projects/markdown/syntax) for help with Markdown.

The [Github Flavored Markdown page](http://github.github.com/github-flavored-markdown/) describes the differences between markdown on github and standard markdown.
@@ -0,0 +1,68 @@
postinstall Cookbook
====================
TODO: Enter the cookbook description here.

e.g.
This cookbook makes your favorite breakfast sandwhich.

Requirements
------------
TODO: List your cookbook requirements. Be sure to include any requirements this cookbook has on platforms, libraries, other cookbooks, packages, operating systems, etc.

e.g.
#### packages
- `toaster` - postinstall needs toaster to brown your bagel.

Attributes
----------
TODO: List you cookbook attributes here.

e.g.
#### postinstall::default
<table>
<tr>
<th>Key</th>
<th>Type</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td><tt>['postinstall']['bacon']</tt></td>
<td>Boolean</td>
<td>whether to include bacon</td>
<td><tt>true</tt></td>
</tr>
</table>

Usage
-----
#### postinstall::default
TODO: Write usage instructions for each cookbook.

e.g.
Just include `postinstall` in your node's `run_list`:

```json
{
"name":"my_node",
"run_list": [
"recipe[postinstall]"
]
}
```

Contributing
------------
TODO: (optional) If this is a public cookbook, detail the process for contributing. If this is a private cookbook, remove this section.

e.g.
1. Fork the repository on Github
2. Create a named feature branch (like `add_component_x`)
3. Write you change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github

License and Authors
-------------------
Authors: TODO: List authors
@@ -0,0 +1,7 @@
name 'postinstall'
maintainer 'YOUR_COMPANY_NAME'
maintainer_email 'YOUR_EMAIL'
license 'All rights reserved'
description 'Installs/Configures postinstall'
long_description IO.read(File.join(File.dirname(__FILE__), 'README.md'))
version '0.1.0'
@@ -0,0 +1,26 @@
#
# Cookbook Name:: postinstall
# Recipe:: default
#
# Copyright 2013, YOUR_COMPANY_NAME
#
# All rights reserved - Do Not Redistribute
#

group "rbenv" do
action :create
members "vagrant"
gid 1100
append true
end

bash "chgrp and chmod" do
user "root"
cwd "/usr/local"
code <<-EOH
chgrp -R rbenv rbenv
chmod -R g+rwxX rbenv
EOH
not_if { ::File::stat("/usr/local/rbenv").gid == 1100 }
end

0 comments on commit 90e4491

Please sign in to comment.