- #MIRRORSYNC DRUPAL MAC OS X#
- #MIRRORSYNC DRUPAL UPDATE#
- #MIRRORSYNC DRUPAL PATCH#
- #MIRRORSYNC DRUPAL PRO#
![mirrorsync drupal mirrorsync drupal](http://3.bp.blogspot.com/-4n15oIgCUNQ/UZ6r8Z1s7WI/AAAAAAAAGT8/aQyTqtHSwrM/s200/Mac+Webpage.png)
#MIRRORSYNC DRUPAL PRO#
Just send a copy of the database to anybody with FileMaker Pro and they are ready to sync.
#MIRRORSYNC DRUPAL UPDATE#
Users can delete, add, or modify records and simply run the sync script whenever they want to update their offline copy of the database with FileMaker server.
![mirrorsync drupal mirrorsync drupal](http://hussainweb.me/wp-content/uploads/2016/07/cygwin-mirrors.png)
After installing MirrorSync on your FileMaker Server and running the simple cross-platform configuration utility, MirrorSync dynamically generates a synchronization script that users run whenever they're ready to sync.
#MIRRORSYNC DRUPAL MAC OS X#
MirrorSync Features 360Works' MirrorSync works with both FileMaker 11 and 12, and can run on an iPad, iPhone, or computer running Mac OS X or Windows since there are no plugins required. There are no plug-ins required, and no scripts to write - the MirrorSync configuration utility writes them for you! Setup typically takes less than 30 minutes, and requires no advanced FileMaker knowledge. MirrorSync has been designed to be very simple to configure. To keep all the data in sync, simply run the MirrorSync script and all changes will be transferred between the offline copy and FileMaker Server to bring them up to date. Mobile users can carry an offline copy of their database with them on their iPhones and iPads, or home/remote users can use bidirectional sync with their laptop and desktop computers to work offline on a fast local copy, which caches their data and solves WAN performance and connectivity problems.
#MIRRORSYNC DRUPAL PATCH#
Of course, a patch to make this "scalable" design also "synchronizable" is by using an external cron job to check periodically for changes in master, as suggested in comments.MirrorSync is an easy-to-use data replication tool that quickly and seamlessly syncs an offline database running on FileMaker Go or FileMaker Pro with a multi-user database hosted by FileMaker Server. So you have to ponder whether changes to your masters will be so critical to compensate the trade-off in scalability. The downside of this strategy is that you might eventually want to make a change to the live server that you want to be propagated to the mirrors before they need to push any change. This way you don't need to setup a hook in the master and synchronization strategy will be completely managed by mirrors. You'll probably find more elegant to use a "lazy" sync strategy in your mirrors: when they receive a push they don't just push to the master, but before that they fetch/pull from the master. On the other hand, that's not all of a scalable design (every time you add a new mirror, you'll need to change your live server's hook to add a site to push).
![mirrorsync drupal mirrorsync drupal](https://www.fmphost.com/wp-content/uploads/2015/03/logo-drupal.png)
Now if site1 on dev1 pushes commits, they are magically pushed to the master-bare-repo.īut what if I make a change on the live server, and push that? I can't set up a post-receive hook to push to the other(s) because that would presumably trigger their post-receive hooks which would end up in recursion?įirst of all, you won't end up in a recursion, since the post-receive hook isn't executed when "Everything is up to date" (as noted in this other question), which will be the result of the pushes from the mirrors to the live server. So I used post-receive hook on dev1's mirror to do git push -mirror origin. But I want the mirrors to stay in sync at all times. dev1$ git clone -mirror live:master-bare-repo dev1-mirror-repoĭev1$ git clone -b site1 dev1-mirror-repo site1ĭev1$ git clone -b site2 dev1-mirror-repo site2Īll good so far.
![mirrorsync drupal mirrorsync drupal](http://3.bp.blogspot.com/-4n15oIgCUNQ/UZ6r8Z1s7WI/AAAAAAAAGT8/aQyTqtHSwrM/s1600/Mac+Webpage.png)
What I'd like to do is set up a mirror of the bare repo on each of my dev servers, and then clone from that. This is great on the one server, hard links are used, it's fast and efficient.īut on my dev servers, they typically all clone from the bare master repo, which means two sites on the same machine can't use hard links to save space. So on, say, the live server I have a bare master repo, and all my sites are clones of this, each using a different branch. I have several sites that use Drupal, I have several servers, live, dev1, dev2.ĭrupal's codebase repo is big (112Mb), so I'm keen to make the most of git's hard-linking abilities so that each time I add a site it's not duplicating this.