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
Add reload!
to lotus console
#46
Conversation
opts[:applications] = 'test/fixtures/microservices/config/applications' | ||
console.stub(:engine, @engine) { console.start } | ||
|
||
@main.verify |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also @engine.verify
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah right!
@davidcelis Thanks for this PR. Because we don't have a proper web reloading process (see #24 ), I'm wondering how this works, and if it does, do you think it may be a viable solution for the other features? EDIT: I'm not wondering how this works w/ Ruby, but if this simple trick resolves all the complexity of Lotus.. ✨ 💯 ✨ |
I think that Rack::Reloader is still gonna be the best bet for reloading the web app as code changes in development, since |
This patch adds a `reload!` method during `lotus console` sessions, much like what is available during a `rails console` session. `reload!` will simply call `Kernel.exec $0` to re-execute the running process after outputting a message that it is doing so. Signed-off-by: David Celis <me@davidcel.is>
@davidcelis Alright, merging this for now. Thanks! |
Add `reload!` to `lotus console`
This patch adds a
reload!
method duringlotus console
sessions, muchlike what is available during a
rails console
session.reload!
willsimply call
Kernel.exec $0
to re-execute the running process afteroutputting a message that it is doing so.
Signed-off-by: David Celis me@davidcel.is