Re: [Dolibarr-dev] Vagrant box

[Doursenaud , Raphaël]

I agree that the vagrant code should be maintained separately but I strongly advise you to not use submodules. They are a pain to maintain and get in the way very often.

2014-07-14 18:28 GMT+02:00 Sasa Ostrouska <address@hidden>:

On Mon, Jul 14, 2014 at 12:19 PM, Marcos García <address@hidden> wrote:

Hi all:

I don't know if many of you do use Dolibarr's vagrant box. If you don't, then I encourage you to use it.

Because Dolibarr usually has an old version of puphpet's box that may or not build correctly, I was thinking of extracting puphpet's code from dolibarr repository and create a new one under dolibarr organization. Then creating a submodule in dolibarr/dolibarr dev/vagrant folder so that every developer can get the latest dolibarr vagrant box without having to change the branch to "develop" and then returning back the previous one.

What do you think?

I never heard of vagrant, but a quick read seems to me that its an interesting thing.

Rgds
Saxa

 

Regards,

 

Marcos García

address@hidden

_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

--

Raphaël Doursenaud

Directeur technique (CTO)

Expert certifié en déploiement Google Apps

+33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10

http://gpcsolutions.fr

Technopole Hélioparc

2 avenue du Président Pierre Angot

64053 PAU CEDEX 9

SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921