You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A command line tool for emulating Heroku build and runtime tasks in containers.
8
8
@@ -19,7 +19,7 @@ Download and uncompress the latest binary tarball from [releases](https://github
19
19
For example, you can do this directly in your Dockerfiles installing into `/bin` as one step:
20
20
21
21
```shell
22
-
RUN curl --location --silent https://github.com/gliderlabs/herokuish/releases/download/v0.7.6/herokuish_0.7.6_linux_x86_64.tgz \
22
+
RUN curl --location --silent https://github.com/gliderlabs/herokuish/releases/download/v0.8.0/herokuish_0.8.0_linux_x86_64.tgz \
23
23
| tar -xzC /bin
24
24
```
25
25
@@ -60,7 +60,7 @@ For example, build processes that produce Docker images without producing interm
60
60
`herokuish exec` will by default drop root privileges through use of [setuidgid](https://cr.yp.to/daemontools/setuidgid.html),
61
61
but if already running as a non-root user setuidgid will fail, you can opt-out from this by setting the env-var `HEROKUISH_SETUIDGUID=false`.
62
62
63
-
####Buildpacks
63
+
### Buildpacks
64
64
65
65
Herokuish does not come with any buildpacks, but it is tested against recent versions of Heroku supported buildpacks. You can see this information with `herokuish version`. Example output:
66
66
@@ -78,7 +78,7 @@ buildpacks:
78
78
79
79
You can install all supported buildpacks with `herokuish buildpack install`, or you can manually install buildpacks individually with `herokuish buildpack install <url> [committish]`. You can also mount a directory containing your platform's supported buildpacks (see Paths, next section), or you could bake your supported buildpacks into an image. These are the types of decisions that are up to you.
80
80
81
-
####Paths
81
+
### Paths
82
82
83
83
Use `herokuish paths` to see relevant system paths it uses. You can use these to import or mount data for use inside a container. They can also be overridden by setting the appropriate environment variable.
84
84
@@ -93,11 +93,11 @@ BUILDPACK_PATH=/tmp/buildpacks # Path to installed buildpacks
93
93
94
94
```
95
95
96
-
####Entrypoints
96
+
### Entrypoints
97
97
98
98
Some subcommands are made to be used as default commands or entrypoint commands for containers. Specifically, herokuish detects if it was called as `/start`, `/exec`, or `/build` which will shortcut it to running those subcommands directly. This means you can either install the binary in those locations or create symlinks from those locations, allowing you to use them as your container entrypoint.
99
99
100
-
####Help
100
+
### Help
101
101
102
102
Don't be afraid of the help command. It actually tells you exactly what a command does:
103
103
@@ -128,7 +128,7 @@ Having trouble pushing an app to Dokku or Heroku? Use Herokuish with a local Doc
128
128
instance to debug. This is especially helpful with Dokku to help determine if it's a buildpack
129
129
issue or an issue with Dokku. Buildpack issues should be filed against Herokuish.
130
130
131
-
####Running an app against Herokuish
131
+
### Running an app against Herokuish
132
132
133
133
```shell
134
134
docker run --rm -v /abs/app/path:/tmp/app gliderlabs/herokuish /bin/herokuish test
@@ -147,7 +147,7 @@ Mounting your local app source directory to `/tmp/app` and running `/bin/herokui
147
147
148
148
You can use this output when you submit issues.
149
149
150
-
####Running an app tests using Heroku buildpacks
150
+
### Running an app tests using Heroku buildpacks
151
151
152
152
```shell
153
153
docker run --rm -v /abs/app/path:/tmp/app gliderlabs/herokuish /bin/herokuish buildpack test
However, there is a risk of compatibility issues when running on a different platform than the one you are developing on. If you are getting strange compilation or segfaults, try running the build process on an x86 platform.
177
177
178
-
####Troubleshooting
178
+
## Troubleshooting
179
179
180
180
If you run into an issue and looking for more insight into what `herokuish` is doing, you can set the `$TRACE` environment variable.
0 commit comments