Is it possible to deploy a Jython app, which uses Flask, on Heroku? There is very little info on this, and according to this article it should be possible by adding a pom.xml: http://venturebeat.com/2011/08/26/heroku-java/. I know Heroku supports JRuby natively, but there's nothing on Jython.
I have an app that references a .jar library, from within Jython. When trying to push the local git repo to Heroku a Python app is detected, packages in requirements.txt file are installed and deploy completes. Unfortunately, when accessing the app online, I get an Application error (Note: gunicorn package has been installed to project and added to requirements.txt). The Log states the following:
Related
I am looking to play with apache-superset on a cloud-based ide. I have it on my local. I tried unsuccessfully to set it up on gitpod. I wanted suggestions on where can I set it up, opensource preferably not necessarily. I believe cloud9 is 1 such place, but I am looking for other options before I settle. If you've ever set it up on any such platform, even if it is on gitpod and can help me, kindly do so.
[Disclaimer: Gitpod staff]
You can indeed use Gitpod to work on apache-superset, and for that you'll just need a working configuration.
From what I can see in apache-superset's requirements, you'll need to get:
PostgreSQL (e.g. by using Gitpod's official gitpod/workspace-full-postgres Docker base image)
Redis (e.g. by installing it in a Dockerfile via sudo apt-get install)
Various Python dependencies (e.g. by running pip install . after cloning)
Various Node.js dependencies for the front-end (e.g. by running npm install)
Here is a basic configuration I wrote to achieve this:
https://github.com/jankeromnes/incubator-superset/commit/0d345a76ec8126fd1f8b9bc7b6ce4961bf3b593d
What it does is:
Create a Docker image with PostgreSQL and Redis
Once the repository is cloned, open 4 separate Terminals ("tasks"):
Redis server
Superset backend
Superset worker
Superset front-end
All dependencies will be installed automatically, and once the front-end is ready, it will automatically open in a web preview IDE side panel.
You can try it out by opening my personal fork of the apache-superset repository in Gitpod, e.g. by following this link:
https://gitpod.io/#https://github.com/jankeromnes/incubator-superset
Encountered this problem with a fresh install of Rubymine for Mac, Ruby and Rails and following Roku integration steps in https://www.jetbrains.com/help/ruby/heroku-getting-started.html
I tried deleting directory .local/share/heroku and then heroku update, but does not fix the issue, which occurs both when, say trying to upload public key file, and when trying to deploy application with Heroku run configuration.
I'm doing the tutorial on Heroku Dev Center (found here: https://devcenter.heroku.com/articles/getting-started-with-scala#introduction). I got through all the steps leading up to running my app locally (as far as I can tell the app is deployed properly and I have installed the app dependencies), but when I run the command 'heroku local web -f Procfile.windows' it gives me back an error on web.1 saying "the system cannot find the path specified"... I double checked that web.1 is up using 'heroku ps' command.
Help!
Seems to be related to the JDK version. I was trying to use JDK 10.0.1 and encountered the same problem. When I changed to point to JDK 1.8.0_121 which (I think) Heroku installed, I was able to continue.
The file specified at the Procfile.windows is not available, yet.
web: target\universal\stage\bin\play-getting-started.bat
To solve this, run:
sbt compile stage
in the root of the project directory to produce the required files.
I'm attempting to deploy a very simple ruby (not rails) app using Capistrano on Site5 shared hosting, and so far my cap deploy:setup and cap deploy commands have succeeded so everything is deployed (I'm assuming) behind the public_html screen - so now I need a symlink to the relevant folder. I know this is the public folder of a deployed rails app, but what do I target for a deployed ruby app?
Thanks so much,
Becky
I am porting a Heroku app from Aspen to Cedar stack at Heroku, following their instructions.
I'm at the last deploy step. I get this error:
2012-10-22T11:23:53+00:00 heroku[web.1]: Starting process with command `bundle exec thin start -p 40310 -e production`
2012-10-22T11:23:54+00:00 app[web.1]: bash: bundle: command not found
I can't see how I can be responsible for telling the Heroku stack where bundle is, or providing it, since bundler is used by it for exactly this job. This command is specified in the Procfile for the app:
web: bundle exec thin start -p $PORT -e $RACK_ENV
Another similar question on stackoverflow suggests that this happens if the app is pushed to Heroku without a Procfile initially, so Heroku gets the wrong idea about what kind of app it is. That poster deleted his app and created a new one and reported success. However, the effort involved in deleting and recreating my ported app is high. Is there some way I can fix this rather than start over?
Heroku's slug build process must have changed with regard to ruby 1.8.7 apps. I'm guessing they started bundling to 1.8 paths instead of 1.9.1 for 1.8 apps. My previously working app stopped working after I tried to push a new revision.
Here's what got it working again:
heroku config:add PATH=bin:vendor/bundle/1.8/bin:/usr/local/bin:/usr/bin:/bin GEM_PATH=vendor/bundle/1.8
I took these paths from a newly created app using the same git repository as I used before.
EDIT: Turns out that heroku published a devcenter article Changing Ruby Version Breaks Path that specifies paths for various ruby versions.
I had the same issue and I solved it by setting the correct heroku config variables
$ heroku config
=== xxxx Config Vars
DATABASE_URL: postgres://(...)
GEM_PATH: vendor/bundle/ruby/1.9.1
HEROKU_POSTGRESQL_CRIMSON_URL: postgres://(...)
LANG: en_US.UTF-8
PATH: bin:vendor/bundle/ruby/1.9.1/bin:/usr/local/bin:/usr/bin:/bin
PGBACKUPS_URL: https://(...)
RACK_ENV: production
RAILS_ENV: production
you can create an empty rails app, push it to heroku and check the variables it automatically set, then copy (and adapt) them to your application