fa sync with local and remote

I'm not sure why you'd want to do that. It is a web application, after all.

But if you really need two separate instances, you could have them use the same database. (Assuming that FA handles the locking required and that your database is accessible from outside.)

Updating two databases independently and then trying to merge the changes is going to be a mess.

I have done exactly this. I'm using master/master replication on the MySQL db. I did this because our internet connection in both of our branches is very flakey, and also so that we have an automatic offsite backup that we can use live if a machine goes out for some reason. There is, however, an issue you should know about....

When the internet goes down, if both branches make, say, a general ledger entry then you get a replication error because the primary key is the next one, so both branches use the same number for their GL entries. It's probably the same with sales/purchases, but so far I've only seen the GL issue, and it's a nightmare to correct.

So, the replication works nicely as long as the connection is there, but that's catch 22 because if the connection is there then you don't need the replicated database - you could just work from one instance of FA. If the connection goes down then the 2 locations will be writing different GL data with the same transaction number and you'll get replication errors and lose data.

What we need (in the next version?) is the primary keys written with a machine specific number, i.e 102323, 4, 5 etc from server 1, and 2022323,4,5 etc from server 2.

FA team, this won't take much programming... are you OK to include this in the core? It would be a major feature to have a system that can be replicated and on top of the IT benefit it's like automatic consolidation from a Finance point of view. I am happy to help with the coding if you like.