That's all well and great, but it would be nice to have a brief overview of some of the more common admin functions, like deleting and renaming repos and projects, changing user passwords, adding/removing users to projects/groups, etc. Another thing is that there are functions that can be called from the command line that do not appear in the source code anywhere since they are some sort of dynamic ruby function, like User.find_by_login. A nice list of these would be mighty handy for people not so familiar with ruby. I would make some documentation myself, but my only dabblings in ruby so far are directly related to un-breaking gitorious, so I am definitely far from an expert.
Alex Forencich On May 6, 6:18 am, Marius Mårnes Mathiesen <[email protected]> wrote: > On Thu, May 5, 2011 at 8:00 PM, Jarrod Roberson > <[email protected]>wrote: > > > I am not a Ruby person, but it is about the only environment I don't know. > > Where should I go look other than the source, which I have tried, and still > > came up wanting? > > Rails is built on the MVC (Model-View-Controller) principle; the console > gives you access to (at least) the Model layer of the Rails app. > > This means you should be able to do anything the controllers do, except for > what has to do with request/response handling. So if you look at the source > code for the controllers (in app/controllers) you'll see code that you > should be able to interact with in the same way as the controllers do. > > Furthermore, Gitorious includes a large number of unit tests (see test/unit) > that excercise the same API, with descriptions of what's going on. So let's > say you want to find out how names of wiki pages in Gitorious are validated, > you pop up test/unit/page_test.rb. Toward the end of that find, you'll find > a few tests describing some valid and invalid page titles. > > Cheers, > - Marius -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
