New Message: Re: Manila Best Practices?

[webmaster at userland.com]

A new message was posted:

Address: http://manila.userland.com/discuss/msgReader$236

By: Steve Kirks (srk at mac.com)

First Mr. Hooker--what a goregous post! I just skimmed it like the fat man at the smorgasbord; now I'm headed back to munch on the best parts....

Once again, the aging G3/300 is my tester machine, ensuring that I'm testing the software and not the OS. Besides, it's 7 years old--what's more fun than telling someone that the website you created is served on a 7 year old machine? :>

The MacOS X/Frontier curse (in my opinion) is that Frontier is a GUI driven app, due to it's history, so running it means running the GUI overhead--same as Windows. On the Mac side, it's a little more processor-intensive to do that (yes, I'm splitting hairs).

Add/Delete Sites:

I've added sites through the controlPanel and the createASite form, but your take is one I hadn't considered--moving/adding the form to other sites. I suppose that's you can create a toplevel site that's not the default, then subsites underneath. That's probably needlessly complicated and more of a human admin issue and not Frontier...rambling, sorry.

Deleting isn't as simple as adding (via the web) and the parts that are involved seemed to be scattered (two root files to modify and the actual content, too). Shouldn't be that hard. Is this a user issue or experience issue? Best practice would help here.

Machine admin always a member:

Looks like this is a "Steve needs to learn UserTalk/programming structure" issue. Still, if this is software for groups that don't want to lean on an IT department, then this seems like a flaw. If I'm running the machine and create multiple Manila sites, then the master admin person should be able to login to all of the sites *without* all sites sharing the same membership pool. Compare this to Windows NT/2000 administrator behavior. Thanks for callback hint. I'll study and implement.

Virtual hosting:

Now it seems that I have to 1) create a site using the standard form then 2) map a domain to that object in the root. If I do that, then any domain seems to use the same directory structure.

Example: mysite.com is default domain. I create mysite.com/steve and am a happy blogger. Later, I register a domain and map it to the same database object and voila! Manila contain with a virtual domain. If I go to newdomain.com it works, but I can also put in the subdirectory of another separate Manila site on the server and it works. More later via different discussion topic if warranted.

Wildcard DNS:

You hit the nail on the head. Looks like I'll talk to my DNS host and see if he can do wildcards.

Thanks again for taking the time to write this post. Check trioconnect.org for a structure of best practices as time passes. But be cautious in the next two days--I'm going to install a Windows server with Remote Desktop. :>

This is a Manila site.. http://manila.userland.com/.