Data Syncing

[arunoda]

Data Syncing

[timbrandin]

This would definitely be useful, this is a very common thing to do with Drush in Drupal.
For example doing:
drush sql-sync @local @prod --create-db will synchronize the database from the machine defined in the @Local alias to another machine defined in the @prod alias. Very useful!

[MaazAli]

I think this should be an entirely different tool. Considering that the database of some applciations can be hosted in a location other than where your app is being deployed. Creating another tool where you can define aliases for the location of your mongo database would be pretty neat.

[timbrandin]

@MaazAli Yeah your right, this could be something else yeah.. or what do you think @arunoda? :)

[arunoda]

Yes it is. We need mup to be simple.
And that makes my life simple too. (no need to maintain a lot)

On Thu, Mar 12, 2015 at 1:19 PM Tim Brandin [email protected]
wrote:

@MaazAli https://github.com/MaazAli Yeah your right, this could be
something else yeah.. or what do you think @arunoda
https://github.com/arunoda? :)

—
Reply to this email directly or view it on GitHub
zodern/meteor-up#31 (comment).

[timbrandin]

True! Would be nice if @meteor was extensible with for example aliases and data-syncing then one could do for example:
meteor db-sync @local @prod

[timbrandin]

Then one could also write:
meteor mongo @prod to access the mongo interface on the production server

[timbrandin]

And aliases could be found in ~/.meteor/aliases/.

Which one can share the aliases with your coworkers super simple just by adding symlinking that folder to dropbox/drive etc.. :)

[timbrandin]

Actually mup could also benefit from using aliases, because we already keep deployment settings files somewhere outside of the repo most times, this could be contained in the aliases instead. and would make it possible to just stand in the right app and do mup deploy @prod

Aliases could even inherit settings from other aliases and so forth.

Sorry for spamming! :S