How can you upgrade an existing graphenedb instance to the latest version?
I tried:
heroku addons:add graphenedb --version v220
Adding graphenedb on myApp ... failed
! That type of add-on can only exist once per app and it already exists for myApp.
Or is it not possible and should I migrate the data to a new instance with the latest version?
BTW, I also tried heroku addons:upgrade. That was NOT what I was looking for!
I'm Alberto, one of the founders of GrapheneDB.
As you have noticed, $ heroku addons:upgrade graphenedb:plan will upgrade the plan, not the version of Neo4j.
Currently it's not possible to upgrade the version of Neo4j through the UI or the Heroku CLI. There are two options:
Export your data store using the export feature in the admin tab. Download a copy. Remove the add-on, add it again with the new version of Neo4j and perform a restore (admin tab again) with the downloaded store file.
Open a support ticket specifying the database and the version you'd like to have and we'll do it for you.
Thanks for using GrapheneDB!
Related
I'd like to get the release version of my app in Heroku on PHP. I was hoping it might be available as an environment variable, for example like $_ENV['HEROKU_RELEASE'] might retrieve v23. Is there a way to get ahold of this?
Yes, that is possible, by enabling dyno metadata on your app with the following command:
heroku labs:enable runtime-dyno-metadata -a
Then, Heroku will set a HEROKU_RELEASE_VERSION environment variable on your app (as well as other ones, which are all described in the article linked above).
That variable includes the number of the current release for your app.
So to start I made an Elixir application using Phoenix framework.
This application uses coherence dependency for authentication to the website. This dependency was installed as it is advised on the git repo with -full argument to install all the options coherence has.
Then, I did just change a couple of lines in config.exs file of my project to use mailgun service for mailing and put credentials over there.
Next, I installed and configured my other deps (they have nothing to do with coherence).
Locally, my application could compile and run without problems.
Then, I wanted to deploy it to Heroku using Phoenix guidelines.
When I completed all the steps, I got an error when trying to push the application to Heroku.
I then tried to check the file lib/mix/tasks/coherence.clean.ex and the line 162 where I found a comment that said there is an error with updating a config file, but I couldn't figure out what that means and how to solve that.
I tried to make a fresh phoenix application, installing coherence with the same or different options and afterward deploying it following the Phoenix guidelines. Every time I was getting the same error.
I also want to note that I did try to create elixir_buildpack.config file and putting always_rebuild=true there and had no success. (it is a solution mentioned in troubleshooting section of deploying to Heroku guide)
So, my question is, what do I need to change in my config.exs file (or elsewhere) in order to make at least a fresh application with coherence installed to compile and work on Heroku?
useful links:
coherence dep github link
Thanks a ton guys.
The Heroku Buildpack for Elixir currently defaults to Elixir 1.2.6 while the code that throws that error uses the else syntax with with, a feature that was added in Elixir 1.3.0, so you need to set the Elixir version to use to 1.3.0 or later by adding the following to elixir_buildpack.config:
elixir_version=1.3.2
Is it possible to attach addons to a standalone postgres database created at https://postgres.heroku.com ? I'm using the dev plan.
The database details page # https://postgres.heroku.com/databases/ shows "Heroku PG-Backups addon not attached" under Snapshots heading. I couldn't find a way to add the PG-Backups addon.
You probably need to take a look at the docs: https://devcenter.heroku.com/articles/pgbackups#provisioning-the-add-on
My Heroku app had its shared database upgraded automatically to the dev plan. I then wanted to upgrade the dev plan to the $9/month plan. I did this, and thinking that it would just allow me to have more rows I deleted the old free 'dev' addon. Now I think I've deleted the database.
I had no backups so I think my only option is to get the data out of the old shared-database. The instructions to upgrade from shared to dev assume you are already on the shared - but I am not. Is there any way to re-upgrade from the shared-database to a dev one?
I ended up contacting support(at)heroku.com.
They fixed it and admitted the upgrade experience is confusing - so watch out when trying to upgrade your plan ...
I have a main app on heroku and another app A on git in location github:a.
I want to create, when it is necessary, copies of A as A1,A2,A3...AN as separate apps on heroku from my main app automatically with different parameters.
How can i do that?
Edit: This process should be done by my main app automatically.
Updating this answer due to Heroku command DEPRECATION:
heroku fork has been deprecated as a core command as of 12/01/2017.
You will need to install the heroku-fork plugin to continue using this command.
heroku plugins:install heroku-fork
Here is a link to the Github plugin repo.
Use heroku fork to copy an existing application, including add-ons, config vars, and Heroku Postgres data.
See this KB page: Forking Applications.
Heroku toolbelt now provides a fork method to clone an existing application, see my answer here :
how to clone a project on heroku
There is a new feature on Heroku called Review Apps. One can create copies of the app manually or set up automatic copies from new PRs on Github.
Read more at: https://devcenter.heroku.com/articles/github-integration-review-apps
Simply create new applications and push your code to them. If you need to copy data, checkout the pgbackups transfers.
For management purposes, check out this dev center article.
To do this programatically, you'll need to look at the Heroku gem, and then figure out a way of getting something to git push to the appropriate remote. I would be surprised if this was possible to be honest.