amichaelgrant

var mongoose = require('./index')
  , TempSchema = new mongoose.Schema({
      salutation: {type: String, enum: ['Mr.', 'Mrs.', 'Ms.']}
    }); 

var Temp = mongoose.model('Temp', TempSchema);

console.log(Temp.schema.path('salutation').enumValues);
var temp = new Temp();
console.log(temp.schema.path('salutation').enumValues);

amichaelgrant

server {
        listen      80;
        server_name server.example.com;
        rewrite     ^(.*)   https://$server_name$1 permanent;
}

server {
        listen   443;

        server_name  server.example.com server;

amichaelgrant

Configuring Nginx for Apache Tomcat 7
September 23, 2011 Java, NginX, Tomcat, Ubuntu 19 comments

Apache Tomcat can be the first choice of an Application Server for someone new to Java world. There are obviously other servers such as JBoss Application Server and IBM WebSphere but those may be slightly difficult for a newbie.

In some situations, like when we are serving a few websites with Nginx over port 80 (HTTP), it is required to configure Nginx in order to serve our Java web application which is running on Apache Tomcat. It is basically using Nginx as a Reverse Proxy This can be done with a new server section in Nginx  configuration file (it is in /etc/nginx/sites-available/default by default) :

server {
    listen mysite.com:80;
    server_name  mysite.com;

amichaelgrant

## Configure eth0
#
# vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE="eth0"
NM_CONTROLLED="yes"
ONBOOT=yes
HWADDR=A4:BA:DB:37:F1:04
TYPE=Ethernet
BOOTPROTO=static

amichaelgrant

webserver: webserver.c libuv/uv.a http-parser/http_parser.o
	gcc -I libuv/include \
    -lrt -lm -lpthread -o \
    webserver webserver.c \
    libuv/uv.a http-parser/http_parser.o

libuv/uv.a:
	$(MAKE) -C libuv

http-parser/http_parser.o:

amichaelgrant

www.yahsoftware.com
www.gigo.club

amichaelgrant

#!/bin/bash
# Sample App       Init script for running sample app daemon
#
# chkconfig: - 98 02
#
# description: Sample Application Upstart, using Forever


APPHOME=/opt/sample-app
APPSCRIPT=app.js

amichaelgrant

check process redis-server
    with pidfile "/var/run/redis.pid"
    start program = "/etc/init.d/redis-server start"
    stop program = "/etc/init.d/redis-server stop"
    if 2 restarts within 3 cycles then timeout
    if totalmem > 100 Mb then alert
    if children > 255 for 5 cycles then stop
    if cpu usage > 95% for 3 cycles then restart
    if failed host 127.0.0.1 port 6379 then restart
    if 5 restarts within 5 cycles then timeout

amichaelgrant

Use mongodump and mongorestore instead:

mongodump:
----------
mongodump --host <ip> --db <database> --out /var/lib/openshift/uuid/app-root/data --username <your-user-name>  --password <your-password>


mongorestore:
-------------
mongorestore --db <database> <file-from-mongo-dump.bson>

amichaelgrant

failed (104: Connection reset by peer) while reading response header from upstream, client:
If you are getting the above error in nginx logs running in from of upstream servers you may consider doing this as it worked for me:
check the ulimit on the machines and ensure it is high enough to handle the load coming in. 'ulimit' on linux, I am told determines the maximum number of open files the kernel can handle.

The way I did that?
modifying limits: for open files:
--------------------------------
add or change this line in /etc/systcl.conf
fs.file-max = <limit-number>