github-migration/guard-rails
1
0
Fork 0
Code Issues 6 Pull Requests 2 Packages Projects Releases Wiki Activity

Rails server should be (re)started on reload? #6

New Issue
Closed
opened 2011-09-15 03:36:16 +00:00 by tehpeh · 1 comment
tehpeh commented 2011-09-15 03:36:16 +00:00 (Migrated from github.com)
Copy Link

Hi John,

Just thinking that the rails server should be started and restarted on guard's reload command rather than run_all?

This would mean when you reload guard with r+enter it will restart the server, but just hitting enter will not do anything.

What do you think?

For me that makes sense if I also run rspec and cucumber in my guardfile, so enter runs all the tests, and r+enter reloads the server and spork.

Hi John, Just thinking that the rails server should be started and restarted on guard's reload command rather than run_all? This would mean when you reload guard with r+enter it will restart the server, but just hitting enter will not do anything. What do you think? For me that makes sense if I also run rspec and cucumber in my guardfile, so enter runs all the tests, and r+enter reloads the server and spork.
johnbintz commented 2011-09-15 13:52:39 +00:00 (Migrated from github.com)
Copy Link

For me, having Rails restart on run_all means that I can change some file that Rails doesn't autoload, like something in lib or config, and Rails restarts without me needing to do a thing. Reloading the Guardfile is another place that a Rails reload may make sense, too, especially now that I'm playing with different servers for Rails development. For my normal workflow, though, run_all makes more sense than reload.

Whoever gets to adding that to guard-rails first wins. :)

For me, having Rails restart on `run_all` means that I can change some file that Rails doesn't autoload, like something in `lib` or `config`, and Rails restarts without me needing to do a thing. Reloading the Guardfile is another place that a Rails reload may make sense, too, especially now that I'm playing with different servers for Rails development. For my normal workflow, though, `run_all` makes more sense than `reload`. Whoever gets to adding that to guard-rails first wins. :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: github-migration/guard-rails#6
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?