Open Exterm1nate opened 2 months ago
Yep that's a fair point, and a fair request. I'll think about the best way forward.
Part of the design motivation is to ensure we don't accidentally leak shared memory into the configurations, but it's pretty inconvenient. Those configuration blocks are actually re-evaluated every time the child is forked/executed to ensure isolation and predictable behaviour.
After upgrading Falcon from 0.43 to 0.44 this configuration:
breaks server boot with a very strange error:
After some investigation I found that configuration block
rack {}
doesn't support Ruby core methods anymore, e.g.puts
,Integer()
, etc.Changing
count Integer(2)
tocount 2
fixes the server boot and works well.Also it is rather strange that block
endpoint {}
insiderack {}
do support all these methods, that are breaking therack {}
itself. For example, you can useInteger()
inside.I suppose this should be fixed or at least mentioned in docs.