Error: Unable to open the database file
Ray
ray at linkit.com
Wed Apr 6 10:19:35 EDT 2016
Thanks for your confirmation on this, Mike. We'll continue with the PHP
middleware plan. It seems to be industry standard and it makes sense,
especially from a security standpoint.
On 4/6/2016 10:15 AM, Mike Bonner wrote:
> Actually, you CAN connect directly to to mysql server (its actually a
> server in its own right) if you set things up that way. You have to change
> where connections are allowed from but honestly, you're still better off
> using middleware. This way you can place any files with sensitive data
> (passwords etc) outside the directly accessible area of your webserver, and
> have your middleware "include" the file. In this way, you make it harder
> for people to poke around and figure out parts of your setup, and obviates
> the need to have a hard coded or known password to your mysql database.
>
> Having an open port accessible from anywhere directly to your database
> server is usually a bad idea.
> The php middleware idea should work swimmingly.
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
More information about the use-livecode
mailing list