5 ms·
Yes I do :) You can see on the following step which image is being used when deploying an app: https://github.com/progrium/dokku/blob/master/dokku#L33 https:/
by agilebyte 13y ago
Yes I do :)
You can see on the following step which image is being used when deploying an app:
https://github.com/progrium/dokku/blob/master/dokku#L33 https://github.com/progrium/dokku/blob/master/dokku#L33
So what I did was change that to an image of my own based on the progrium/buildstep one:
sudo docker run -i -t progrium/buildstep /bin/bash
Now you can make changes to it and save them into your new image (while you are still logged in to progrium/buildstep):
sudo docker commit <id> myownimage
OK, and inside this image I have referenced my own buildstep instead of the default Heroku one. The relevant txt document is in /build/.
And to get to the point I have changed the npm install line to run pointing to the http EU repo.
npm install --registry "http://registry.npmjs.eu" --userconfig $build_dir/.npmrc --production 2>&1 | indent
That is one way to go about it.
- andrewmunsell 13y agoGreat, thanks. I also figured out that I could put the following line into a file called `.env` (I was originally trying to use a file named `ENV`): export BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs This will use Heroku's version of the build pack, which already has a fix for the NPM problem.