├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── credits.txt ├── data ├── user.json ├── user2.json └── zips.json ├── help.txt ├── learnyoumongodb-screenshot.png ├── learnyoumongodb.js ├── menu.json ├── package.json ├── prerequisites.txt └── problems ├── .DS_Store ├── basics_find_and_modify ├── problem.txt ├── setup.js └── solution.js ├── basics_indexes ├── problem.txt ├── setup.js └── solution.js ├── basics_query ├── problem.txt ├── setup.js └── solution.js ├── basics_update ├── problem.txt ├── setup.js └── solution.js ├── bulk_insert_with_index_and_query ├── problem.txt ├── setup.js └── solution.js ├── geospatial_query ├── problem.txt ├── setup.js └── solution.js ├── hello_world ├── problem.txt ├── setup.js └── solution.js ├── my_first_insert ├── problem.txt ├── setup.js └── solution.js ├── my_first_query ├── problem.txt ├── setup.js └── solution.js ├── retrieving_and_querying_HN_stories ├── problem.txt ├── setup.js └── solution.js └── storing_an_image_with_gridfs ├── problem.txt ├── setup.js └── solution.js /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Code of Conduct 2 | 3 | As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. 4 | 5 | If any participant in this project has issues or takes exception with a contribution, they are obligated to provide constructive feedback and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct. 6 | 7 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team. 8 | 9 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers. 10 | 11 | We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, ability or disability, ethnicity, religion, or level of experience. 12 | 13 | ## Credits 14 | 15 | Based on the [Contributor Covenant](https://github.com/Bantik/contributor_covenant) by [Coraline Ada Ehmke (Bantik)](https://github.com/Bantik). 16 | 17 | If you have suggestions to improve this code of conduct, please submit an issue or PR. -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | #Contributing to MongoDBSchool 2 | 3 | We'd love for you to contribute to our source code and to make MongoDBSchool even better than it is today! Here are the guidelines we'd like you to follow: 4 | 5 | - [Code of Conduct](#coc) 6 | - [Question or Problem?](#question) 7 | - [Issues and Bugs](#issue) 8 | - [Feature Requests](#feature) 9 | - [Submission Guidelines](#submit) 10 | - [Further Info](#info) 11 | 12 | ## Code of Conduct 13 | Please read and follow our [Code of Conduct][coc]. 14 | 15 | ## Got a Question or Problem? 16 | 17 | If you have questions about how to use MongoDBSchool, please direct these to the [Google Group][groups] discussion list. 18 | 19 | ## Found an Issue? 20 | If you find a bug in the source code or a mistake in the documentation, you can help us by submitting and issue to our [GitHub Repository][github]. Even better you can submit a Pull Request with a fix. 21 | 22 | **Please see the Submission Guidelines below**. 23 | 24 | ## Want a Feature? 25 | You can request a new feature by submitting an issue to our [GitHub Repository][github]. If you would like to implement a new feature then consider what kind of change it is: 26 | 27 | * **Major Changes** that you wish to contribute to the project should be discussed first on our [Google group][groups], to prevent duplication of work, and help you to craft the change so that it is successfully accepted into the 28 | project. 29 | * **Small Changes** can be crafted and submitted to [GitHub Repository][github] as a Pull Request. 30 | 31 | 32 | ## Want a Doc Fix? 33 | If you want to help improve the docs, it's a good idea to let others know what you're working on to minimize duplication of effort. Before starting, check out the issue queue. Comment on an issue to let others know what you're working on, or create a new issue if your work doesn't fit within the scope of any of the existing doc fix projects. 34 | 35 | For large fixes, please build and test the documentation before submitting the PR to be sure you haven't accidentally introduced any layout or formatting issues.You should also make sure that your commit message is labeled "docs:" and follows the **Git Commit Guidelines** outlined below. 36 | 37 | If you're just making a small change, don't worry about filing an issue first. Use the friendly blue "Improve this doc" button at the top right of the doc page to fork the repository in-place and make a quick change on the fly. 38 | 39 | ## Submission Guidelines 40 | 41 | ### Submitting an Issue 42 | Before you submit your issue search the archive, maybe your question was already answered. 43 | 44 | If your issue appears to be a bug, and hasn't been reported, open a new issue. 45 | Help us to maximize the effort we can spend fixing issues and adding new 46 | features, by not reporting duplicate issues. Providing the following information will increase the chances of your issue being dealt with quickly: 47 | 48 | * **Overview of the issue** - if an error is being thrown a non-minified stack trace helps 49 | * **Motivation for or Use Case** - explain why this is a bug for you 50 | * **Angular Version(s)** - is it a regression? 51 | * **Browsers and Operating System** - is this a problem with all browsers or only IE8? 52 | * **Reproduce the error** - provide a live example (using [Plunker][plunker] or 53 | [JSFiddle][jsfiddle]) or a unambiguous set of steps. 54 | * **Related issues** - has a similar issue been reported before? 55 | * **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be 56 | causing the problem (line of code or commit) 57 | 58 | **If you get help, help others. Good karma rulez!** 59 | 60 | ### Submitting a Pull Request 61 | Before you submit your pull request consider the following guidelines: 62 | 63 | * Search [GitHub](https://github.com/braz/learnyoumongodb) for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort. 64 | * Make your changes in a new git branch 65 | 66 | ```shell 67 | git checkout -b my-fix-branch master 68 | ``` 69 | 70 | * Create your patch, including appropriate test cases. 71 | * Commit your changes and create a descriptive commit message (the 72 | commit message is used to generate release notes: 73 | 74 | ```shell 75 | git commit -a 76 | ``` 77 | 78 | * Build your changes locally to ensure all the tests pass 79 | 80 | ```shell 81 | grunt test 82 | ``` 83 | 84 | * Push your branch to Github: 85 | 86 | ```shell 87 | git push origin my-fix-branch 88 | ``` 89 | 90 | * In Github, send a pull request to `learnyoumongodb:master`. 91 | * If we suggest changes then you can modify your branch, rebase and force a new push to your GitHub 92 | repository to update the Pull Request: 93 | 94 | ```shell 95 | git rebase master -i 96 | git push -f 97 | ``` 98 | 99 | That's it! Thank you for your contribution! 100 | 101 | When the patch is reviewed and merged, you can safely delete your branch and pull the changes 102 | from the main (upstream) repository: 103 | 104 | * Delete the remote branch on Github: 105 | 106 | ```shell 107 | git push origin --delete my-fix-branch 108 | ``` 109 | 110 | * Check out the master branch: 111 | 112 | ```shell 113 | git checkout master -f 114 | ``` 115 | 116 | * Delete the local branch: 117 | 118 | ```shell 119 | git branch -D my-fix-branch 120 | ``` 121 | 122 | * Update your master with the latest upstream version: 123 | 124 | ```shell 125 | git pull --ff upstream master 126 | ``` 127 | 128 | ## Git Commit Guidelines 129 | 130 | We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that are easy to follow when looking through the **project history**. But also, we use the git commit messages to **generate the MongoDBSchool change log**. 131 | 132 | ### Commit Message Format 133 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: 134 | 135 | ``` 136 | (): 137 | 138 | 139 | 140 |