MAMP WORDPRESS FROM LOCAL TO LIVE INSTALL
MAMP WORDPRESS FROM LOCAL TO LIVE UPDATE
MAMP WORDPRESS FROM LOCAL TO LIVE FULL

Next, it would probably be easiest as a python script, followed by a php script. If would be easiest to write it as a bash script.

MAMP WORDPRESS FROM LOCAL TO LIVE UPDATE

There just really are so many moving parts.Īutomator would again make things not work well at all because it would take over your computer for a bit, which isn't ideal as the update should really be a background task that just lets you know when it's done, especially because it could take a few minutes to do all the tasks that are necessary to do what you need to do. What's possible? What is your hosting provider? I do hope you have a virtual box. Perhaps another way that you could do it would be to combine the github workflow with a server script so that when you update (and push to github), then the server grabs everything from github. And needing files stored on a remote server to do the rest of the work isn't so great. You could probably write an alfred sub-workflow that would help create the config file, but that wouldn't be too elegant. There might be a few other things that I'm leaving out. 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.

MAMP WORDPRESS FROM LOCAL TO LIVE 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.

MAMP WORDPRESS FROM LOCAL TO LIVE 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.

Plus, if i was going to then move it from my real test server to final real destination then id have to manually redo it all again.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.

Unlike a normal DB where i can talk to the info as normal, since WP is a CMS im assuming that it ties the info to the domain but again, i dont know how it 100% works.Īny ideas as to what im doing wrong? because as of now, if i cant do it like this, id have to manually create ALL the pages. Im assuming that something has to be changed/done in order for it to work but not sure what. Then exporting the database sql from the local server(done), and thereafter importing it to the real server(done) and the 2xs that ive done it the site comes up blank.(outcome equals major fail!) Since my tool stopped working(uploads half the content) i decided to just do it manually by installing Wordpress first on the real webserver(done), Applying my theme(done), When done and ready for testing i use the tool, move it to my personal test server to test and when happy and work is approved, i move to the real server. Usually my workflow is that i develop the site on my local machine using WAMP/MAMP. So for backing up any/all my WordPress sites i use a tool called 'BACKUP BUDDY' and itsĪ great tool and all but lately its been really buggy and today finally it went kaboom!

Mamp wordpress from local to live