Timeline for Single server / instance mongodb deployment
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2019 at 23:32 | vote | accept | Dannie P | ||
| May 17, 2017 at 13:41 | history | edited | SqlWorldWide | CC BY-SA 3.0 |
added 226 characters in body
|
| May 17, 2017 at 13:41 | comment | added | SqlWorldWide | Edited my answer. Looks good to me. Make sure backup is copied to different location in case you loose your storage (if that is important in your case). | |
| May 17, 2017 at 13:36 | comment | added | Dannie P |
Thank you. I've read the docs and still don't get it: should I enable journaling for single-server deployment? If I should, how do I do that? I know how to enable it in write operation via j:true, but can't see how to enable journaling for entire db. Anything else I need to do so that my deployment is fine?
|
|
| May 17, 2017 at 12:18 | comment | added | SqlWorldWide | I did get that from your question but still wanted to mention. You should be able to set up single-server following those links. | |
| May 17, 2017 at 11:31 | comment | added | Dannie P | Thank you for your answer and links. I know their recommendation but I don't need high-availability and replication, I want small single-server deployment. Like one can do with mysql and add replicas later when needed. | |
| May 17, 2017 at 1:40 | history | answered | SqlWorldWide | CC BY-SA 3.0 |