squeek502 / heroku-buildpack-luvit

Heroku buildpack for Luvit 2.0

Heroku Buildpack for Luvit 2.0

A Heroku buildpack for Luvit 2.0 and/or Lit apps.

Usage

To create a new Heroku app using this buildpack:

heroku create --buildpack https://github.com/squeek502/heroku-buildpack-luvit.git

The buildpack will detect that your app has a package.lua in the root.

Luvit Apps

By default, Luvit will be compiled and added to PATH.

An example Luvit app can be found in examples/luvit_app and a running instance of this example can be found at luvit-buildpack-luvit-app.herokuapp.com

Truncated example output from a git push:

-----> Fetching custom git buildpack... done
-----> luvit app detected
-----> Found package.lua
-----> Fetching lit and building luvit
       ...
       done building: lit
       done: success
       ...
       done building: luvit
       done: success

       Luvit built to .luvit/bin/luvit

-----> Installing deps
       ...
       done: success

-----> Skipping lit make step (main.lua not found or SKIP_MAKE config var set)
-----> Creating runtime environment
-----> Discovering process types
       Procfile declares types -> web

-----> Compressing... done, 15.0MB
-----> Launching... done, v3
       https://luvit-buildpack-luvit-app.herokuapp.com/ deployed to Heroku

Note: If your app contains a main.lua and you don't want to run lit make, set the config var SKIP_MAKE (see Options)

Lit Apps

If a main.lua file is found in the root, then lit make will be executed automatically.

An example Lit app can be found in examples/lit_app and a running instance of this example can be found at luvit-buildpack-lit-app.herokuapp.com

Truncated output from a git push:

-----> Fetching custom git buildpack... done
-----> luvit app detected
-----> Found package.lua
-----> Fetching lit and building luvit
       ...
       done building: lit
       done: success
       ...
       done building: luvit
       done: success

       Luvit built to .luvit/bin/luvit

-----> Installing deps
       ...
       done: success

-----> Running lit make (main.lua found and SKIP_MAKE config var not set)
       ...
       done building: lit-example
       done: success

-----> Creating runtime environment
-----> Discovering process types
       Procfile declares types -> web

-----> Compressing... done, 15.0MB
-----> Launching... done, v3
       https://luvit-buildpack-lit-app.herokuapp.com/ deployed to Heroku

Options

To stop lit make from being executed:

heroku config:set SKIP_MAKE=

To specify the luvi version to use:

heroku config:set LUVI_VERSION=2.7.6

To specify the lit version to use:

heroku config:set LIT_VERSION=3.5.4

heroku-buildpack-luvit's Issues

Initialization

Hello. I'm having some troubles to connect the script to heroku. May you help me?

I'm not sure how to put the lua files and stuff, how to use the cedar-14 + this buildpack at once... it's confusing X_X

Dyno and compiling problems

• Solved a problem with dyno, I'm sorry for this awful spam

SSL Certificate Expired

I was having trouble trying to push the project and I just noticed it is the buildpack (this one)

The error message:

remote: curl: (60) SSL certificate problem: certificate has expired
remote: More details here: https://curl.haxx.se/docs/sslcerts.html
remote:
remote: curl failed to verify the legitimacy of the server and therefore could not
remote: establish a secure connection to it. To learn more about this situation and
remote: how to fix it, please visit the web page mentioned above.
remote:  !     Push rejected, failed to compile luvit app.
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !       Push rejected to modulo-bot.
remote:
To https://git.heroku.com/modulo-bot.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/modulo-bot.git'

I have tried two other buildpacks for luvit. The push worked, but when I tried to turn the system on it returned

WARNING: forgot to close luv_pipe lhandle=0x40bafaa8 handle=0xb1b290
Process exited with status 255

So I'd say it could be a problem in luv/luvit itself?