Closed dwrensha closed 8 years ago
Will this handle migration without me having to do more effort? i.e., if I have a meteor-spk app already using Niscu, and I upgrade meteor-spk, will it automatically handle migrating data, or do I need to do something to make it work?
Yes, the migration is automatic.
:+1:
Note that vagrant-spk will need some updating as well to work properly with this. I believe it currently doesn't use meteor-spk's start script, opting instead for a shell script, which made some sense when the script was trivial but perhaps now we should should switch it back to using the start script...
BTW @dwrensha, Meteor 1.2 was released a few hours ago, I’m not on the blending edge anymore ;-)
Niscu was causing @mquandalle problems (perhaps related to GridFS). This pull request moves meteor-spk over to Mongo 3.0 with the Wired Tiger storage engine, which can be configured to have a small disk footprint. We need to still include the niscud binary in order to allow data in old grains to be migrated.
I've verified that this works with Wekan. (Though I needed to drop in a newer node binary to get that to work, because Wekan lives on the bleeding edge of Meteor releases.)
Note that after these changes, we build both Niscu and an unpatched Mongo 3.0 from source, which seems like a bit of overkill, but I haven't gotten around to figuring out a better way.