I made a few changes to secure the defaults, and make it easier for folks to get started. I'll note them here since we probably should include them in our setup instructions, or set it by default:
* removed the Adobe sample neighborhood * add my own account (and rbowen, since I noticed he had registered) as admins of the /p/ and /u/ neighborhoods. I can add any other PPMC members as well. * disabled all the default admin & test users * changed http://allura-vm.apache.org/p/wiki/Home/ to include a link to registering a new project and listing the current projects I've noticed many issues that don't affect our deployment at SF since we use a custom theme and authentication plugin. Things like not being able to set your email address, project registration page layout, critical icons missing on project permission pages, etc. These do affect the default build of Allura, so of course they'd be good to ticket up and work on. -Dave On 2/12/13 3:26 PM, Stefano Invernizzi wrote: > The forge is now installed and running on the virtual machine! At the > moment, I changed only the port number in the configuration file, so that > it runs on port 80 instead of 8080. I don't know if something else is > supposed to be changed. Probably, we need to configure the forge so that it > uses LDAP, but I haven't tried to do so yet. Let me know if I should do it. > Finally, I had to change a small thing in the code, because I wasn't able > to run it. In the file Allura/allura/lib/custom_middleware.py I changed the > line in which mercurial is imported with: > from mercurial import hg > therefore, in the following one, I replaced mercurial.hg with hg. > > > 2013/2/10 Rich Bowen <[email protected]> > >> Yes. And as a pmc member there should be no question about that. >> >> -- >> Rich Bowen - [email protected] >> On Feb 9, 2013 3:31 AM, "Stefano Invernizzi" < >> [email protected]> >> wrote: >> >>> Thank you! Now I can ssh to the Virtual Machine, but I still don't have >>> root/sudo access, therefore I can't install the forge. Should I ask them >> to >>> give me this permission too? >>> >>> >>> 2013/2/7 Dave Brondsema <[email protected]> >>> >>>> Cool. Go to https://id.apache.org/ and login and add an ssh >> authorized >>>> key. >>>> >>>> Then create a new ticket at >>> https://issues.apache.org/jira/browse/INFRAasking >>>> for your account to have permission to the allura-vm.apache.org Since >>>> you're >>>> part of the Allura podling I wouldn't think any approvals or such would >>> be >>>> necessary. >>>> >>>> After that, you should be able to ssh to allura-vm.apache.org and >> start >>>> installing stuff. >>>> >>>> On 2/7/13 7:34 AM, Stefano Invernizzi wrote: >>>>> Yes, I think it is very interesting. How can I contribute to this? >>>> Should I >>>>> get privileges on the VM? It's not clear to me how to do it. >>>>> Thank you, >>>>> >>>>> Stefano Invernizzi >>>>> 2013/2/6 Rich Bowen <[email protected]> >>>>> >>>>>> >>>>>> On Feb 6, 2013, at 4:56 PM, Rich Bowen wrote: >>>>>> >>>>>>>> Is anyone interested in this? I think we'll have to ask ASF >>>>>> Infrastructure to >>>>>>>> grant permission to the VM. Only rbowen and I do currently. >>>>>> >>>>>> If you want to do this, you should start by requesting privileges on >>> our >>>>>> VM. You can do that at https://issues.apache.org/jira/browse/INFRA >>>>>> >>>>>> -- >>>>>> Rich Bowen >>>>>> [email protected] :: @rbowen >>>>>> [email protected] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Dave Brondsema : [email protected] >>>> http://www.brondsema.net : personal >>>> http://www.splike.com : programming >>>> <>< >>>> >>> >> > -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
