@@ -78,7 +78,7 @@ \subsection{Introducing procer}
7878expected to be the one true init, poorly documented, not maintained, and definitely not
7979going to work for this manual. My only choice was to shave a yak and write my own.
8080
81- The end result is \shell {procer}, which lives in \file {examples /procer} and does
81+ The end result is \shell {procer}, which lives in \file {tools /procer} and does
8282most of what you need in a USPM. It works a lot like daemontools or minit, but
8383is much simpler, with these differences:
8484
@@ -129,11 +129,11 @@ \subsection{Introducing procer}
129129\subsection {Installing procer }
130130
131131Installing procer is very easy. It's a single little binary and it lives in
132- \file {examples /procer} in the Mongrel2 source. Here's how you'd install it
133- totally from scratch as if you hadn't even build Mongrel2 yet:
132+ \file {tools /procer} in the Mongrel2 source. Here's how you'd install it
133+ totally from scratch as if you hadn't even built Mongrel2 yet:
134134
135135\begin {code }{Install procer}
136- << d['/docs/manual/ inputs/install_procer.sh|pyg|l'] >>
136+ << d['inputs/install_procer.sh|pyg|l'] >>
137137\end {code }
138138
139139That's the entire install process, and now procer is in \file {/usr/local/bin}
@@ -169,7 +169,7 @@ \section{Step 1: The Deployment Area}
169169but feel free to change this up later if you find a better way.
170170
171171\begin {code }{Make Deployment Directories}
172- << d['/docs/manual/ inputs/make_deployment_directories.sh|pyg|l'] >>
172+ << d['inputs/make_deployment_directories.sh|pyg|l'] >>
173173\end {code }
174174
175175Hopefully, you're starting to see how you could easily automate this so that you don't
@@ -218,7 +218,7 @@ \section{Step 2: The mongrel2.org Configuration}
218218did with these commands:
219219
220220\begin {code }{Testing The Initial Configuration}
221- << d['/docs/manual/ inputs/testing_initial_config.sh|pyg|l'] >>
221+ << d['inputs/testing_initial_config.sh|pyg|l'] >>
222222\end {code }
223223
224224That's enough to make sure it runs, but you've got nothing running,
@@ -240,13 +240,13 @@ \section{Step 3: Setup procer}
240240and make sure procer can run everything:
241241
242242\begin {code }{Skeleton procer Setup}
243- << d['/docs/manual/ inputs/skeleton_procer_setup.sh|pyg|l'] >>
243+ << d['inputs/skeleton_procer_setup.sh|pyg|l'] >>
244244\end {code }
245245
246246With all of that, you can then try to run \shell {procer} to watch
247247it fail but still try to run everything:
248248
249- << d['/docs/manual/ inputs/run_procer_first_time.sh|pyg|l'] >>
249+ << d['inputs/run_procer_first_time.sh|pyg|l'] >>
250250
251251This is assuming that you are still in the \file {profiles} directory.
252252You should see the file \file {error.log} get created and
@@ -290,7 +290,7 @@ \section{Step 3: Setup procer}
290290Next up, let's get Mongrel2 running inside \shell {procer}:
291291
292292\begin {code }{procer Config For Mongrel2}
293- << d['/docs/manual/ inputs/procer_config_for_mongrel2.sh|pyg|l'] >>
293+ << d['inputs/procer_config_for_mongrel2.sh|pyg|l'] >>
294294\end {code }
295295
296296Obviously, you don't have to use a series of \shell {echo} commands to
@@ -303,7 +303,7 @@ \section{Step 3: Setup procer}
303303
304304
305305\begin {code }{Using procer To Run Mongrel2}
306- << d['/docs/manual/ inputs/using_procer_to_run_mongrel2.sh|pyg|l'] >>
306+ << d['inputs/using_procer_to_run_mongrel2.sh|pyg|l'] >>
307307\end {code }
308308
309309To watch \shell {procer} in action, try doing \shell {m2sh stop -db config.sqlite
@@ -322,7 +322,7 @@ \subsection{The Python Examples}
322322you will change \file {profiles/chat/run} to be like this:
323323
324324\begin {code }{Run Script For Chat Demo}
325- << d['/docs/manual/ inputs/procer_script_for_chat_demo.sh|pyg|l'] >>
325+ << d['inputs/procer_script_for_chat_demo.sh|pyg|l'] >>
326326\end {code }
327327
328328This little script uses some funky features you might not be familiar
@@ -345,13 +345,13 @@ \subsection{The Python Examples}
345345
346346When you run this manually, you should see something like this:
347347
348- << d['/docs/manual/ inputs/run_procer_chat_demo.sh|pyg|l'] >>
348+ << d['inputs/run_procer_chat_demo.sh|pyg|l'] >>
349349
350350After all that, you can then try out \shell {procer} again to see if it
351351properly runs the chat demo as well as mongrel2:
352352
353353\begin {code }{Running procer With Chat Demo}
354- << d['/docs/manual/ inputs/running_procer_with_chat_demo.sh|pyg|l'] >>
354+ << d['inputs/running_procer_with_chat_demo.sh|pyg|l'] >>
355355\end {code }
356356
357357If you go look at \file {profiles/error.log}, you'll see that \shell {procer}
@@ -365,17 +365,17 @@ \subsection{The Python Examples}
365365 \file {profiles/handlertest/run}
366366\hrule
367367
368- << d['/docs/manual/ inputs/procer_handlertest_run.sh|pyg|l'] >>
368+ << d['inputs/procer_handlertest_run.sh|pyg|l'] >>
369369
370370\file {profiles/mp3stream/run}
371371\hrule
372372
373- << d['/docs/manual/ inputs/procer_mp3stream_run.sh|pyg|l'] >>
373+ << d['inputs/procer_mp3stream_run.sh|pyg|l'] >>
374374
375375\file {profiles/web/run}
376376\hrule
377377
378- << d['/docs/manual/ inputs/procer_web_run.sh|pyg|l'] >>
378+ << d['inputs/procer_web_run.sh|pyg|l'] >>
379379\end {code }
380380
381381
@@ -385,7 +385,7 @@ \subsection{Testing The New Setup}
385385just need to see if things work. Here's some curl commands to try:
386386
387387\begin {code }{Testing With Curl}
388- << d['/docs/manual/ inputs/testing_procer_setup.sh|pyg|l'] >>
388+ << d['inputs/testing_procer_setup.sh|pyg|l'] >>
389389\end {code }
390390
391391
@@ -421,7 +421,7 @@ \section{Step 4: Static Content}
421421out the chat demo:
422422
423423\begin {code }{Setting Up Static Content}
424- << d['/docs/manual/ inputs/setting_up_static_content.sh|pyg|l'] >>
424+ << d['inputs/setting_up_static_content.sh|pyg|l'] >>
425425\end {code }
426426
427427If you get a good response then you should be able to go to
0 commit comments