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
A month or two ago, I’ll explain our journey attempting to migrate to Falcon, and the issues we ran into.
First off, some info about our env:
Framework: Hanami
Ruby 2.6
Using Guard in development
Currently using Iodine for our app server
The issues we had
It should be way easier to turn off SSL. We don’t use it in dev, and it proved to be too big of a burden to implement since we would have to make updates to webpack etc. Also, we don’t care about having it, nor http2 in production since we use old balancers in front of our deployment. Turning it off should be easier.
Having before_startbefore_fork and after_fork would have been super helpful, since we already have tooling which supports this. Using the preload.rb was confusing and didn’t really work well for us
The guard-falcon gem did not work well for us, it would either a) not reload code or b) reload the entire app, gems and all. So it either didn’t work or was too slow, not there was no perceivable over using something like guard-process
This missing changelog issue made us hesitant that we could properly upgrade in a sustainable way
Unfortunately, we decided not to being using Falcon, but plan to give it another shot in the future! ❤️
The text was updated successfully, but these errors were encountered:
What is hard about falcon serve --bind http://localhost?
Falcon doesn't have a fork model like any other server (which is so complicated that requires hooks, which I think is crazy). Your config.ru will be loaded in the child process OR a thread, so you just put the code you need in that file and that file only.
guard in general is pretty much unmaintained at this point. guard-falcon is a best effort to support it but obviously as a single developer, it's impossible to support the entire eco-system while maintaining a full time job and a family. If you have specific issues, feel free to contribute back.
A change log is a good idea. Unfortunately, given time constraints, I'd be generating it from the git log. So, that is what I suggest you refer to.
A month or two ago, I’ll explain our journey attempting to migrate to Falcon, and the issues we ran into.
First off, some info about our env:
The issues we had
It should be way easier to turn off SSL. We don’t use it in dev, and it proved to be too big of a burden to implement since we would have to make updates to webpack etc. Also, we don’t care about having it, nor http2 in production since we use old balancers in front of our deployment. Turning it off should be easier.
Having
before_start
before_fork
andafter_fork
would have been super helpful, since we already have tooling which supports this. Using the preload.rb was confusing and didn’t really work well for usThe guard-falcon gem did not work well for us, it would either a) not reload code or b) reload the entire app, gems and all. So it either didn’t work or was too slow, not there was no perceivable over using something like guard-process
This missing changelog issue made us hesitant that we could properly upgrade in a sustainable way
Unfortunately, we decided not to being using Falcon, but plan to give it another shot in the future! ❤️
The text was updated successfully, but these errors were encountered: