I have cloned it into dir ejabberd. Ran the following commands.
./autogen.sh
./configure
make rel
made a Procfile
web: ./rel/ejabberd/bin/ejabberdctl start
with the following line it.
heroku create -buildpack https :// github .com/archaelus/heroku-buildpack-erlang.git
then did
git push heroku master
its gives me the following error
root#Anubhav:/home/anubhav/new/ejabberd# git push heroku master
Counting objects: 25255, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5322/5322), done.
Writing objects: 100% (25255/25255), 13.78 MiB | 167.00 KiB/s, done.
Total 25255 (delta 19874), reused 25251 (delta 19872)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Fetching custom git buildpack... done
remote:
remote: ! Push rejected, no Cedar-supported app detected
remote: HINT: This occurs when Heroku cannot detect the buildpack
remote: to use for this application automatically.
remote: See https: // devcenter.heroku.com/articles/buildpacks
remote:
remote: Verifying deploy...
remote:
remote: ! Push rejected to infinite-retreat-6912.
remote:
To https: //git.heroku.com/infinite-retreat-6912.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https: //git.heroku.com/infinite-retreat-6912.git'
What am I doing wrong?
I do not think ejabberd can be used as is on Heroku. There is several dependancies in C and lib required that are probably not available on Heroku. At least it has never been tested but I would be surprised if it worked.
Related
josh#josh:~/my_projects/la_manne$ git push heroku master
Énumération des objets: 3, fait.
Décompte des objets: 100% (3/3), fait.
Écriture des objets: 100% (3/3), 230 octets | 230.00 Kio/s, fait.
Total 3 (delta 0), réutilisés 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-20 stack
remote: ! No default language could be detected for this app.
remote: HINT: This occurs when Heroku cannot detect the buildpack to use for this application automatically.
remote: See https://devcenter.heroku.com/articles/buildpacks
remote:
remote: ! Push failed
remote: !
remote: ! ## Warning - The same version of this code has already been built: 73ed9a909f2a7e80a0a45f0f5d86aa6c7fdd70c1
remote: !
remote: ! We have detected that you have triggered a build from source code with version 73ed9a909f2a7e80a0a45f0f5d86aa6c7fdd70c1
remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch.
remote: !
remote: ! If you are developing on a branch and deploying via git you must run:
remote: !
remote: ! git push heroku <branchname>:main
remote: !
remote: ! This article goes into details on the behavior:
remote: ! https://devcenter.heroku.com/articles/duplicate-build-version
remote:
remote: Verifying deploy...
remote:
remote: ! Push rejected to lamanne.
remote:
To https://git.heroku.com/lamanne.git
! [remote rejected] master -> master (pre-receive hook declined)
error: impossible de pousser des références vers 'https://git.heroku.com/lamanne.git'
remote: -----> Building on the Heroku-20 stack
remote: ! No default language could be detected for this app.
remote: HINT: This occurs when Heroku cannot detect the buildpack to use for this application automatically.
remote: See https://devcenter.heroku.com/articles/buildpacks
https://github.com/heroku/heroku-buildpack-php#usage
You'll need to use at least an empty composer.json in your
application.
$ echo '{}' > composer.json
$ git add composer.json
$ git commit -m "add composer.json for PHP app detection"
If you also have files from other frameworks or languages that could
trigger another buildpack to detect your application as one of its
own, e.g. a package.json which might cause your code to be detected
as a Node.js application even if it is a PHP application, then you
need to manually set your application to use this buildpack:
$ heroku buildpacks:set heroku/php
This will use the officially published version. To use the default
branch from GitHub instead:
$ heroku buildpacks:set https://github.com/heroku/heroku-buildpack-php
Please refer to Dev Center for further usage instructions.
I've been trying to do it for a long time, and I never can, I keep creating files and folders, new .git, I try but it doesn't work! I've been wanting to host my discord py bot, but the command git push heroku master always gets an ERROR! Now I leave the logs! I have git installed I am logged into HEROKU and registered! I have a GITHUB account and I have repositories
C:\Users\ruben\Desktop\Discord\Bot\ValientBot>git push heroku master Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 2 threads Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 2.57 KiB | 263.00 KiB/s, done.
Total 4 (delta 0), reused 0 (delta 0), pack-reused 0 remote: Compressing source files... done. remote: Building source: remote: remote: -----> Building on the Heroku-18 stack remote: -----> App not compatible with buildpack:
https://buildpack-registry.s3.amazonaws.com/buildpacks/heroku/python.tgz remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure remote: remote: ! Push failed remote: ! remote: !
## Warning - The same version of this code has already been built: eb6fced64ec14c05dd2f92e7cf40c0e2cd30a1ff remote: ! remote: ! We have detected that you have triggered a build from source code with version eb6fced64ec14c05dd2f92e7cf40c0e2cd30a1ff remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch. remote: ! remote: ! If you are developing on a branch and deploying via git you must run: remote: ! remote: ! git push heroku <branchname>:main remote: ! remote: ! This article goes into details on the behavior: remote: !
https://devcenter.heroku.com/articles/duplicate-build-version remote: remote: Verifying deploy... remote: remote: ! Push rejected to valient-bot. remote: To https://git.heroku.com/valient-bot.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://git.heroku.com/valient-bot.git'
If the project you’re deploying uses main as its default branch name, use $ git push heroku main
instead of
$ git push heroku master
Heroku has updated default git branch name to main and this might be a reason for the error that you are having.
this is my server folder: https://github.com/Yokubjon-J/react-chat-testSuite/tree/master/server. whenever i run "git push heroku master" i am getting the error below:
Total 866 (delta 199), reused 0 (delta 0), pack-reused 0
remote: Compressing source files... done.
remote: Building source:
remote:
remote: ! No default language could be detected for this app.
remote: HINT: This occurs when Heroku cannot detect the buildpack to use for this application automatically.
remote: See https://devcenter.heroku.com/articles/buildpacks
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to my-first-react-chat-app.
remote:
To https://git.heroku.com/my-first-react-chat-app.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/my-first-react-chat-app.git'
I have browsed through several stackoverflow answers to no avail.
Any suggestions?
I set buildpacks, typed "web: node index.js" in procfile, but none of it helped
The error says "No default language could be detected for this app.
Try:
heroku buildpacks:set heroku/the-programming-language OR
heroku create myapp --buildpack heroku/the-programming-language
refer-https://devcenter.heroku.com/articles/buildpacks
I ran cd .. and then git subtree push --prefix server heroku master. this way the problem was solved. For reference: https://dev.to/stlnick/how-to-deploy-a-full-stack-mern-app-with-heroku-netlify-ncb
I deleted yarn.lock and commit changes but still getting lockfiles error.
Counting objects: 24375, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (17171/17171), done.
Writing objects: 100% (24375/24375), 30.34 MiB | 1.03 MiB/s, done.
Total 24375 (delta 6150), reused 23977 (delta 5909)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Build failed
remote: ! Two different lockfiles found: package-lock.json and yarn.lock
remote:
remote: Both npm and yarn have created lockfiles for this application,
remote: but only one can be used to install dependencies. Installing
remote: dependencies using the wrong package manager can result in missing
remote: packages or subtle bugs in production.
remote:
remote: - To use npm to install your application's dependencies please delete
remote: the yarn.lock file.
remote:
remote: $ git rm yarn.lock
remote:
remote: - To use yarn to install your application's dependences please delete
remote: the package-lock.json file.
remote:
remote: $ git rm package-lock.json
remote:
remote: https://kb.heroku.com/why-is-my-node-js-build-failing-because-of-conflicting-lock-files
remote:
remote: ! Push rejected, failed to compile Node.js app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to weight-tracker-react-rails.
remote:
To https://git.heroku.com/weight-tracker-react-rails.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/weight-tracker-react-rails.git
'
There is a dropplet(vps) on digitalocean, the dropplet is built using dokku template. Following a bunch of instruction, I was able to set everything up. At least I think so. The problem appears during the build after git push. The log is here:
$ git push dokku master
Counting objects: 64, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (57/57), done.
Writing objects: 100% (64/64), 14.68 KiB | 0 bytes/s, done.
Total 64 (delta 4), reused 0 (delta 0)
remote: -----> Cleaning up...
remote: -----> Building ** from herokuish...
remote: -----> Adding BUILD_ENV to build environment...
remote: -----> Fetching custom buildpack
remote: -----> Node.js app detected
remote: -----> Installing node
remote: -----> Installing meteor
remote: Downloading Meteor distribution
remote:
remote: #
...
remote: ########################################################################
100.0%
remote:
remote: Meteor 1.2.1 has been installed in your home directory (~/.meteor).
remote:
remote: Now you need to do one of the following:
remote:
remote: (1) Add "$HOME/.meteor" to your path, or
remote: (2) Run this command as root:
remote: cp "/tmp/buildpacks/custom/meteor-o6l8/.meteor/packages/meteor-tool/1.1.10/mt-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor
remote:
remote: Then to get started, take a look at 'meteor --help' or see the docs at
remote: docs.meteor.com.
remote: -----> Bundling bundle
remote: -----> Building Meteor with ROOT_URL: http://****
remote: Killed
To dokku#****:**
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'dokku#****:**'
I am new to the theme. Where can I see what's gone wrong?
You might have too few resources to build meteor on your server. Please be sure you have at least 1GB of memory available. If you are on a smaller digital ocean droplet, you can also enable swap.