You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering that lux is sort of a batteries-included api solution, it’s a safe bet that a lot of ppl would be using it alongside a PaaS like Heroku. I think it would be worthwhile, before release, to ensure that lux plays nicely with Heroku, and also document deployment to Heroku.
I know the goal isn’t specifically to make lux a Heroku solution, but 1) I think there’s a lot of overlap between the person who would be attracted to lux and the person who’s attracted to Heroku, and 2) something like Heroku is a perfect place to try out/play with this sort of solution.
I tried deploying something to Heroku last week and it wasn’t a “batteries-included” type experience (e.g., not as seamless as deploying a Rails app, for example), so it may require some minor tweaks to lux.
The text was updated successfully, but these errors were encountered:
Considering that lux is sort of a batteries-included api solution, it’s a safe bet that a lot of ppl would be using it alongside a PaaS like Heroku. I think it would be worthwhile, before release, to ensure that lux plays nicely with Heroku, and also document deployment to Heroku.
I know the goal isn’t specifically to make lux a Heroku solution, but 1) I think there’s a lot of overlap between the person who would be attracted to lux and the person who’s attracted to Heroku, and 2) something like Heroku is a perfect place to try out/play with this sort of solution.
I tried deploying something to Heroku last week and it wasn’t a “batteries-included” type experience (e.g., not as seamless as deploying a Rails app, for example), so it may require some minor tweaks to lux.
The text was updated successfully, but these errors were encountered: