Building rocket.chat on heroku server faced error - heroku

I wanted to deploy the rocket.chat project on heroku, following the deployment instruction, I have encountered the following error:
"
Can't open /tmp/build_29c97eef7e456d21231bc9eb4751ca67/ringelco-racket-chat-a864ad48b50652f34205d656e8e6d93976ce69e3/packages/rocketchat-livechat/plugin/build.sh
/app/tmp/cache/meteor/.meteor/packages/tap_i18n/.1.8.2.10lihy6.24zh++os+web.browser+web.cordova/plugin.tap-i18n-compiler.os/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:116
throw error;
"
I have noticed that some other issues are related to such error (this and this), but nobody has answered it yet!
It would be appreciative if you could help me.
Thanks in advance,

Issue fixed.
I just pulled the latest code from Rocket.Chat.
Followed the step to deploy it on Heroku Rocket.Chat Herokyu Deployment.
You have to use buildpack https://github.com/RocketChat/meteor-buildpack-horse.git.

Related

How can i solve heroku Application error?

*I am having a Heroku Application error. I can not find how can I solve it. or you can say to me how can i remove the whole Heroku application from my project to re-create Heroku app.
thank you.

How to properly deploy a Spring Boot Web App on Heroku?

I am trying to deploy my Spring Boot Web application to HEROKU and I am getting the following error:
***> -----> Building on the Heroku-20 stack
-----> Determining which buildpack to use for this app ! No default language could be detected for this app. HINT: This occurs
when Heroku cannot detect the buildpack to use for this application
automatically. See https://devcenter.heroku.com/articles/buildpacks
! Push failed***
I tried setting the build back to heroku/java manually only to also get an error.
The app is built in java so I don't understand what is happening exactly. This is my first time deploying an app online. Any help or guidance will be greatly appriciated
Beppe C. gave me the solution. My pom.xml file was not at the root. I restructured my repo and I got past that error but faced another one.

Openshift 3 starter

Im trying to investigate how to get a simple SpringBoot project up and running on openshift 3 starter(free version).
Im using this simple starter project whixh uses widfly, see here:
https://github.com/callistaenterprise/spring-boot-openshift
I followed the build/deploy guide here and tried both wildfly and openjdk image types, both fail.
https://developers.redhat.com/blog/2017/02/23/getting-started-with-openshift-java-s2i/
The error in the build console is this:
Pod
blog2-1-build
Failed sync
Error syncing pod
Pod
blog2-1-build
Scheduled Successfully assigned blog2-1-build to ip-172-31-53-149.ec2.internal
i have no idea how to solve this, any advice help greatly appreciated.

Heroku Build API can't fetch source code

I'm trying to update my app on heroku using node heroku client, but it fails with the message
Unable to fetch source from: https://my-aws-account.s3.amazonaws.com/source.tar.gz?AWSAccessKeyId=...&Expires=...&Signature=...
The source code gzipped tarball is public and fresh during the deploy.
The node-heroku-client seems to follow build api properly. This error occurs after the build has began.
It seems to be a bug on heroku build servers, but I would like to know if someone else had this problem before...
It's a known issue with at heroku, the upstream provider is working on fix https://status.heroku.com/

Trouble Migrating from Shared DB to Dev Plan

I just followed the steps to migrate my very small shared db to Heroku's new "dev" plan. Everything went very smoothly until I tried $ heroku addons:remove shared-database
I received the following error:
$ heroku addons:remove shared-database
-----> Removing shared-database from [my_app]... failed
! Shared databases cannot be removed
I have confirmed that my DATABASE_URL matches my HEROKU_POSTGRESQL_[COLOR]_URL, and that my app is fully functioning.
I work at Heroku on the Data team. We're sorry about that: the problem you observed was a temporary problem on our end, not a problem with your code. Please try again, it was an issue on the bamboo stack specifically.
As an aside, consider using the cedar stack. :)

Resources