Hey there, its been a while since I last wrote something on my blog. I have been really busy developing a Content Management System for my business – [ http://www.spinningyourweb.net ] – it has been programmed in PHP and uses MySQL as a backend. This will be running on many of my clients website within the next month or two.
I still have some things to add to the system such as a few more image functions (editing the size of the picture) and being able to switch between images easily while editing. I have considered running one instance of the program and having all the clients logging into a single version of the system, but this does have some problems – such as;
- Version control – If some clients pay for a later version – this could be dealt with with a few dynamic tampers
- Database Failure – If the database corrupts, it could lead to; information displaying on the wrong website or if the database goes down, all the websites will go down
However, there are many positives to running a single instance;
- When there is a system update, you only need to run one codebase update
- Database backups are easy to manage – you dont need to backup multipul databases – you can do the one and when there is a problem, you only need to roll back the one version.
Anyway, those are just a few thoughts, I have attached a few screenshots of the content manager below;
how interesting. very good. the automatic update thing is the most interesting i think.
if you created a system like http://www.wordpress.com for instance where you have one instance of the application running on a server (like http://www.sywcms.com, for example) and then you just point the data to a domain it would be really cool.
J
Hi Jonathan,
Thats the concept, the program will run one instance and then it will automatically update – well automatic – not really – i will only need to update one code base. It may run on sywglobal or sywmedia / sywsocial – ill have to see
hmmm, cool.