On 5/14/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote:
We won't be able to use Atlassian's public server - our stuff is just too heavy duty.
Is there a particular aspect of "heavy duty" that causes more problems: Too many pages or too many hits? If the size of a space matters, it might make sense to use multiple spaces. I'm finding that larger spaces are harder to export. I haven't been able to export our current space to HTML, but I have had some luck with smaller subsets. If we can get an export working, then we can start posting HTML to the site and funnel visitors to the static pages. The link to the wiki, we can keep with the "How to Help" and "Nightly Build" material. Out of sight, out of mind. But, we do need to fish or cut bait. Right now, it doesn't look like the current configuration is going to work for us, simply because we can't get an export of the space. Regardless, I think I should ask Jeff Turner for a license that we can use for now, before the evaluation expires.
Contegix (not Contegrix :P) might be interested to help, but I imagine they would probably feel more interested if they were in a position that was more than just an emergency/temporary storage location (eg: official hosting provider for Struts - which I know is a much bigger issue). I'll ask Matthew Porter next week what his thoughts are.
Well, there's yet-another ASF Confluence thread open on infrastructure right now, where someone is offering to donate a dedicated machine. No one has screamed "stop" yet. There's a test instance running now on an ASF host name now, where they are trying to run Confluence and server statically auto exported HTML. But, there's no way to tell if this will work out or not, and how temporary any other arrangements might be. The idea of someone being the official hosting provider of a single ASF project is probably a non-starter. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
