Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in pure JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Try the getting started tutorial.
Next, read the guide or the reference documentation at http://docs.meteor.com/.
In this brief tutorial we combine Meteor with best practices in both application architecture and deployment, namely, Microservices and Linux Containers. We will bootstrap our Meteor application on the popular PaaS provider, the Digital Garage. Digital Garage utilizes Red Hat Openshift, Google Kubernetes and Docker Containers to create an open and efficient way to incorporate these best practices into our project.
- A Github account. If you do not already have a Github account, you can follow this link to sign up for free.
- A Digital Garage Account. If you do not already have a Digital Garage account, you can sign up for free at www.thedigitalgarage.io.
We will be:
- Forking the Meteor seed project on the Digital Garage Github Organization to your private repository.
- Creating a Meteor application workspace on the Digital Garage platform.
- Bootstrapping Meteor in your Meteor Application workspace with MongoDB and Node.js containers from Docker Hub.
- Building the AngularJS application from the source in the forked repository and deploying the application on Meteor.
After signing into your Github account, go to: www.github.com/thdigitalgarage/meteor-ex and fork the repository into your own account. This repository contains some files and a file structure that will give you a quick start on your Meteor application. I go into more detail on the files and file structure a little further into the tutorial. For now, let's complete our setup by logging into your Digital Garage account and set up Meteor.
After signing into your Digital Garage account, Choose the Add to Project link in the top menu bar to go to the template catalog.
In the add to project screen, choose Meteor Quickstart (qs-meteor) from the catalog.
In the template configuration page for Meteor Quickstart change the Git Repository URL to point to the repository that was just forked into your account. https://github.com/johnmccawley/meteor-ex.git. If you are running this tutorial in the free Hello World tier, you will want to set the Memory Limit for MongoDB to 128Mi rather than the default 192Mi. This will give your application enough room to build and deploy all of the containers it needs. For the rest of the parameters, you can simply accept the defaults for the remaining parameters and click "Create"
That's it. Digital Garage is now setting up your Meteor. On the next page you'll be presented with some information about your new application. When you are ready, click "Continue to Overview". You will be taken to the Project Overview screen where you can watch Digital Garage do the setup work for you. In just a few minutes you'll have full Meteor stack running in containers and managed through Google Kubernetes. When MongoDB and Node.js are completely deployed, (the pod status circle is Green) simply click on the application URL in the upper right corner of the overview screen. You will be taken to a browser to see a simple "Hello World" message.
Now that we have the Meteor Example repository forked into your account, let's take a few minutes to review the file structure for the repository. There are many ways to structure a Meteor application. I have tried to take the best-practices from several tutorials and create a simple yet expandable file structure for this example project. For further reading on file structures for Meteor, Mean.io is a good boilerplate to see best practices and how to separate file structure. For now we will just use the following structure and adjust as we go.
meteor-ex
├── app - files for node components (models, routes)
├── config - all our configuration will be here
│ └── database.js
├── LICENSE
├── openshift
│ └── templates
│ └── qs-meteor.json - example template for Kubernetes.
├── public - files for our front-end angular application
│ ├── app.js
│ └── index.html
├── package.json -npm configuration to install dependencies/modules
├── README.md
├── tests - files for basic test scripts
└── server.js -Node configuration
Congratulations! You have deployed your first application on Meteor.
You can create a new application using the web console or by running the oc new-app command from the CLI. With the OpenShift CLI there are three ways to create a new application, by specifying either:
Pointing oc new-app at source code kicks off a chain of events, for our example run:
$ oc new-app https://github.com/thedigitalgarage/meteor-ex -l name=myapp
The tool will inspect the source code, locate an appropriate image on DockerHub, create an ImageStream for that image, and then create the right build configuration, deployment configuration and service definition.
(The -l flag will apply a label of "name=myapp" to all the resources created by new-app, for easy management later.)
We can also create new apps using template files. Clone the demo app source code from GitHub repo (fork if you like).
$ git clone https://github.com/thedigitalgarage/meteor-ex
Looking at the repo, you'll notice one file in the openshift/templates directory:
meteor-ex
├── app - files for node components (models, routes)
├── config - all our configuration will be here
│ └── database.js
├── LICENSE
├── openshift
│ └── templates
│ └── qs-meteor.json - example template for Kubernetes.
├── public - files for our front-end angular application
│ ├── app.js
│ └── index.html
├── package.json -npm configuration to install dependencies/modules
├── README.md
├── tests - files for basic test scripts
└── server.js -Node configuration
We can create the the new app from the qs-meteor.json template by using the -f flag and pointing the tool at a path to the template file:
$ oc new-app -f /path/to/qs-meteor.json
oc new-app will kick off a build once all required dependencies are confirmed.
Check the status of your new nodejs app with the command:
$ oc status
Which should return something like:
In project my-project on server https://10.2.2.2:8443
svc/meteor-ex - 172.30.108.183:8080
dc/meteor-ex deploys istag/nodejs-ex:latest <-
bc/meteor-ex builds https://github.com/thedigitalgarage/meteor-ex with openshift/nodejs:0.10
build #1 running for 7 seconds
deployment #1 waiting on image or update
Note: You can follow along with the web console to see what new resources have been created and watch the progress of builds and deployments.
If the build is not yet started (you can check by running oc get builds), start one and stream the logs with:
$ oc start-build meteor-ex --follow
You can alternatively leave off --follow and use oc logs build/meteor-ex-n where n is the number of the build to track the output of the build.
Deployment happens automatically once the new application image is available. To monitor its status either watch the web console or execute oc get pods to see when the pod is up. Another helpful command is
$ oc get svc
This will help indicate what IP address the service is running, the default port for it to deploy at is 8080. Output should look like:
NAME CLUSTER-IP EXTERNAL-IP PORT(S) SELECTOR AGE
meteor-ex 172.30.249.251 <none> 8080/TCP deploymentconfig=nodejs-ex,name=myapp 17m
An OpenShift route exposes a service at a host name, like www.example.com, so that external clients can reach it by name.
DNS resolution for a host name is handled separately from routing; you may wish to configure a cloud domain that will always correctly resolve to the OpenShift router, or if using an unrelated host name you may need to modify its DNS records independently to resolve to the router.
After logging into the web console with your account credentials, make sure you are in the correct project/workspace and then click Create route.
This could also be accomplished by running:
$ oc expose svc/meteor-ex --hostname=myapp-myproject.apps.thedigitalgarage.io
in the CLI.
Now navigate to the newly created Meteor web app at the hostname we just configured.
To take a look at environment variables set for each pod, run oc env pods --all --list.
You should now have a Meteor welcome page rendered via AngularJS.
Assuming you used the URL of your own forked repository, we can easily push changes and simply repeat the steps above which will trigger the newly built image to be deployed.