1.0: publish the "hostmaster API" once it is frozen

Yes there is. See: http://chatroom.darren.oh.name/ for instance that is using http://drupal.org/project/api for http://drupal.org/project/chatroom module...

Oh, shoot. Sorry about that.

anarcat: where are you at with creation of API?

My recipe—

drush_make:
core = 6.x
api = 2
projects[] = drupal

projects[] = api
projects[] = job_queue
projects[] = ctools

Manually download grammar_parser and alter its .info file to 6.x instead of 7.x. Grr.

In the site's files directory, mkdir aegirsrc

git-clone -n git://git.aegirproject.org/hostmaster
git checkout hostmaster-0.4-beta1

git-clone -n git://git.aegirproject.org/provision
git checkout provision-0.4-beta1

Fill in the API reference config and run cron a few times... http://aegirapi.idealworld.org/

This only needs updating when a new release comes out, which would take a couple of minutes. If there's a demand for HEAD coverage simple to do the git pull thing as well.

Sorry for being late to the party on this issue, but I also put up an API site for the Aegir code at api.ergonlogic.net. I also included drupal core, drush, drush_make, ubercart and uc_hosting, since these are all required to make a useful commercial platform out of Aegir. I'd be happy to maintain one for just the Aegir code though, if there's interest in that.

I've been sporadically updating this manually, but will write up a simple script that does a "git pull" on the aegir projects, and "drush dl" to update those hosted on d.o. I dumped all of this into a common project and branch, as API.module doesn't appear to generate links across branches. Also, API doesn't look great under eldir, so some theming tweaks are probably necessary.

No, it's cos I did it on another site, cloned it and didn't check and find out that the path to the files in the API module config pointed to the old site. Then I deleted the old site. It's working now, and the recipe is sound.

Thanks to ergonlogic, I thought someone would have got there first. One odd bug, which doesn't seem to apply to most searches, but http://api.ergonlogic.net/api/search/6/hostmaster.profile is 403 forbidden?

Comparing our two sites, I think it's much better with the other bits you mention (especially drush and drush_make) but it would make sense for the home page to be the equivalent of http://aegirapi.idealworld.org/api/Aegir/0.4-beta1 or better yet write some overview text that points out hostmaster, provision, anything else that needs pointing out and shove it up in a page.

The only other thing I'm slightly concerned about is that after putting everything in one branch, what happens when a new version of aegir comes out? Or would the site only track HEAD or only show the latest proper release?

It would be good to update http://community.aegirproject.org/node/79 soon as that was what frustrated me into action and it's a half hour job to get at least something up once the hosting's been determined.

subscribing

To anarcat's points:

1. I've removed Drupal core (along with UC for the moment). I think devel links directly to api.drupal.org, but I haven't figured out how to (or if it's even possible) using API.module.
2. I don't know about "sucks", but the eldir theme does need some work. I just upgraded to beta2, and copied the eldir theme from there to the API site. So, it's pretty close to HEAD.
3. it's could be api.aegirproject.org ;) I've "add[ed] the alias on [my] side [so let's] make sure adrian points the domain there"

As for keeping the code updated, I'm calling drush make via cron with the attached makefile.

... call drush_make repeatedly, what does it do? it overwrites existing code?

drush_make does indeed overwrite existing code. From running it with --debug, it looks like it executes 'cp -Rf' from a temporary directory. I just realized that, while this will keep existing files updated, and add new files, it won't purge files removed from the repo. So, I could run 'rm -rf' on the directories in question, before rebuilding them with drush_make, or write a script that calls git pull. I'll give it some further thought.

Do we really need the drush_make API?

I guess not, so I've removed it :) Drush Make is just so brilliant... However, there are starting to be some contributed modules targeting Aegir, such are uc_hosting and aegir_feeds. Is there interest in hosting those on this API site, maybe under 'contrib' or something?

BTW, this started off as a personal API site, so I had included a bunch more stuff I'm interested in too. Once api.aegirproject.org points there, I'll rebuild api.ergonlogic.net separately, and include those contrib modules, among others.

I think including contrib is a really good idea mainly because it provides other people with a starting point for developing aegir modules.

It's using a pretty recent version of Eldir... At one point I had a block in the left sidebar, but after removing it, the region was still appearing, even when empty. I double-checked that it was indeed empty, then cleared the cache. This seems to have fixed it.