VVV 4

[tomjn]

The plan for VVV 4 is to build on top of VVV 3 now that we can update the base box easily. When the VVV4 box gets built, we provision PHP/MariaDB/etc, so that when a user does their first provision, only the sites and tools need to be setup.

This should take a lot of the time out of setting things up, as well as eliminating a source of support burden so we can focus on making things nicer.

Additionally, if PHP or DB provisioning ever breaks, only the build server breaks, everybody carries on using the last built box

This also means we can eliminate a number of shared folders and folders on the filesystem, e.g. the provision and config folders. Only database, logs, www, and certificates might be needed, and those could be consolidated further ( perhaps into a subfolder? )

[ghost]

does this mean, that some software would eventually get pre-install inside the box rather than getting provisioned, that would make things faster

[tomjn]

yes, everything except the sites and certificats would be ready out of the box

On Tue, May 21, 2019 at 5:01 PM Benjamin Lu notifications@github.com wrote:

does this mean, that some software would eventually get pre-install inside the box rather than getting provisioned, that would make things faster

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1785?email_source=notifications&email_token=AAAOLZY4ABSGW3WNFCP2GQTPWQMFXA5CNFSM4HLNEOXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4MF5A#issuecomment-494453492, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOLZ7LTTVORKCS6YGFKQ3PWQMFXANCNFSM4HLNEOXA .

[IronGhost63]

I will no longer have "it's provisioning" excuse soon.