Summary of meteor deployment issues


Deploying meteor in server environment

The server includes: nodejs, GIT, mongodb

  1. Install meter

    $ curl | sh
  2. Install the demetrizer

    $ npm install -g demeteorizer
  3. Installing PM2

    $ npm install -g pm2
  4. Type in the root of the warehouse

    $ demeteorizer 

    Package (build nodejs available) code

  5. $ cd .demeteorized/bundle/programs/server
  6. $ npm install
  7. Return to the root directory of the warehouse and type

    $ MONGO_URL=mongodb://localhost:27017/test PORT=80 ROOT_URL=http://localhost:80 pm2 start main.js

Node.js Administration:

reference resources…Install the latest version (including NPM, no need to install separately)

  1. Install NVM

    $ curl -o- | bash

    or Wget:

    $ wget -qO- | bash
  2. Using NVM to install node

    $ nvm install 4.6.1
  3. Set default node version

    $ nvm alias default v5.0.0

For ports less than 1024, sudo is required

$ meteor --port 80
Error: listen EACCES
$ sudo meteor --port 80

Mupx setup failed

$ mupx setup: sudo:no tty present and no askpass program specified

Edit / etc / sudoers to add lines

Defaults visiblepw;

reference resources:…

Apache reverse proxy settings:

ServerName localhost

<VirtualHost *:80>

ProxyRequests Off

<Proxy *>
    Order deny,allow
    Allow from all

ProxyPass /groupchat max=20 ttl=120 retry=300
ProxyPassReverse /groupchat http://www.pay4china:3000/groupchat


Reverse proxy configuration Q & A


AH00526: Syntax error on line 30 of /etc/apache2/sites-enabled/000-default.conf:
Invalid command 'ProxyRequests', perhaps misspelled or defined by a module not included in the server configuration


$ sudo a2enmod proxy
$ sudo /etc/init.d/apache2 restart


No protocol handler was valid for the URL /groupchat. If you are using a DSO version of mod_proxy, 
make sure the proxy submodules are included in the     configuration using LoadModule.


$ sudo a2enmod proxy_http