Best way to build a CMS that publishes to users sites

[whoisgregg]

I've got a project coming up where I am building a custom niche content management system. Having the web site hosted on my server will not be an option, so I need to work out a way to publish to each users website.

Any suggestions on how to do this? Once each user provides FTP connection details, is it as straightforward as looping through the generated pages and uploading them to the remote site?

[henry0]

I created such a CMS here is how I do it:
One set a robust Auth that allows the Admin user to create a master account
Two after going to security input and validation my script from a template dir creates all needed files and links (real files and no ### ID? - clean links)
Three the admin creates as many as needed “user” account
Four login as a user and start editing/adding content.

The admin may create and del “editors” accounts

The user may create unlimited dirs and pages
Publish and unpublished
Set how the links should appear.
Add secured email

It comes (As needed) with a newsletter/mailer (opt-in opt-out)
Articles publisher
Calendar of events
Etc…

Make sure to add a function that will del your install dir
The system creates added tables on the fly (one per new dir)
But I manually load the original DB (Not done it on auto mode yet!) I have no problem with that since I manage the accounts, I do not per se sale it, but I integrate the system in any new dev.

My CMS is not targeting "one size fits all users" and the developper is required to be PHP MySQL sufficiently knowledgeable.
The admin and users do not need any tech capability.

The install is very fast (Full install tailor-made 45 minutes max)
Each such site can be built to user’s requirement once you know your way around the main templates
It uses spaw editor with the iBrowser plugin, which I worked on with the original developer.

the whole thing is PHP MySQL driven and the templates are OOP.

Bear in mind that (in my opinion) Creating real file thus real links make your life easier
If you need more info email me.
if you need more input ask for it :)

Cheers

[whoisgregg]

So for what you wrote, the scripts get installed on the client's web server?

I don't want to go through the hassle of maintaining versioning and upgrades for different installs with each client, so I was hoping to build a system where each user signs in to my site, edits their site, then hits a "publish/upload" button to send the changes to their web server. (Static pages only to their server, not actual PHP scripts.)

I also don't want to end up giving away my work and the clientele in this niche are likely to do so if they have the source on their own server.

[henry0]

Yes it is on the client server (mine anyway) since I host myself.

I have a contract set by my attorney that takes care of the proprietary software usage limitations.

I also have done what you described
But then each of your clients won’t have a dedicated IP or even a true URL
They only will be a sub-dir of your portal site.

This generates much more headaches, giving each new client a new ID and adding tons of where ID and PW =$whatever, plus the URL could be not a clean one.

You could do as I described (my system) if you host as a VS then you could create a package corresponding to the model and via a form generate the changes when installing.

Edit
<<<
You may encode your scripts with the Zend encoder.
>>>