(Migrated) Windows support

(This message has been automatically imported from the retired mailing list)

Hi

Only one question - as I read zato does not support windows.

Why is that - only because of gunicorn ?

And is it planned also to support windows ?

On 10/30/2013 01:35 PM, Ewald Geschwinde wrote:

Hi Ewald,

Only one question - as I read zato does not support windows.

Why is that - only because of gunicorn ?

And is it planned also to support windows ?

You know, these days with virtualization all around us the concept of
supporting a given platform is becoming more and more blurred so what is
supported and what is not needs to be clarified.

You can install Zato under Ubuntu with VirtualBox on Windows just like
any other application. Combine it with VB’s shared folders for
hot-deployment from command line and you can have a complete development
environment in under 1 hour.

Soon, I hope to be able to produce a docker.io instance that will give
you an already configured environment with a running cluster in 20 minutes.

So if you work in an environment when your workstations are all Windows
but servers are Linux you can easily use Zato right now and it with
docker.io this will become even easier.

If you’re thinking of running Windows servers, and coincidentally -
Windows workstations as well, then it’s a matter of properly allotting work.

If there’s someone who’d like to dig into the matter, I’m all open to
help in any way I can.

Note that Microsoft contributed an MSDN subscription to the project so
we have access to everything that is needed in order to help with
support for Windows

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2013-August/000067.html

But if there’s a Microsoft shop that runs Windows servers only and
they’d like to use Zato natively but without contributing the changes
needed, we need to talk about sponsoring the work and again, I’d be
happy to talk about it - my email is dsuch@zato.io

7 or even 5 years ago I would’ve treated it differently but in 2013
(almost 2014) you can easily obtain a development environment through
other means than porting an application so like I say - please use VB
for now and wait a bit for docker.io soon.

For production - this needs either a contributor or a sponsor.

What do you think about it?

On 10/30/2013 01:35 PM, Ewald Geschwinde wrote:

Hi Ewald,

Only one question - as I read zato does not support windows.

Why is that - only because of gunicorn ?

And is it planned also to support windows ?

You know, these days with virtualization all around us the concept of
supporting a given platform is becoming more and more blurred so what is
supported and what is not needs to be clarified.

You can install Zato under Ubuntu with VirtualBox on Windows just like
any other application. Combine it with VB’s shared folders for
hot-deployment from command line and you can have a complete development
environment in under 1 hour.

Soon, I hope to be able to produce a docker.io instance that will give
you an already configured environment with a running cluster in 20 minutes.

So if you work in an environment when your workstations are all Windows
but servers are Linux you can easily use Zato right now and it with
docker.io this will become even easier.

If you’re thinking of running Windows servers, and coincidentally -
Windows workstations as well, then it’s a matter of properly allotting work.

If there’s someone who’d like to dig into the matter, I’m all open to
help in any way I can.

Note that Microsoft contributed an MSDN subscription to the project so
we have access to everything that is needed in order to help with
support for Windows

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2013-August/000067.html

But if there’s a Microsoft shop that runs Windows servers only and
they’d like to use Zato natively but without contributing the changes
needed, we need to talk about sponsoring the work and again, I’d be
happy to talk about it - my email is dsuch@zato.io

7 or even 5 years ago I would’ve treated it differently but in 2013
(almost 2014) you can easily obtain a development environment through
other means than porting an application so like I say - please use VB
for now and wait a bit for docker.io soon.

For production - this needs either a contributor or a sponsor.

What do you think about it?