I made some tests with MongoDB 2.1 (unstable debian package). I want to test the code with 2.0 stable to see the speed difference.
Can I simply uninstall mongoDB 2.1 and reinstall 2.0 without caring about the data ?
Thanks
#Stennie replied the question with his comment. I tried and it worked. On the mopngoDB website, the best is to download the legacy-static witch is very usefull for version testing.
Be sure to put the right data path to mongod ;-)
Related
I need to update an old forum made in phpBB from version 3.0.11 to the new / stable version 3.2.2.
It is the first time that I put my hand at phpBB.
Making an update step by step is complicated: move from 3.0.11 to 3.0.14 ... from 3.0.14 to 3.1.x ... and from 3.1.x to 3.2.2.
So I thought: can I make a clean install of 3.2.2 and import everything I need (posts / forum / users / ALLINEED)?
Do you know any plugins that do this? maybe phpBB itself does it? Or maybe I just need to export the tables from mysql?
can you advise me something?
thank you
There is no plugin to do it, but there is a process to upgrade from 3.0 to 3.2. Your forum will be as clean as a fresh install.
The more secured solution is to begin by upgrading from 3.0.11 to 3.0.14 for security reasons.
When you can stop your forum during one or two hours, stop it and upgrade directly from 3.0 to 3.2. You don’t need to upgrade to 3.1 then to 3.2.
All explanations are provided in upgrade documentation from 3.0 to 3.2
Do not forget any step! After step3, I advise you to restore the 3.0.11 forum on a local machine or another server to be sure that your backup files are not corrupted. (Yes, it could happen during a download.)
I did it a lot of time. It works fine. One hour to do it cautiously and slowly (+ download and upload time).
Why is 3.0.* ok but 3.2 version has to specifically be 3.2.6? Is 3.2.1 ok?
Any version is fine when doing a fresh install with parse-server but from parse.com you will not be able to move to 3.2. Seems that migration tool wont allow it.
I moved to 3.0 and from there did backup/restore to 3.2.
However i would always strongly suggest that one in general runs the latest version if you can.
I do know that all test on mongodb 3.2.6 are passing including geo queries.
On starting meteor 1.4.1, I get this message:
Your development database is using mmapv1, the old, pre-MongoDB 3.0 database
engine. You should consider upgrading to Wired Tiger, the new engine. The
easiest way to do so in development is to run meteor reset. If you'd like to
migrate your database, please consult
https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/
I though Meteor looks after the mongodb side of things under the hood and I would need to fix it if it is not broken, Will it be a problem if left as is or should be better to upgrade, and how to go about it? Thanks
You can check it in here.
https://guide.meteor.com/1.4-migration.html#update-to-mongo-3_2
MDG recommended you to update. minimum version supported by metetor1.4 is Mongodb Version 2.6.
This may be a dumb question, but I am confused about something. I have downloaded mongodb 2.6.4(latest) version to my mac, and deleted old mongodb folder which had executables and other stuff. But whenever I execute 'meteor mongo' command from my meteor.js application, it is opening MongoDB shell version 2.4.9, not the latest one. Why is this happening? Where is this old version is coming from? How can I use the latest version in meteor.js application?
Thank you
Meteor 1.0.x supports both 2.6 and 3.0. It ships with 2.6 locally.
http://info.meteor.com/blog/meteor-104-mongo-cordova-template-subscriptions
Meteor includes its own version of mongodb as a part of its bundle when you ran curl https://install.meteor.com | sh
It does this so its not a hassle to install and they can bundle the correct supported versions with it.
Meteor doesn't yet officially support 2.6.4 on the account of some oplog differences, though you can get it to work without the oplog without any issues, and with the oplog with a couple of issues.
How to go about upgrading moodle without all coursefiles going to the legacy folders?
I have tried re mapping files and creating links in the course area to the files that worked, but i am wondering if their any other way of going about it? Possibly upgrading further to 2.3+ could fix this issue?
Yes it is possible to upgrade moodle version from 1.9 to 2.2.
Please go through following url
http://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2