Hogie

I do not see how to connect that to a different database. Not the blesta database, but a remote database for the system I am trying to get blesta to talk to. Since I will have multiple of these database clusters, I can not set the blesta and the service's databases to be the same since multiple clusters would have overlapping table names.

I am currently writing a module that requires a direct database connection to the service. I am using the minphp-db code, but I am trying to figure out how to capture a connection error when I am testing it in the Module::addModuleRow code, but the system is capturing it and throwing up: Something went wrong. SQLSTATE[HY000] [1045] Access denied for user 'xxxxxxx'@'remotehost' (using password: YES) I'd like to figure out a way to capture that error so I can throw up an error to the user instead of a blank screen (which is what you get when Configure::errorReporting is set to 0). Any ideas? There is currently not an API available for what I am writing, so it needs to be a direct DB connection.

I guess I should also throw out what is going on with it... try_files is a fast way to do an if statement if the files exist. First, it will try to see if that path exists as a file ($uri), then see if it is a directory ($uri/) then it will internally redirect it to run as index.php?fullpath which is what the url was doing with index.php in it, but we are just making it go away. You can add other things too, and this is MUCH faster than if statements in the location section. If you can get away with it, never use if statements in the nginx configuration where it will be parsed for every connection. It would slow it down to apache levels

I am running blesta-4.0.0-b4 as root in a dev environment (debian/nginx/php7.0-fpm) and I use this for the root location section: location / { try_files $uri $uri/ /index.php?$args; } and my urls come out as: http://blesta.mydomain.local/admin/settings/company/modules/manage/10 Hope that helps.