Closed
Bug 1407532
Opened 7 years ago
Closed 7 years ago
Deploy to Heroku using Deploy to Heroku button is broken
Categories
(Webtools Graveyard :: Pontoon, defect, P3)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mathjazz, Assigned: jotes)
Details
Attachments
(1 file)
-----> GIT Submodules app detected
---> Installing parseconfig gem
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions for the /var/lib/gems/2.3.0 directory.
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- parseconfig (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /app/tmp/buildpacks/c909f172553514c0516a6d2b64ed693530df6edf3dd0127117ce77320c06cafb0c504eb17c9dd742e8142e94fdf37ed3fee0c52251237b54cb83139db42e7994/bin/install_git_submodules.rb:1:in `<main>'
! Push rejected, failed to compile GIT Submodules app.
! Push failed
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → poke
Assignee | ||
Comment 1•7 years ago
|
||
I updated the buildpack responsible for fetching git submodules, added information about the python runtime and the build phase of deployment is okay. However, I noticed that there are problems with the /heroku-setup/ view (django raises an exception about non allowed host) - I'm still working on this issue.
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/pontoon
https://github.com/mozilla/pontoon/commit/5d4f67103a768aa7b6468d1fa8f11d3300d36a7e
Fix bug 1407532: Fix "Deploy to Heroku" button (#735)
* Update version of buildpack for git submodules
* Add SITE_URL setting to app.json and mark as required
* Remove code responsible for automatic discovery of SITE_URL after a
deploy on Heroku
* Add runtime.txt and set python2 as the default for python buildpack
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•