In the config file, however, you'd have to have the local mysql db, user, and pass (depending on setup above) the production mysql db, user, and pass authentication credentials to push the files (login/pass/private key) the local dir the remote dir the local path to the mysql apps (these would probably stay the same for mamp, but if the program isn't in the applications folder, then, well, it could break) the remote sever ip the local url the remote url. A config file for the server side would need to be generated, but I guess that could be done through a single web-script. There is another possibility that a simply little web-app could be written in php, and, when it's pinged (probably with a token to verify it), then it will run a php script or a python script or something (depending on what's installed) that will then move the files and import the database. It gets even trickier if you're using private keys.
#MAC MAMP MYSQLDUMP FULL#
So a full inventory of the firewalls and open ports would need to be considered. You can connect to mysql non-locally, but that's only if your hosting provider allows you to do so. If you don't have access to the shell, the ability to write cron scripts, etc. Slightly different commands, different paths.
#MAC MAMP MYSQLDUMP INSTALL#
Downside: you have to install a companion "app" on your server, and then it might not work quite as well on different *nix flavors, etc. (This of course would consume a lot of bandwidth, and so it would be better to do with some way of tracking changed files or a database diff sort of thing, depending on the size of the database). Then it seems like it would be easiest to write a cron job on the server that would check for the new files in an upload directory and then run a script to make a backup of the website, overwrite the database, and drop in the new files.
So, say you're using a virtual machine that you have root access to. So, native command line tools that can be backgrounded would be best. It wouldn't be nearly as good to do it through any programs (like ForkLift) as they would have to be launched and would play in the foreground. There are quite a few moving parts here, and each would be up to the hosting configuration. Then you'd have to somehow ssh in to the server and do a drop database and import sort of workflow.
#MAC MAMP MYSQLDUMP UPDATE#
Any help would be appreciated.It seems like the easiest way to do that would be to actually write a config file for each site, then use the mysqldump command tools and rsync to update the files in the background. My guess is maybe some sort of permissions issue but I haven't been able to work it out. I can see the process: - 0 extrapolation_db_backup Launchctl load ~/Library/LaunchAgents/extrapolation_db_ist` Which I've saved in /Users//Library/LaunchAgents
Users//Sites/extrapolationlaunch/dbase_backup.sh Applications/MAMP/Library/bin/mysqldump -opt -u root -proot -host=localhost extrapolation > /Users//Desktop/db/extrapolation_$DT.sql Here is the bash script for the mysqldump: DT=`date +%m_%d_%Y_%H_%M_%S` I can successfully run the bash script manually to backup the db in terminal, but if I try to use launchd, nothing seems to happen. I'm trying to create a mysqldump of a database via bash script, and automate the process by using Mac's launchd / launchctl process.
0 kommentar(er)
