Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle mongo errors on duplicate and other improvements #13

Open
wants to merge 69 commits into
base: master
Choose a base branch
from

Conversation

mackrauss
Copy link

  1. Added a guard to handle MongoDB errors on duplicate insertion.

  2. Moved BasicAuth passwords and usernames to config.yaml file. Added config.example.yaml file to repo and config.yaml to gitignore.

  3. Updates to Gemfile to make it work. Seems that https urls are now required??

zuk added 30 commits May 18, 2012 18:02
- new rest methods
- only one way to query collections now -- using 'selector' parameter
- renamed drowsy.rb to drowsy_dromedary.rb
…ock to point to newer versions of gems (fixes dependency on yanked multi_json 1.3.1)
…if id doesn't exist, will now happily create it instead of 404)
zuk and others added 29 commits January 28, 2013 13:23
…we send as form data and types are not retained (e.g. integers come through as strings)
…create a db or collection that already exists (currently fails for db creation)
…y exists during create -- catching the exception didn't seem to work consistently
…lematic since a 304 isn't expected to be a redirect
… status is now returned instead of 304 (304 was causing problems with CORS requests)
Adding collection limit parameter and Travis config
…t prefixing rackup with bundle exec in README
…will throw an error on key violation. Older version not always do so.
…s to prevent WakefulWeasel from running in circles on model.destroy() in frontend
@zuk
Copy link
Owner

zuk commented Mar 27, 2015

Hey Armin something's messed up with this pull request. Looks like you have copies of all the original commits in this repo. Can you try git reset --hard zuk/master, then rebase just your commits on top of that, then re-send the merge request (change 'zuk' to whatever your remote is called for my repo).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants