one cms for multiple servers
Posted: Mon Nov 24, 2003 3:10 pm
Hi Everyone,
At our company we have developed a content management system which currently is placed behind a website on the same domain.
We want to convert it to let it run on one domain, but updates the database of the domain chosen by the user that has logged in.
Updating the database isn't a problem, because you can easily connect to another mysql server(if allowed).
The difficulty starts with uploading images. Currently the situation is that the filename of the image is stored in a varchar field, and the code of the cms and website knows where to place/find the image.
This situation is not a problem when the domain is on the same server as the cms domain, because we can set rights to different directories, so we could write the image to another domain's webroot.
The problem starts when the domain is on another server than the cms domain(let's say the website of the customer is hosted at another hosting provider).
What would be the best sollution to solve this problem, with keeping these few things in mind:
1. We don't want to store the image in the database as a blob.
2. We've got all the username and passwords of our customer hostingspace.
We were thinking about ftp-ing the files to the other server, but maybe there's a better sollution.
Let us know, if you know a better one.
Thanks in advance for reading this awfully long story.
Greetz Jolly.
At our company we have developed a content management system which currently is placed behind a website on the same domain.
We want to convert it to let it run on one domain, but updates the database of the domain chosen by the user that has logged in.
Updating the database isn't a problem, because you can easily connect to another mysql server(if allowed).
The difficulty starts with uploading images. Currently the situation is that the filename of the image is stored in a varchar field, and the code of the cms and website knows where to place/find the image.
This situation is not a problem when the domain is on the same server as the cms domain, because we can set rights to different directories, so we could write the image to another domain's webroot.
The problem starts when the domain is on another server than the cms domain(let's say the website of the customer is hosted at another hosting provider).
What would be the best sollution to solve this problem, with keeping these few things in mind:
1. We don't want to store the image in the database as a blob.
2. We've got all the username and passwords of our customer hostingspace.
We were thinking about ftp-ing the files to the other server, but maybe there's a better sollution.
Let us know, if you know a better one.
Thanks in advance for reading this awfully long story.
Greetz Jolly.