3 ms·
Adding a couple of responses from Genie's creator [1], when parent commenter mentioned these issues a few months ago, for visibility in case it's helpful to so
by sundarurfriend 5y ago
Adding a couple of responses from Genie's creator [1], when parent commenter mentioned these issues a few months ago, for visibility in case it's helpful to someone here:
> startup time for the server was SO large that it just does not work on heroku
Response: The solution (which granted should be maybe better documented) is to set the `EARLYBIND` env variable to `true` - this will allow Genie to bind to the port very early so Heroku will love it.
> many features like authetication were nowhere to be found.
Response: Genie has built in support for handling (encrypted) cookies and sessions and plugins like GenieAuthentication (or GenieAuthorisation) and SearchLight provide straightforward features. Have you used these?
----
With that said, I myself do think of Genie as (currently) something to be used when (a) you already have Julia code and need a web front-end for it, or (b) you want to experiment and possibly break things for the potential of expanding horizons.
[1] https://news.ycombinator.com/item?id=29830003 https://news.ycombinator.com/item?id=29830003
- blindseer 5y agoThanks for sharing the information about EARLYBIND and GenieAuthentication. I will say that when I used EARLYBIND it still took too long for Heroku. That's not to mention that didn't solve any of the live development workflow issues. I looked into GenieAuthetication but it doesn't support SSO and a bunch of other features that other modern authetications libraries support.