I've actually put a lot of thought into this, particularly as we recently
moved servers and it got me to thinking about the administration and scaling
side of this kind of massive setup.

I would love to see a hosted Habari offering, but I'm not sure we're ready
for that yet. There's still so much day-to-day flux in the SVN codebase and
so much outdated / non-working stuff in the latest 0.5 release, that I think
maintaining any kind of large hosted system would be too complex and
time-consuming currently.

Add to that a lack of themes, which should hopefully start to become less of
an issue after we address some themeing concurns in 0.7, and a "rough"
multi-site capability (to say the least) and it seems like we're a little
too early entering the game on all sides.

Personally, I think we would only be able to offer a poor showing if we were
to pursue something like this at present. I would rather wait a few more
versions (or possibly for a 1.0) and really knock peoples socks off then
than toss out a ho-hum service now.

If anyone has other ideas or opinions, please chime in...

On Tue, Nov 11, 2008 at 11:10 AM, Benjamin Hutchins <[EMAIL PROTECTED]>wrote:

>
> As many people know Wordpress has their Wordpress.com service where
> you can get a free blog hosted via their free service. Where is
> Habari.com (this domain is registered, it is a figure of speech)?
>
> I'd like to propose an attempt to start a hosting service for free
> content hosting using Habari. The restrictions may have to be talked
> about, so we can do so here, but I myself would be willing to host
> these users. I currently have multiple servers I pay an overpriced
> hosting bill for to have them hosted at my local datacenter. I have
> enough resources to maintain hosting for multiple hundreds of Habari's
> until I would have to even consider getting an upgrade.
>
> Managing all these users would be my problem though. When Habari
> updates come around I would easily create a script to go in and modify
> all the files and what not, but that may prove to be an issue with
> custom modifications. Though I can of coarse not permit FTP/SSH access
> to the blog files which would simplify this. Maybe access to the user
> directory only, where they can modify plugins, themes, custom classes,
> and files on their own. Meaning all System files could be replaced.
>
> Support would become an issue to, I would need help from the Habari
> Community to give these users support. From common questions to
> debugging their mess ups users would be emailing support.
>
> Costs might become a problem if we as a community decide to host
> somewhere else for this service. As I mentioned I could host this but
> that is only one suggestion, we would do things in many ways. I am new
> the community but am trying to get myself involved, however there are
> users who have been here for years who might think it better not to
> start a service with someone who hasn't been around long, completely
> understandable.
>
> In any case, I think a service such as this would increase the number
> of Habari users quickly. Please vote if you would think this is an
> idea we should talk more about or drop it now and potentially bring it
> up at a later date.
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to