OK. I understand. I thought that was already a team working with the 
documentation, translation and so on. I can't promise you that it will be 
something, but I will try as long I have time to go for it.

Can I use your book as reference? Where I find the new version from 
documentation? Already on git?

Best

Gabriel



Am Donnerstag, 23. Januar 2014 17:05:14 UTC+1 schrieb Mitchell Hashimoto:
>
> Gabriel,
>
> I'd love to improve the way that the configuration options are presented. 
> I agree it can be much better. With the last release of Vagrant, and in git 
> now, the docs are much better, but the organization hasn't changed at all 
> and I think, like you said, there is room to improve there.
>
> Unfortunately, I don't have the bandwidth [in time] to do it right now, 
> but I'd be happy to look at a proof of concept and give feedback. 
> Ultimately, if I got a pull request to do something like this I'd be super 
> excited.
>
> Best,
> Mitchell
>
>
> On Thu, Jan 23, 2014 at 6:03 AM, Gabriel Stein 
> <[email protected]<javascript:>
> > wrote:
>
>> Hi all,
>>
>> Well, I'm new here, I must confess that I didn't read all the threads 
>> from the group, but I just want to ask something, but please don't get me 
>> wrong. If are already some thread with the same subject, will be nice to 
>> get some reference back.
>>
>>  I will explain my situation: 
>>
>> - I'm actually working on a migration from Virtualbox to VMware as 
>> provider, since we are using Windows and NFS to share folders and the 
>> performance is quite unacceptable - and searching for solutions I find 
>> this: 
>> http://puppetlabs.com/presentations/multi-provider-vagrant-aws-vmware-and-more
>>
>> -  Well, the video is true, comparing Virtualbox and even VMware Player 
>> without Vagrant you already perceive that VMware is really faster(please, 
>> I'm not discussing VMware X Virtualbox)
>>
>> - And in the end of this migration I installed the last version from 
>> Vagrant, 1.4.3 and I decided to test/implement version "2" from config.
>>
>>
>> The thing which I didn't like it's the documentation from Vagrant. Yes, 
>> the things are there, but I feel that will be better a kind of page with 
>> the syntax cheat , splitting between version(1 | 2), provider(Virtualbox | 
>> VMware) and so on.
>>
>> For example, I have a search page, which I check the checkbox "Provider: 
>> VMware-Fusion", I can search for the syntax which I can use on Vagrantfile 
>> with VMware-Fusion, or if I want to search about vm.customize I will have 
>> references to version "2" too.
>>
>> Are there someone working on that? Was already a subject here? Who can 
>> help with this question? There is a way to help?
>>
>> And please, I don't want to get anyone offended, but after two days 
>> hacking the configurations from Vagrant(yes, that was awesome!), I think 
>> that are much more people with the same questions. Even a plain text file 
>> can help others with this syntax "cheat".
>>
>> I'm already writing some documentation about this migration, but probably 
>> are better ways to do that or at least some official Vagrant Best Practices.
>>
>> Well thanks for the work with Vagrant!
>>
>> Best Regards,
>>
>> Gabriel
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to