MongoDB

MongoDB is an open source NoSQL document-oriented database. MongoDB allows flexible schema representation instead of relying on fixed tables and columns. It supports full indexing, query, aggregation, tunable consistency and durability levels, and linear horizontal scaling through sharding.

Issue Description

Since the old Instagram API will stop working on June 29 (See https://www.instagram.com/developer/), the url in https://github.com/parse-community/parse-server/blob/d0a9c709fea4cbdba540420353a36a0e89601ffb/src/Adapters/Auth/instagram.js#L9 needs to be changed to match the new "instagram_graph_user_profile" API. (See https://developers.facebook.com/docs/instagram-basic-disp

Yuck.

Whoever wants to tackle this, .chats-full should be a flex item instead.

Prerequisites

Are you running the latest version?
Are you able to consistently reproduce the issue?
Did you search the issue queue for existing issue?

Issue Description

The description field is missing in the input schema when you are creating a shop. It's defined in the graphql schema but not in the validation schema. So, if you create a shop with description,

Much of the text on Habitica's website either has no alt text or is not allowing screen readers to read the alt text. This is a serious accessibility issue as it means that anything that is represented solely by a graphic is essentially invisible to blind users of the site.

In some cases there is no alt text, but there is a tooltip. However, the screenreader will not read out the text unless y

See:
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0?type=dev

It would be better to use bcrypt, beause its more secure as it's slower (uses more computing cycles).
Your code could also be better:

You wouldn't need salt field in User model, because it's saved into the same field as password does.

For authentication, something like:

var mongoose = require('mongoose'),
  bcrypt = require('bcryptjs');

var userSchema = mongoose.Schema({
  email: String,

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

Aug	SEP	Oct
	14
2019	2020	2021

MongoDB

Here are 29,605 public repositories matching this topic...

meteor / meteor

macrozheng / mall

ityouknow / spring-boot-examples

mongodb / mongo

parse-community / parse-server

Issue Description

nswbmw / N-blog

linnovate / mean

NodeBB / NodeBB

reactioncommerce / reaction

Prerequisites

Issue Description

bailicangdu / node-elm

HabitRPG / habitica

macrozheng / mall-learning

pyeve / eve

angular-fullstack / generator-angular-fullstack

samuelclay / NewsBlur

digoal / blog

donnemartin / dev-setup

jenssegers / laravel-mongodb

golang-migrate / migrate

madhums / node-express-mongoose-demo

backup / backup

What went wrong?

RichardKnop / machinery

FAQGURU / FAQGURU

yinxin630 / fiora

macrozheng / mall-swarm

mongo-express / mongo-express

azat-co / practicalnode

Tencent / westore

mrvautin / adminMongo

bigchaindb / bigchaindb