forrest run - bad port

[Ian Blizard <bu...@samsungcontact.com>]

Used forrest run on a new seeded project:

-(buzz@carling:3)-(38 files:560K@buzz)-(0 jobs)-(17:01)-
-(~:$)-> wget http://localhost:8888/
--17:02:38--  http://localhost:8888/
           => `index.html'
Resolving localhost... done.
Connecting to localhost[127.0.0.1]:8888... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://localhost:8888index.html [following]
http://localhost:8888index.html: Bad port number.

-Buzz

Jeff Turner wrote:

>On Fri, Nov 08, 2002 at 09:54:38AM -0500, Rodent of Unusual Size wrote:
>  
>
>>i don't have a handle on the 'forrest run' bit yet
>>    
>>
>
>It goes something like:
>
> - type 'forrest run'
> - point your browser at http://localhost:8888/.  You should see the site
>   rendered
> - Delete build/webapps/content/xdocs and symlink it to
>   src/documentation/content/xdocs
> - Edit away in src/documentation/content/xdocs, and after every change,
>   see the updates rendered immediately in the browser
>
>  
>
>>, but it just occurred to me: with all the fancy only-if-changed
>>technology we've got in mae (n/a) and ant.. why does 'forrest site'
>>actually rebuild the entire site rather than just the bits that have
>>changed?
>>    
>>
>
>It should really.  Not so easy though, because there's no simple 1-1
>mapping between source files and result. Eg, index.html should be rebuilt
>if {index.xml, book.xml, tabs.xml} changes, and this is just one of many
>rules in the sitemap.
>
>Cocoon has caching.. the trick is to get it to work in command-line mode.
>
>
>--Jeff
>
>  
>
>>it's getting very time-consuming..
>>    
>>
>
>
>  
>

Re: forrest run - bad port

[Jeff Turner <je...@apache.org>]

On Fri, Nov 08, 2002 at 05:04:21PM +0000, Ian Blizard wrote:
> Used forrest run on a new seeded project:
> 
> -(buzz@carling:3)-(38 files:560K@buzz)-(0 jobs)-(17:01)-
> -(~:$)-> wget http://localhost:8888/
> --17:02:38--  http://localhost:8888/
>           => `index.html'
> Resolving localhost... done.
> Connecting to localhost[127.0.0.1]:8888... connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location: http://localhost:8888index.html [following]
> http://localhost:8888index.html: Bad port number.


I think I've fixed it.  There were similar problems when running
build/webapp in Tomcat.

jeff@expresso:~$ wget http://localhost:8888/
--18:02:10--  http://localhost:8888/
           => `index.html'
Resolving localhost... done.
Connecting to localhost[127.0.0.1]:8888... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://localhost:8888/index.html [following]
--18:02:12--  http://localhost:8888/index.html
           => `index.html'
Connecting to localhost[127.0.0.1]:8888... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [ <=>                                 ] 9,226          4.40M/s             

18:02:16 (4.40 MB/s) - `index.html' saved [9226]


--Jeff

> -Buzz