fix some POD links
Sawyer X
8 years ago
| 28 | 28 | While developing your application, it is often handy to have the server |
| 29 | 29 | automatically reload your application when changes are made. There are |
| 30 | 30 | two recommended ways of handling this with Dancer: using C< plackup -r > |
| 31 | and L< Plack::Loader::Shotgun >. Both have their advantages and disadvantages | |
| 31 | and L<Plack::Loader::Shotgun>. Both have their advantages and disadvantages | |
| 32 | 32 | (which will be explained below). |
| 33 | 33 | |
| 34 | 34 | Regardless of the method you use, it is B< not > recommended that you |
| 51 | 51 | specified directories. If the timestamp of any files in a watched |
| 52 | 52 | directory changes, the application is recompiled and reloaded. |
| 53 | 53 | |
| 54 | See the L< plackup > docs for more information on the C< -r > and C< -R > | |
| 54 | See the L<plackup> docs for more information on the C< -r > and C< -R > | |
| 55 | 55 | options. |
| 56 | 56 | |
| 57 | 57 | =head3 Auto reloading with plackup and Shotgun |
| 60 | 60 | you, be it for the way it looks for changes, or because there are many |
| 61 | 61 | directories you need to monitor, or you want to reload the application any |
| 62 | 62 | time one of the modules in Perl's F< lib/ > path changes. |
| 63 | L< Plack::Loader::Shotgun > makes this easy by recompiling the application | |
| 63 | L<Plack::Loader::Shotgun> makes this easy by recompiling the application | |
| 64 | 64 | on every request. |
| 65 | 65 | |
| 66 | 66 | To use Shotgun, specify it using the loader argument to C< plackup (-L) >: |