Hello Mark,<div><br></div><div>You can disable the Configure and Halo functionality but I think it is better to prepare a Smalltalk runtime image without these development packages loaded. I did something similar for my ec2demo Seaside app. See <a href="http://blog.doit.st/2010/09/08/creating-a-seaside-runtime-image-with-pharo/">http://blog.doit.st/2010/09/08/creating-a-seaside-runtime-image-with-pharo/</a></div>
<div><br></div><div><a href="http://blog.doit.st/2010/09/08/creating-a-seaside-runtime-image-with-pharo/"></a>Jan. </div><div><br><div class="gmail_quote">On Tue, Aug 31, 2010 at 10:15 PM, Mark Carter <span dir="ltr">&lt;<a href="mailto:mcturra2000@yahoo.co.uk">mcturra2000@yahoo.co.uk</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I&#39;m new to Smalltalk and Seaside.<br>
<br>
I started Seaside 3.0 all-in-one for Windows. I started the adapter from the<br>
control panel and put it in deployment mode. However, if I point my browser to<br>
    <a href="http://localhost:8080" target="_blank">http://localhost:8080</a><br>
the menu strip down the bottom (the one with Configure and Halos on it) is still<br>
visible. What gives? That&#39;s worrying. Isn&#39;t that massively insecure? I&#39;ve<br>
Googled around for deploying Seaside, but I can&#39;t seem to find a straight answer<br>
about what I&#39;m supposed to do about it.<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Jan van de Sandt<br>gsm: +31 (0)6 3039 5998<br>
</div>