Heroku introduced "private spaces", is it possible to migrate an existing app to a private space?
https://blog.heroku.com/archives/2015/9/10/heroku_private_spaces_private_paas_delivered_as_a_service
There is currently not a one-click/command migration path (e.g. clone, fork), but apps in private spaces still use the same cedar-14 stack, so most apps that work on Heroku today can be re-created in a private space and just work.
Related
Is there a way to forward traffic from an old heroku app hosted on their (no longer supported) cedar-14 stack to the new version of the app (on heroku-18)? I can no longer build to the cedar-14 site. Both apps are using Heroku's default domains, [app name].herokuapp.com.
The goal is to keep the old code in case it is needed while directing people visiting the old domain access to the newly written site. This can be accomplished with carefully sequenced site name changes. Heroku describes how to change site names here. You will also have to update git remotes and such on your local machine but the Heroku instructions tell you how to do that, too.
The now somewhat obvious sequence is:
change name of [old site] to something like [old_site]-backup
change name of [new site] to [old site]
I'm deploying a Play 2.7.x Application in Heroku and my search capability based on Lucene is crashing because of not finding the public folder containing the documents to index. I then logged into the Heroku deployment and I see there are only binaries, I searched on the root i.e. on top of ../app but no luck finding my public assets.
UPDATE I'm deploying using Heroku CLI and the SBT plugin sbt stage deployHeroku
Any ideas?
I am sharing a MongoDB between a few heroku apps and would like to move the ownership/billing to another app.
I have tried attaching (heroku addons:attach) to the receiving app and then using the heroku addons:detach command on the billing app, but this doesn't work.
Heroku support just confirmed that it is not possible to change the billing app for an add-on.
You can attach the add-on to other apps, but if you delete the original billing app then it will instantly delete your database without warning - even if it is attached to other active apps.
Some add-ons like Postgres offer a fork option, so you may be able fork, reconnect to the new instance, and delete the old database. The Postgres fork command looks like:
heroku addons:create heroku-postgresql:standard-0 --fork the-old-app-name::HEROKU_POSTGRESQL_CHARCOAL --app the-new-app-name
Where HEROKU_POSTGRESQL_CHARCOAL is the ENV variable name of your old database on your old app.
My app only uses PHP and SQLite.
I get this error:
Heroku push rejected, no Cedar-supported app detected
You should be a able to use PHP, there is a PHP buildpack — although it’s not very well documented on the Heroku site. Looking at its detect script, it is checking for an index.php file. Does your app have one? If not you’ll need to create one, if only so that it’ll be detected as a PHP app.
If your app still isn’t being detected as a PHP app, you could try explicitly specifying the buildpack to use with a config var:
$ heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-php
A bigger problem is that you won’t be able to use SQLite on Heroku. Even if you were to create your own buildpack that added the relevant SQLite libraries, the read-only filesystem would mean it’s of little use. You should look into using Postgres (or possibly MySQL using an add-on).
I am working on a private repo, I need to integrate CI for my app. How to integrate travis for my private repo. Or is it possible to have travis on our server
Travis Pro supports private github repos.
There are other hosted CI services. For example, you could use Circle.
Also, if running Travis checks locally will be enough for your case, see: https://github.com/PaulRosset/previs