Skip to content

Loading…

Additional documentation #3

Merged
merged 1 commit into from

2 participants

@mck-

For people unfamiliar with git, the push without specifying a branch would throw an error.

Also added heroku open for people new to heroku.

@jsmpereira jsmpereira merged commit 95d71d6 into jsmpereira:master
@jsmpereira
Owner

Merged. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Showing with 5 additions and 4 deletions.
  1. +5 −4 README.md
View
9 README.md
@@ -31,17 +31,18 @@ To avoid trouble with SBCL source encoding use: ```heroku config:add LANG=en_US.
And deploy:
- git push heroku
+ git push heroku branch
-That's it!
+Where you should replace *branch* with the branch of your choice. There are currently 2 branches. *Master* has Huchentoot specific code and *aserve* has AllegroServe specific code.
+
+That's it! Use `heroku open` to view your app in your browser!
## More details:
-There are currently 2 branches. *Master* has Huchentoot specific code and *aserve* has AllegroServe specific code.
Currently https://github.com/jsmpereira/heroku-buildpack-cl let's you run Hunchentoot with SBCL and CCL and AllegroServe(portableaserve) with CCL.
There is a pending issue with [acl-compat](https://github.com/mtravers/portableaserve/tree/master/acl-compat) bundled with portableaserve preventing use with SBCL. Look [here](https://github.com/mtravers/wuwei/issues/10) for more information.
The file heroku-setup.lisp gets loaded at compile time, and needs to load any Lisp files or packages required.
-Thanks to [Mike Travers](https://github.com/mtravers) for getting Common Lisp on Heroku.
+Thanks to [Mike Travers](https://github.com/mtravers) for getting Common Lisp on Heroku.
Something went wrong with that request. Please try again.