PHPackages                             wojtekk/herokupipelines4travis - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. wojtekk/herokupipelines4travis

ArchivedLibrary[DevOps & Deployment](/categories/devops)

wojtekk/herokupipelines4travis
==============================

v0.5.0(8y ago)2201[1 PRs](https://github.com/wojtekk/HerokuPipelines4Travis/pulls)Shell

Since Mar 9Pushed 6y ago1 watchersCompare

[ Source](https://github.com/wojtekk/HerokuPipelines4Travis)[ Packagist](https://packagist.org/packages/wojtekk/herokupipelines4travis)[ RSS](/packages/wojtekk-herokupipelines4travis/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (51)Used By (0)

Heroku Pipelines for Travis CI
==============================

[](#heroku-pipelines-for-travis-ci)

Initial setup
-------------

[](#initial-setup)

Create application and configure pipeline on [Heroku](https://devcenter.heroku.com/articles/pipelines).

To initiate project follow commands:

```
npm install herokupipelines4travis lodash --save-dev
$(npm bin)/hp4t setup
```

*Package *lodash* is optional - install it if you want to use it in `infrastructure/`.*

You can edit files:

- `.travis.yml` - Travis CI configuration file
- `infrastructure/` - directory with infrastructure configuration
    - `base.js` - base configuration
    - `stage.js` - stage environment configuration
    - `production.js` - production environment configuration

Convention
----------

[](#convention)

For simplify usage you should define:

```
alias hp4t="$(npm bin)/hp4t"
```

Setup commands
--------------

[](#setup-commands)

- `hp4t setup` - initialise project
- `hp4t export app_name [heroku_api_key]` - export existing Heroku application configration

Commands for Travis CI
----------------------

[](#commands-for-travis-ci)

- `hp4t init` - initialise runtime environment
- `hp4t provision environment_name` - provision Heroku app
- `hp4t pipeline` - setup Heroku pipeline
- `hp4t deploy app_name` - deploy code to Heroku app
- `hp4t run app_name "command with params"` - run command on Heroku application (useful for database migration)
- `hp4t promote app_name` - promote existing application to next environment
- `hp4t package output-file.tgz` - build a tarball (tgz) with dependencies for Npm based projects
- `hp4t deploy-tarball app_name file.tgz` - deploy tarball file to a Heroku aplication

Read more
---------

[](#read-more)

- [Heroku Pipelines](https://devcenter.heroku.com/articles/pipelines)
- [Travis CI](https://travis-ci.org/)
- [Heroin-JS](https://www.npmjs.com/package/heroin-js)

Example Travis configuration file
---------------------------------

[](#example-travis-configuration-file)

`.travis.yml`

```
---
language: node_js
node_js: stable
env:
  global:
  # ========== Heroku Pipelines for Travis =========
  # HEROKU_API_KEY
  - secure: "..."
  - HP4T_HEROKU_APPNAME_STAGE=hp4t-test-stage
  - HP4T_HEROKU_APPNAME_PRODUCTION=hp4t-test
cache:
  directories:
  - node_modules
install:
- npm install
script:
- npm test
- npm lint
deploy:
  - provider: script
    skip_cleanup: true
    script: make deploy
    on:
      branch: master
after_success:
- hp4t notify-rollbar
```

`Makefile`

```
deploy:
  hp4t init
  hp4t package build.tgz
  hp4t pipeline
  hp4t provision stage
  hp4t deploy-tarball build.tgz ${HP4T_HEROKU_APPNAME_STAGE}
  hp4t run ${HP4T_HEROKU_APPNAME_STAGE} "npm run migrate-database"
  hp4t provision production
  hp4t promote ${HP4T_HEROKU_APPNAME_STAGE}
  hp4t run ${HP4T_HEROKU_APPNAME_PRODUCTION} "npm run migrate-database"
```

*Please remember to use one tab indent in `Makefile`.*

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity10

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity66

Established project with proven stability

 Bus Factor1

Top contributor holds 99.1% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~10 days

Recently: every ~3 days

Total

50

Last Release

3264d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/59187?v=4)[Wojciech Krawczyk](/maintainers/wojtekk)[@wojtekk](https://github.com/wojtekk)

---

Top Contributors

[![wojtekk](https://avatars.githubusercontent.com/u/59187?v=4)](https://github.com/wojtekk "wojtekk (112 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (1 commits)")

### Embed Badge

![Health badge](/badges/wojtekk-herokupipelines4travis/health.svg)

```
[![Health](https://phpackages.com/badges/wojtekk-herokupipelines4travis/health.svg)](https://phpackages.com/packages/wojtekk-herokupipelines4travis)
```

###  Alternatives

[in2code/in2publish_core

Content publishing extension to connect stage and production server

40143.4k](/packages/in2code-in2publish-core)[tiamo/phpas2

PHPAS2 is a php-based implementation of the EDIINT AS2 standard

4678.9k](/packages/tiamo-phpas2)[wapmorgan/php-rpm-packager

RPM packager for PHP applications.

116.5k](/packages/wapmorgan-php-rpm-packager)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)