One of the more significant complaints I've seen is the confusion caused by all the individual repositories being so spread out across three different github organizations. While there are conversations happening about how those repos should be organized, one interim step is to provide a roadmap that outlines all of the relevant repositories, where they live, and how they relate to one another. Th

Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

On Windows10 machine, following README installation instructions:

c:\code\mean>npm start

mean@2.0.2 start c:\code\mean
concurrently -c "yellow.bold,green.bold" -n "SERVER,BUILD" "nodemon server" "ng build --watch"

[SERVER] [nodemon] 1.18.9
[SERVER] [nodemon] to restart at any time, enter rs
[SERVER] [nodemon] watching: .
[SERVER] [nodemon] starting node server
[SERVER] ../.

From cTheDragons:

It appears the username in the settings on the web has not been updated since the changeover. It states:
"We will be transitioning login names to unique, public usernames soon. This username will be used for invitations, @mentions in chat, and messaging."

From shanaqui:
![image](https://user-images.githubusercontent.com/1495809/51815458-cd275f00-230c-11e9-8f95-457e57bc7c7

The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

I think the average user doesn't caret about the GitHub repository of this project. You could remove the GitHub link from the top-right, and show it somewhere else.

It would be great if all of these projects included a devcontainer dir & docker file so that they can be run without any machine setup or config

The example code does not work as intended.

Steps to reproduce

Use the example code:

var express = require('express');
var proxy = require('http-proxy-middleware');

var app = express();

app.use(
  '/api',
  proxy({ target: 'http://www.example.org', changeOrigin: true })
);
app.listen(3000);

Expected behavior

This should create a proxy for /api to `http

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,

E.g.

check('email').isEmail().withMessage({
	message: 'Not an email',
	errorCode: ErrorCodes.NOT_EMAIL,
})

To support express-validator/express-validator#667 (comment).

Hi,

Can someone explain what is the purpose of having the Events object in the cloudformation file? The reason why I ask is that I was able to comment it out, rebuild the stack and still be able to create a user (POST /users).

Thanks.

The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?

I really like this project and I find it awesome. I wish there were resources like this when I started haha.
I believe that this project could gain both in popularity and usefulness by porting it to https://nuxtjs.org/

As it's still Vue.js and permit much more ( and potentially simpler) !
We can discuss about if you believe it's relevant to the project or not, to begin