[Seaside] ZincStaticServerAdaptor starts with different port

[Sven Van Caekenberghe]

WAServerManager class>>#startUp sends #startUp to all registered adaptors

If you saved an image with a running adaptor in it, it will be restarted when the image comes up. This is cool and works fine, but I find it better suited to development than deployment. When deploying I make sure there are no servers of any kind running, and then start them manually and explicitly in a startup script.

So if something starts up automagically, you must have done something.

BTW, 80 is a restricted port, but I guess you already know that.

> On 10 May 2020, at 00:14, Esteban Maringolo <emaringolo at gmail.com> wrote:
> 
> Hi,
> 
> I have a ZnZincStaticServerAdaptor, that after quitting the image and
> starting it again starts in a different port.
> 
> So I did:
> WAServerManager default adaptors do: [ :each | WAServerManager default
> unregister: each ].
> (ZnZincStaticServerAdaptor startOn: 8000 andServeFilesFrom:
> (FileLocator  imageDirectory / 'static' ) asFileReference).
> 
> And get the server running in the port 8000. [see zn8000.png]
> 
> But after restarting the image, it is running in the port 80. [see zn80.png]
> 
> Why is it so?
> 
> Regards,
> <zn8000.png><zn80.png>_______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside