|
RE: Having Difficulty with MySQL connection
I wanted to comment on this thread because I ran into similar issues and hoped to get into some dialogue to clarify the logic behind a few of the design decisions.
Firstly, I love what has been done with webERP thus far. I spent a good amount of effort comparing various options out there and you have created what really stands out to me as a robust, well-built, modular solution. Very impressive.
I've installed our test system on BlueHost, which from what I've been able to determine restricts new db creation to be done with its internal control panel. This means that in order to create a new company database, the steps outlined by kbobsdaddy have to be carried out for each organization managed under webERP.
Our system handles a multitude of organizational entities, each being tracked under an umbrella account which handles transactions between them. We're hoping to do this via the API that you've put together, and looking to some of the automation forms/processes that you've made available.
During the initial install of the test account, I had problems very much like the on that kicked off this thread. After a couple hours of troubleshooting, re-naming folders, resetting permissions, deleting and re-creating db users and such, I was finally able to get it to work but it was pretty unpleasant and not something that I would want anyone to have to go through if it can be avoided.
In any case, I think that having the system detect organizations based on the directory names present, in combination with the automation of the naming scheme are at the heart of the problems that I came up against. BlueHost prepends an account prefix to the db name which caused all sorts of complications. I was aware of this detail going into the install and it still took hours to resolve; my renaming the account directory even exacerbated the issues.
The fields labeled on the form also contributed to some confusion, as assumptions are made about the company name and auto-naming of the db and user are treated as an outlier case. It was also unclear to me whether the db username and password versus the webERP username and password were required, and after trying several combinations manually through the config file, was left more confused by setting $allow_demo_mode = TRUE. (The user/pass did not match up with what I'd set)
I love what you're going for with this auto-install form. In its present state however it possibly causes as much suffering as it prevents, when run under server environments like the one I'm using anyway. I would like to help improve the automation for other users in this kind of environment; how do you currently collaborate for modifications like this?
I have several points that I'd like to discuss, most involving the underlying design philosophy involved in some of the mechanisms used here (and by extension in the 'Make new Company' option under the 'Utilities' menu section.) What should I do to help support your awesome project and avoid stepping on any toes?
Thanks!
|
