Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in
Toggle navigation
H
heroku-buildpack-nodejs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
JIRA
JIRA
Merge Requests
0
Merge Requests
0
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Python-Dev
heroku-buildpack-nodejs
Commits
68a8047d
Commit
68a8047d
authored
Mar 24, 2013
by
zeke
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add CONTRIBUTING.md
parent
06f629ce
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
81 additions
and
4 deletions
+81
-4
CONTRIBUTING.md
CONTRIBUTING.md
+75
-0
README.md
README.md
+6
-4
No files found.
CONTRIBUTING.md
0 → 100644
View file @
68a8047d
## Testing buildpack changes using Anvil
[
Anvil
](
https://github.com/ddollar/anvil
)
is a generic build server for Heroku.
```
gem install anvil-cli
```
The
[
heroku-anvil CLI plugin
](
https://github.com/ddollar/heroku-anvil
)
is a wrapper for anvil.
```
heroku plugins:install https://github.com/ddollar/heroku-anvil
```
The
[
ddollar/test buildpack
](
https://github.com/ddollar/buildpack-test
)
is for testing things: it runs
`bin/test`
on your app.
```
heroku build -b ddollar/test # -b can also point to a local directory
```
## Compiling new versions of node and npm using Vulcan
Install
[
vulcan
](
https://github.com/heroku/vulcan
)
and create your own build server. Use any
app name you want and vulcan will remember it in a
`~/.vulcan`
config file.
```
gem install vulcan
vulcan create builder-bob
```
Store your S3 credentials in
`~/.aws/`
```
mkdir -p ~/.aws
echo 'YOUR_AWS_KEY' > ~/.aws/key-nodejs.access
echo 'YOUR_AWS_SECRET' > ~/.aws/key-nodejs.secret
```
Add a credentials exporter to your
`.bash_profile`
or
`.bashrc`
```
setup_nodejs_env () {
export AWS_ID=$(cat ~/.aws/key-nodejs.access)
export AWS_SECRET=$(cat ~/.aws/key-nodejs.secret)
export S3_BUCKET="heroku-buildpack-nodejs"
}
```
Build:
```
setup_nodejs_env
support/package_nodejs <node-version>
support/package_npm <npm-version>
```
## Publishing buildpack updates
```
heroku plugins:install https://github.com/heroku/heroku-buildpacks
cd heroku-buildpack-nodejs
git checkout master
heroku buildpacks:publish heroku/nodejs
```
-
Email
[
dos@heroku.com
](
mailto:dos@heroku.com
)
if changes are significant.
-
Add a
[
changelog item
](
https://devcenter.heroku.com/admin/changelog_items/new
)
.
-
Update
[
Node Devcenter articles
](
https://devcenter.heroku.com/admin/articles/owned
)
as necessary.
## Keeping up with the Nodeses
-
Run
`npm info npm version`
to find out the latest available version of npm.
-
Follow
[
@nodejs
](
https://twitter.com/nodejs
)
and
[
@npmjs
](
https://twitter.com/npmjs
)
on Twitter.
\ No newline at end of file
README.md
View file @
68a8047d
...
@@ -12,7 +12,7 @@ Example usage:
...
@@ -12,7 +12,7 @@ Example usage:
$ ls
$ ls
Procfile package.json web.js
Procfile package.json web.js
$ heroku create --
stack cedar --
buildpack http://github.com/heroku/heroku-buildpack-nodejs.git
$ heroku create --buildpack http://github.com/heroku/heroku-buildpack-nodejs.git
$ git push heroku master
$ git push heroku master
...
...
...
@@ -48,8 +48,8 @@ To list the available versions of Node.js and npm, see these manifests:
...
@@ -48,8 +48,8 @@ To list the available versions of Node.js and npm, see these manifests:
http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.nodejs
http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.nodejs
http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.npm
http://heroku-buildpack-nodejs.s3.amazonaws.com/manifest.npm
Hack
ing
Contribut
ing
-------
-------
-----
To use this buildpack, fork it on Github. Push up changes to your fork, then create a test app with
`--buildpack <your-github-url>`
and push to it.
To use this buildpack, fork it on Github. Push up changes to your fork, then create a test app with
`--buildpack <your-github-url>`
and push to it.
...
@@ -71,3 +71,5 @@ Open `bin/compile` in your editor, and change the following lines:
...
@@ -71,3 +71,5 @@ Open `bin/compile` in your editor, and change the following lines:
Commit and push the changes to your buildpack to your Github fork, then push your sample app to Heroku to test. You should see:
Commit and push the changes to your buildpack to your Github fork, then push your sample app to Heroku to test. You should see:
-----> Vendoring node 0.6.7
-----> Vendoring node 0.6.7
For more info, see
[
CONTRIBUTING.md
](
CONTRIBUTING.md
)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment