Thank you for the ideas. I have created a Directory (/mysql) in the existing Default virtual host. When I try to run a query, I am getting an error returned to me:
"You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '\/SELECT * FROM test' at line 1" I know that the query is OK as well as the database and table. The DB Bridge seems to be adding 2 slashes to the beginning of any query. This is what my URL structure looks like: http://ec2-174-129-129-183.compute-1.amazonaws.com/mysql/SELECT%20%2A%20FROM%20test%3B With "SELECT%20%2A%20FROM%20test%3B" == "SELECT * FROM test;" Is having the bridge in a directory like this causing the problem? Thank you again. On Wed, Dec 24, 2008 at 1:37 AM, Alvaro Lopez Ortega <[email protected]>wrote: > Hello Trevor, > > It's up to you whether you run it on the same server or you launch a new > one. I'd personally run two servers in the same box, although it isn't > really required. > > What the documentation means is that you'll have to add a special rule to > handle the DB-balancer requests. For instance, you could create a virtual > server with a single rule where the DB requests are handled. In case you > wanted to add the DB-balancer rule to the very same virtual host, I'd > recommend you to add a 'Directory' rule handled by it, so Cherokee knew > which requests are SQL queries and which are regular file/script requests. > > > PS: as I've pointed quite a few time, most of the people who are currently > working on the project are not native English speaker, including myself. If > someone finds an inaccuracy in the documentation, please, let us know. > > > > On 24-dic-08, at 06:38, Trevor Fitzgerald wrote: > > I am trying to set up a MySQL Bridge to balance requests among a network >> of replicated databases. The docs say the following: >> >> "Thus you will have to set up multiple rules in Cherokee, or even multiple >> instances in different ports, in case you need to use several databases." >> [1] >> >> I would like to keep the database proxy on the existing app server to >> eliminate points of failure from the architecture. If I cannot run the >> bridge in the same instance as the web server, running it on a different >> port would be best. >> >> Can someone please explain how I make that happen? What do I have to >> configure and do? Or any alternative ideas are appreciated. >> >> Thank you. >> [1] http://www.cherokee-project.com/doc/cookbook_dbslayer.html >> > > -- > Octality > http://www.octality.com/ > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
