Hello Luis
Yes, you are right, however it is far from having "Infraestructure as
code", what I mean is having health on a way on working as Continues
Delivery and Continues Integration, considering that implementing ERP
requires more than just install
What do you think about that?
Best regards
2016-04-05 12:05 GMT-05:00 Luis Falcon <fal...@gnu.org>:
> Hi Carlos !
> On Tue, 5 Apr 2016 10:55:29 -0500
> Carlos Eduardo Sotelo Pinto <carlos.sotelo.pi...@gmail.com> wrote:
>
> > Dear Coders
> >
> > I would like to propose a discussion about Health deployment. I mean,
> > work on the Vagrant and install script
> >
> > Each time that I need to upgrade versions or deploy with extra
> > modules I need to do too much losing my custom code, for example, I
> > was working on 2.8 version, and build extra modules, in order to
> > deploy on testing server, I had had to install the server, but with
> > extra customization cause on new requirements and custom modules,
> > after an upgrade, I have lost my custom changes and modules, I must
> > do a copy paste and update vagrant file.
> >
> When using the standard GNU Health installation, the command
> "gnuhealth-control update" will update Tryton and GNU Health, and
> relink your custom modules (under the "local" directory).
>
> This applies for current deployment updates. WHen you want to upgrade
> the GNU Health from one version to the other, then it's done manually.
> This makes sense, since it involves change on API.
>
> Bests,
> Luis
>
>
--
Carlos Eduardo Sotelo Pinto
Senior Software Analyst Developer
Claro RPC +51983265994 | MOV RPM( # ) +51 966110066
GTalk: carlos.sotelo.pi...@gmail.com | Skype: csotelop
GNULinux RU #379182 | GNULinux RM #277661
No availability between 08:30 and 18:00, I will answer as soon as posible
Please consider the environment before printing this email
Join the campaign at http://thinkBeforePrinting.org
