I will see if I have rights to fix that when I get home

Sent from my iPhone

> On Jun 21, 2014, at 4:33 PM, Matt Sicker <boa...@gmail.com> wrote:
> 
> I don't appear to have wiki edit permissions.
> 
> 
>> On 20 June 2014 17:50, Remko Popma <remko.po...@gmail.com> wrote:
>> I'd  like to try this, so I'm looking forward to such a wiki page!
>> 
>> Ralph, we could add "Vagrant*" to the excludes in the assembly. That would 
>> make sense to me as we're already excluding IDE files like .project etc 
>> there. I do agree that a wiki page would be a better "home" for this file, 
>> again similar to our policy not to commit IDE files. 
>> 
>> Sent from my iPhone
>> 
>>> On 2014/06/21, at 2:29, Matt Sicker <boa...@gmail.com> wrote:
>>> 
>>> And for other VMs, well, there'd have to be different configurations. 
>>> There's a way to configure multiple VMs in a single Vagrantfile (e.g., for 
>>> making a cluster of VMs), so I'll take a look into that as well.
>>> 
>>> 
>>>> On 20 June 2014 12:29, Matt Sicker <boa...@gmail.com> wrote:
>>>> It's in the root directory (i.e., /vagrant, next to /var, /home, /etc). 
>>>> It's easiest to set up in the root of your project because it 
>>>> automatically shares that directory in the VM. Otherwise, you need to add 
>>>> more shared directories and such.
>>>> 
>>>> So yes, if you navigate to /vagrant (not /home/vagrant), you'll see all 
>>>> the sources.
>>>> 
>>>> I'll write up some wiki docs this weekend to explain more about it. Good 
>>>> idea.
>>>> 
>>>> 
>>>>> On 20 June 2014 12:00, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>>>>> I should also add that the wiki is the perfect place for this because you 
>>>>> can also document how to install vagrant and virtualbox as well as how to 
>>>>> start, stop and use the VM.
>>>>> 
>>>>> Ralph
>>>>> 
>>>>>> On Jun 20, 2014, at 9:51 AM, Ralph Goers <ralph.go...@dslextreme.com> 
>>>>>> wrote:
>>>>>> 
>>>>>> OK, so this builds an ubuntu VM. What if I want a Windows VM, or a 
>>>>>> CentOS or Redhat VM?  I am just having a problem understanding why this 
>>>>>> file would be in the root of the project.  I could understand if we had 
>>>>>> a tools sub-project or something outside of the project. I just don’t 
>>>>>> know why this would be in the source that we release.
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>> 
>>>>>>> On Jun 20, 2014, at 7:55 AM, Matt Sicker <boa...@gmail.com> wrote:
>>>>>>> 
>>>>>>> It's a quick and easy way for any developer to get up and running with 
>>>>>>> a VM for testing. You just run "vagrant up", then "vagrant ssh", then 
>>>>>>> everything from the project is available in the /vagrant directory in 
>>>>>>> the VM. You can compile, run tests, etc.
>>>>>>> 
>>>>>>> 
>>>>>>>> On 20 June 2014 09:23, Ralph Goers <rgo...@apache.org> wrote:
>>>>>>>> I don't really understand.  I use VMware fusion and don't need this 
>>>>>>>> file. Now matter what OS I want.  Why does it need to be part of the 
>>>>>>>> project?
>>>>>>>> 
>>>>>>>> Ralph
>>>>>>>> 
>>>>>>>>> On Jun 20, 2014, at 6:48 AM, Matt Sicker <boa...@gmail.com> wrote:
>>>>>>>>> 
>>>>>>>>> I added that. See
>>>>>>>>> http://www.vagrantup.com/
>>>>>>>>> 
>>>>>>>>> It's for creating a Linux VM to test log4j in since we all use 
>>>>>>>>> Windows or Mac.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On 19 June 2014 22:58, Ralph Goers <ralph.go...@dslextreme.com> 
>>>>>>>>>> wrote:
>>>>>>>>>> What is the file “Vagrantfile” checked in to the root of trunk for?  
>>>>>>>>>> Was it committed by accident?
>>>>>>>>>> 
>>>>>>>>>> Ralph
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
>>>>>>>>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> -- 
>>>>>>>>> Matt Sicker <boa...@gmail.com>
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> Matt Sicker <boa...@gmail.com>
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Matt Sicker <boa...@gmail.com>
>>> 
>>> 
>>> 
>>> -- 
>>> Matt Sicker <boa...@gmail.com>
> 
> 
> 
> -- 
> Matt Sicker <boa...@gmail.com>

Reply via email to