Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Our Onboarding Issues, Summarized #129

Closed
ianks opened this issue Aug 22, 2020 · 2 comments
Closed

Our Onboarding Issues, Summarized #129

ianks opened this issue Aug 22, 2020 · 2 comments

Comments

@ianks
Copy link

ianks commented Aug 22, 2020

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

  1. 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.

  2. Having before_start before_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

  3. 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

  4. 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! ❤️

@ioquatix
Copy link
Member

ioquatix commented Aug 22, 2020

  1. What is hard about falcon serve --bind http://localhost?

  2. 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.

  3. 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.

  4. 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.

Thanks for your feedback.

@ioquatix
Copy link
Member

By the way, as this is not an issue, I closed it. Please use the discussion forum for general feedback and support: https://github.com/socketry/falcon/discussions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants