Hi Till,
> On Jun 28, 2016, at 7:26 PM, Till Wegmüller wrote:
>
>
> On 28.06.2016 17:50, Adam Števko wrote:
>> Yes, I did and got vagrant working as separate ruby gems. The main problem
>> with this approach is that packaging every needed gem is too much work and
>> maintenance cost is high.
On 28.06.2016 17:50, Adam Števko wrote:
Yes, I did and got vagrant working as separate ruby gems. The main problem with
this approach is that packaging every needed gem is too much work and
maintenance cost is high. Also, Vagrant webpage doesn’t recommend using
gem-based deployment of Vagrant
Hi Tim,
> On Jun 23, 2016, at 8:53 PM, Tim Mooney wrote:
>
>
>> Hello,
>>
>> I prepared OpenIndiana vagrant box from the latest hipster 2016.04 snapshot.
>> This is targeted mostly at users and developers, who do not run OI as their
>> main platform, but use VirtualBox for developing software
Hello,
I prepared OpenIndiana vagrant box from the latest hipster 2016.04 snapshot.
This is targeted mostly at users and developers, who do not run OI as their
main platform, but use VirtualBox for developing software or doing illumos
builds on OpenIndiana. This box is created from text install
Hello,
I prepared OpenIndiana vagrant box from the latest hipster 2016.04 snapshot.
This is targeted mostly at users and developers, who do not run OI as their
main platform, but use VirtualBox for developing software or doing illumos
builds on OpenIndiana. This box is created from text install
