Meteorite documentation currently says:
"[...] you need to provide Node.js 0.8 and the MongoDB server. Then you can start the application by invoking the host, specifying the HTTP port for the application to listen on, and the MongoDB endpoint."
So, among several ways to install Node.js, I ran it and executed it, following the best advice I found : unpacking the latest version, available directly on the official Node.JS website , already compiled for Linux (64 bits, in my case):
# Does NOT need to be root user: # create directory mkdir -p ~/.nodes && cd ~/.nodes # download latest Node.js distribution curl -O http:
And to install MongoDB , I just followed the instructions in the MongoDB manual, available in the "Documentation" section on its official website :
# Needs to be root user (apply "sudo" if not at root shell) apt-key adv --keyserver keyserver.ubuntu.com --recv 7F0CEB10 echo 'deb http://downloads-distro.mongodb.org/repo/ubuntu-upstart dist 10gen' | tee /etc/apt/sources.list.d/10gen.list apt-get update apt-get install mongodb-10gen
The server is ready to launch Meteor applications! For deployment, the main βproblemβ is where the β bundle β operation occurs. We need to run the meteor bundle command from the application source tree. For example:
cd ~/leaderboard meteor bundle leaderboard.tar.gz
If the deployment will occur on another server (option 2), we need to load the package tar.gz file onto it using sftp , ftp or any other method of file transfer. Once the file is found, we will follow both the Meteor documentation and the README file, which is magically included in the root of the bundle tree:
If the deployment will be on the same server (version 1), the package tar.gz file already exists, and we do not need to recompile the native packages. (Just go to the appropriate section above.)
Wow! With these steps, I have deployed a Leaderboard example deployed on my user server , rather than "meteor.com" ... (only for studying and evaluating their services!)
I still need it to work on port 80 ( I plan to use NginX for this ), save environment variables, run Node.JS, disconnected from the terminal, and so on ... I know that this installation is "almost bare". .. only the foundation, the first step, the main foundation stones.
The application was "manually" deployed, without using all the meteor deploy commands of magic functions ... I saw that people published their " meteor.sh " and " meteoric.sh " and I along the same path ... create a script to emulate the function "deploying one team" ... remember that in the near future all this will be part of only the pioneers of the Meteor, as it will turn into a whole galaxy! and most of these questions will be archaic things of the past.
In any case, I am very pleased to see how a quickly deployed application runs on the cheapest VPS , with surprisingly low latency and almost instant simultaneous updates in several different browsers. Fantasy!
Thank!!!