I know that by using oil migrate will automatically upload the tables for you in the database on local server (computer localhost) but I can't seem to get to work with my remote server.
I am currently using 3 different computers because I move around a lot and I keep all of my files in dropbox to keep them in sync but I do have a domain website that I would like to upload and work from my remote server. I can upload the files and everything but I can't get the oil to migrate or generate tables in my remote database. Is there an easier way of doing this? I have been trying to figure this out for the last few days as I am learning FuelPHP, which seems to be awesome framework so far, and I am getting frustrated. Any help would be greatly appreaticated!!
If you have access to the remote database server (you can connect to it from other than localhost) then you could setup a test environment db config and run this: FUEL_ENV=test oil r migrate
But this is rather an ugly workaround than a solution.
If you have access to the remote database server (you can connect to it from other than localhost) then you could setup a test environment db config and run this: FUEL_ENV=test oil r migrate
But this is rather an ugly workaround than a solution.
Another thing I noticed was that Oil have few new features added in Usage and one of them was server and I cannot find any documentation on how to config it because it seems to be connecting to my localhost rather than my remote server and when I ran '$ php oil server help', it returned information of server that is listening on. I don't know if this has to do anything with me trying to generate tables in my remote database.
it starts a local built-in PHP server, so you can use Fuel without having a webserver ready. It doesn't have any options, other then serving your index.php.
There is no help for the server command, it just runs PHP's built-in webserver. And it expects a standard Fuel setup, where you have a public folder (which is your docroot), and in it your index.php front controller.
If you don't have the /public folder, you can use the -d commandline option to specify the path to your docroot, and -r to specify the path to the router script (by default the phpserver.php in the oil package).
I've made a note that it isn't documented at the moment.
As to your exception: are you on MAMP by any chance? Or some other xAMP package?
Chances are that your webserver and the PHP cli binary use different php.ini files (on a Mac virtually always the case), which means the correct PHP config isn't loaded.
Assuming that you've not made a typo, since the error message is quite clear: Access denied for user 'enigmama_MD'@'localhost' (using password: YES)
I am using XAMPP on Windows 7 and I finally corrected the Access issue, it turns out that I needed to add a Remote Access on my webhost. Weird but it is no longer telling me that message it is now telling me that the connection is taking too long to respond. Another issue that I'll have to research later tonight.
I've added the missing "oil server" documentation and added inline help for the "server" command to the 1.8/develop branch. It should come online soon, at http://dev-docs.fuelphp.com.
In general you only need to use one db.php, which is in your environment folder. The one in app/config is only meant for some global (over all environments) defaults, and should under normal circumstances not be changed.
I know that. I wanted all of my changes to be done on my remote server because I move around so much that it is frustrating and annoying that I have to repeat the same process on different computers but since I got it fixed and realized that I only needed to make changes to one so I proceeded to remove the one that I didn't really need to make changes to.
I should not have to make anymore changes to the db.php for the rest of my development process so I am very excited to move forward.