CMS Made Simple Forums

I don't find any specific infos about this in the docs/faqs etc.

How do I create and manage different sites with cmsms?

can I start out from scratch instead of from adapting the default site found in the installation ?

How do I keep a backup of a site? how to restore from the back up?

Thankxx

How do I create and manage different sites with cmsms?

Heh, you'll have to use separate copies of the source tree for each domain. Or you could try out the changes I posted elsewhere on the forum or in the bugtracker. Those will allow you to run different domains from a single sourcetree, but you will still have separate databases for them and separate admin areas. (or you can combine the databases if you want the website to be the same too.)
Integrated management of separate websites is beyound the intended audience I think.

can I start out from scratch instead of from adapting the default site found in the installation ?

Sure why not? Remove all pages, create a new template based on your existing site and add your content. no problem at all. The existing pages are just there to guide you along. 

How do I keep a backup of a site? how to restore from the back up?

The is a separate backup module that can do those things.

jelle wrote: ...you could try out the changes I posted elsewhere on the forum or in the bugtracker. Those will allow you to run different domains from a single sourcetree, but you will still have separate databases for them and separate admin areas. (or you can combine the databases if you want the website to be the same too.)

Can you specify where this information can be found?

no, I won't. I made some changes that allowed me to do this, but it was a pain to set up and every module writer would still assume his chosen location for site specific files was the correct one. So clearly this was not the way to go.
There is a simpler trick you can use that looks like a sparate sourcetree but only takes up space for one: `cp -lr original/* target/` This will create a directory tree similar to the original, but will hardlink all files instead of copying them. 
offcourse, this will only work on linux/unix and not across filesystems. You will also need to set the permissions such that one user cannot change the contents of the linked files (she can only do that if she removes them first and saves a copy that can be changed)

You can do the rest of the tricks with apache mod_rewrite.

If you need a quick bash script that does this things for you, just ask me.