(Migrated) post installation script

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

Hello.

During the creation of deb package for ubuntu 14.04. I thought it can be
nice to include a post installation script that create the first zato
server with relative init scripts.

What do you think about?

Hello Giovanni,

El 30/04/14 20:44, Giovanni Colapinto ha escrit:

During the creation of deb package for ubuntu 14.04. I thought it can
be nice to include a post installation script that create the first
zato server with relative init scripts.

What do you think about?

I don’t think it would be a great idea: bear in mind that zato can be
used in multiple configuration scenarios, and that a particular
component (server, load-balancer, etc.) may or may not be needed in the
machine which zato is being installed into.

Also, at the moment redis and postgres are required but they are not
"hard" package dependencies (since they can be running in different
machines).
So even if we decided that having a quickstart running right after the
installation would be a good idea, we cannot know for sure if the
environment is prepared to handle it.

A different thing would be, for example, that the post-script phase
involved asking the user if she wants to install postgres and redis and
create a quickstart cluster all at once.
But having such a good documentation (the inital steps are very clear) I
don’t think this is necessary.

Regards,
Carles

On 04/30/2014 08:44 PM, Giovanni Colapinto wrote:

During the creation of deb package for ubuntu 14.04. I thought it can be
nice to include a post installation script that create the first zato
server with relative init scripts.

What do you think about?

I like the idea but it’s really what Carles says - there are far too
many deployment options to consider.

But the thought is certainly good - what would you say about making it a
part of specially crafted Vagrantfile?

This could be based on this one …

https://zato.io/download/osx/Vagrantfile

… and could include installing both a base package and all the
additional resources concluding with running ‘zato quickstart’ against
what has just been installed.

This would become even easier once Redis and Postgres become optional
dependencies …

https://github.com/zatosource/zato/issues/206
https://github.com/zatosource/zato/issues/207

… but it doesn’t necessarily need to wait for these tickets to be done.

On 04/30/2014 08:44 PM, Giovanni Colapinto wrote:

During the creation of deb package for ubuntu 14.04. I thought it can be
nice to include a post installation script that create the first zato
server with relative init scripts.

What do you think about?

I like the idea but it’s really what Carles says - there are far too
many deployment options to consider.

But the thought is certainly good - what would you say about making it a
part of specially crafted Vagrantfile?

This could be based on this one …

https://zato.io/download/osx/Vagrantfile

… and could include installing both a base package and all the
additional resources concluding with running ‘zato quickstart’ against
what has just been installed.

This would become even easier once Redis and Postgres become optional
dependencies …

https://github.com/zatosource/zato/issues/206
https://github.com/zatosource/zato/issues/207

… but it doesn’t necessarily need to wait for these tickets to be done.