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

Jump to bottom

Fix links to new repo. From timcharper to sporkrb #155

Merged
merged 1 commit into from Nov 1, 2011
Merged

Fix links to new repo. From timcharper to sporkrb #155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.rdoc
View file
Open in desktop
@@ -1,10 +1,10 @@
= Spork = Spork


* Repository: http://github.com/timcharper/spork * Repository: http://github.com/sporkrb/spork
* Issues: http://github.com/timcharper/spork/issues * Issues: http://github.com/sporkrb/spork/issues
* Changes: http://github.com/timcharper/spork/blob/master/History.txt * Changes: http://github.com/sporkrb/spork/blob/master/History.txt
* Mailing list: http://groups.google.com/group/sporkgem * Mailing list: http://groups.google.com/group/sporkgem
* Wiki: http://wiki.github.com/timcharper/spork * Wiki: http://wiki.github.com/sporkrb/spork


== SYNOPSIS: == SYNOPSIS:


Expand Down Expand Up @@ -70,7 +70,7 @@ It will output a lot of stuff. At the top you'll find a summary of all project


Some project changes will require a spork restart, and you shouldn't expect them to not (IE: modifying your project gem dependencies or core application config). Any file that is loaded during Spork start-up will be cached until Spork is restarted. You can restart spork by sending a USR2 signal to the server process. This could be automated with a gem such as Kicker (https://github.com/alloy/kicker). Since a native hook is required for each operating system to efficiently watch for filesystem changes, automatic restarting has not been built into Spork. Some project changes will require a spork restart, and you shouldn't expect them to not (IE: modifying your project gem dependencies or core application config). Any file that is loaded during Spork start-up will be cached until Spork is restarted. You can restart spork by sending a USR2 signal to the server process. This could be automated with a gem such as Kicker (https://github.com/alloy/kicker). Since a native hook is required for each operating system to efficiently watch for filesystem changes, automatic restarting has not been built into Spork.


You may find this wiki page useful for common ways to battle a variety of common pre-loading issues: http://github.com/timcharper/spork/wiki/Spork.trap_method-Jujutsu You may find this wiki page useful for common ways to battle a variety of common pre-loading issues: http://github.com/sporkrb/spork/wiki/Spork.trap_method-Jujutsu


== Running specs over Spork == Running specs over Spork


Expand Down Expand Up @@ -120,7 +120,7 @@ Essentially:


== Some potential issues and ways to overcome them: == Some potential issues and ways to overcome them:


See http://wiki.github.com/timcharper/spork/troubleshooting See http://wiki.github.com/sporkrb/spork/troubleshooting


== Kudos to == Kudos to


Expand Down