I have a buildpack here: https://github.com/y0utubeperson1/heroku-test-push
It compiles successfully and pushes to my Heroku slugs, which I set them up using GitHub Actions to compile: https://github.com/y0utubeperson1/heroku-test-push-slug
Its been over 24 hours and it does compile successfully. But it wont show on the Heroku Buildpack store: https://elements.heroku.com/search?q=y0utubeperson1%2Fheroku-test-push
This is how it is set up: https://i.imgur.com/B9RG5qx.png
Why is this happening?
Related
What worked so far: I installed sonarqube locally with mvn sonar:sonar I get the results on localhost:9000.
Now I want to do the same thing for our app that is hosted on heroku. I could successfully install the buildpack from NayaraCaetano with
heroku buildpacks:set https://github.com/ https://github.com/NayaraCaetano/heroku-buildpack-sonarqube.git/heroku-buildpack-sonarqube.git -a ourAppName
On heroku I saw that the buildpack was added.
Not working / unclear
So how am I now able to open the sonarqube findings from heroku, I didn't find any documentation on this but not shure if I am missing the point of what this buildpack is supposed to do
In the end we were able to use sonarcloud.io. Since our heroku app was anyway connected to github we just created an account at sonarcloud that was connected to our master branch.
It's not really the solution i hoped for, but it meet our goal to constantly monitor our code coverage on every commit to the master branch.
First thing i am very new in Vue, adonis and heroku. so please tell me all the steps in answer
i have a project build in vuejs(frontend) and adonisjs api-only and i want to deploy this project on heroku with postgresql database.
What i am done till now:-
1). create a heroku account
2). create a project on heroku
3). upload frontend dist/ folder on heroku using these command
git add --all
git commit -m "initial commit"
git push heroku master
And my frontend run perfectly but i don't know how to deploy backend and how to create database
in heroku.
my working directories are
To deploy the back-end application you can do the same steps as you did for the other application.
Here's what's changing:
Add database with heroku add-ons (https://elements.heroku.com/addons/heroku-postgresql)
! When adding the add-on new heroku environment variables are created. (If they do not appear, see below)
Interesting things to know:
To execute Adonis commands : node ace <your_command> (node ace migration:run)
I advise you to use the heroku environment variables. Don't forget to add the variable ENV_SILENT = true to avoid errors because of the.env file.
Get connection db informations: (on your postgresql add-on):
Some additional information
Personal project deployed on heroku (.gitlab-ci.yml) : https://gitlab.com/CrBast/website
Interesting article : https://scotch.io/tutorials/deploying-adonisjs-apps-to-heroku
If my explanations are not clear, don't hesitate to tell me :)
I have a shiny app and want to deploy it to Heroku. I tried to follow the steps as mentioned in:
https://github.com/btubbs/heroku-buildpack-shiny
I created a git Git repository and put the R files into it. Then, I created an app in heroku and tell Heroku to use a custom buildpack for my app. But, I was not be able to enable Heroku websockets support.
Error is:
Couldn't find that feature.
I can't figure out how to deal with this problem. Is there any other way to deploy the shiny app to Heroku?
Have you seen https://github.com/virtualstaticvoid/heroku-docker-r?
Check out the example shiny app too. To specify additional dependencies, you can still use init.R.
To deploy using Docker, you might have to move your current Heroku app to a container stack. This can be done with the heroku stack:set CLI command:
$ heroku stack:set container
Here's a minimal example. Basically:
Create run.R file with the following
library(shiny)
port <- Sys.getenv('PORT')
shiny::runApp(
appDir = getwd(),
host = '0.0.0.0',
port = as.numeric(port)
)
Commit to git
Create a new heroku app with
heroku create --buildpack https://github.com/virtualstaticvoid/heroku-buildpack-r.git
git push heroku master
That's all there is to it.
Another way would be to deploy using Docker. I am not an expert, but it took me a couple of days to deploy an app using this soluation. Many tutorials exist and could bring you to achieving this.
I have deployed the Parse-Server-Example to the Heroku directly through the github and it is successfully deployed, but my Heroku App dashboard shows that the repo size is 0.
Could you help me?
Thanks
Your Heroku repo size will be zero because you are linking parse-server through github and it's not stored on Heroku. What you can do to change this is clone your repo by installing Heroku command line tools and this command.
heroku git:clone -a project-name
Make whatever changes you like and push back to heroku by using
git push heroku master
After pushing your project to Heroku it should tell you the size of your repo.
I am trying to add a [buildpack][1] to my Heroku app
heroku buildpacks --app appname
1. heroku/python
2. https://github.com/heroku/heroku-buildpack-pgbouncer.git
3. https://github.com/beanieboi/nginx-buildpack.git
4. https://github.com/cyberdelia/heroku-geo-buildpack.git#1.3
But deployment is failing because before Heroku can fetch the new buildpack it runs
python manage.py collectstatic and it will not proceed further. So is it possible to fetch the new buildpack maually and then trigger the deployment.
I am using basically the same buildpacks, however the order is important. You will want the Python buildpack to be last since that is what determines that collectstatic should be run.
These are the buildpacks I use and their order:
https://github.com/beanieboi/nginx-buildpack.git
https://github.com/cyberdelia/heroku-geo-buildpack.git#1.3
https://github.com/heroku/heroku-buildpack-pgbouncer
https://github.com/heroku/heroku-buildpack-python#v69
If that doesn't work, you can also disable collectstatic with an environment variable: https://devcenter.heroku.com/articles/django-assets#disabling-collectstatic. You will need to manually run collectstatic after the deployment or make it part of the Procfile, though.