-
Notifications
You must be signed in to change notification settings - Fork 332
Running from git master
This page documents how to run Pump.io from Git master, as opposed to the version on npm.
Installation is super easy. Run:
$ [sudo] npm install -g e14n/pump.io
This will work even if you already have the npm version installed.
Pump.io's git master is, generally-speaking, suitable for daily use. A fair amount of effort is put into making sure that this remains the case, and that things aren't merged to master
unless they're stable and ready. Additionally, at least as of 2016-06-07 (with npm's pump.io@latest
being 0.3.0
), git master
is actually more stable, because a lot of bugfixes, etc. have gone in since the last npm release.
That being said, running from git master is not for the faint of heart. At the very least, you should have a basic understanding of how npm works (e.g. how npm resolves dependencies and how those dependencies are organized on the filesystem) and be willing and able to file good bug reports, because things will break from time to time.
- Follow one of the community accounts (in particular, large new features or refactorings will be announced on these to help you be better prepared for bugs)
- Run
npm@latest
- Make sure to regularly rerun
[sudo] npm install -g e14n/pump.io
to ensure you have the latest code (git master is stable enough that you can probably put this in a cronjob - just make sure to watch community accounts for upcoming semver-major breaking changes) - Don't forget to restart your pump.io daemon after upgrading via npm
- Glance through the logs once and a while for errors (or even better, practice artificial ignorance)
- File any and all bugs you encounter (but search for duplicates first!)