docker run -i -t --name mymeanjs --link mymongodb:db_1 -p 80:3000 maccam912/meanjs:latest bash
I recently had come across this article, Running a MEAN web application in Docker containers on AWS. I'm researching containers for development work that can start in one place and then migrate into production as a docker file. So I spent an hour getting this up and running. In addition to the steps in the article, I found a few extra steps might make things work better.
1. Update Node. The maccam912 VM has an older version of node. It's an easy fix.
Having driven a 1966 VW bug, 1969 van, 1972 bug, dasher, 72 van, in my early years, then Lynda and I drove the van and Penelope till we got Goldie. Then Goldie died and we got snowball. Later we bought shadow our most expensive car to date. Shadow and Goldie served us for years till we got hit heading to La Verne. That lead us to Lexie. Lexie served is well until a furlough Friday when her transmission failed.
Going through these hundreds of snapshots, I'm reminded about some of our design principlles in going from the old house to new house. No 70's wallpaper, no vinyl floor patterns, easy cat cleanup, no electric range, no brown tile, no clutter, no slipping on bricks, no dark woods, no carpet, filtered air, filtered water, better and more lighting.
Even the cats got a new wall library out of the deal.
After we moved the propane tank, we knew we wante to stop using the wood burning stove and the old fireplace was never utilized. So, we did a fireplace insert with gas and we've never regretted it. I've updated the thermostat to work with our home automation tools and we can heat the front room in 10-15 mins. We used Woodstove and Sun and we'll use them again for the firepit supplies when that project gets scoped.
I finally upgraded my Ubuntu 10.04 LTS Linode to Ubuntu 14.04 LTS. Had a heck of a problem with what should have been a very simple upgrade.
One of my objectives with migrating data out of Drupal and into a MEAN stack app is for easier management of downstream requests for JSON data. We want to take advantage of the built in functionality of the MeanJS stack, and here's a simple exaple.
In this use case we wish to expose articles to some other app who will make a HTTP GET request for all the articles or just one.
In app/controllers/articles.server.routes.js, we need to add entries for the two functions we'll allow via GET.
Well, I'm no expert but here's a tip that might save you some time. I have a Drupal databae outputting valid GeoJSON data. Our data looks like this:
I took some time to try MeanIO over the past few days. While I ended up coming back to MeanJS, I drew some conclusions that might be helpful.
Here's the use case. I wanted to take a GeoJSON file, load it into a boilerplate MEAN stack, generate CRUD files and get a basic app tested. Ideally, I'd want to tweak the layouts, menus, and boilerplate HTML as well as use bower to add js libs that add functionality.
Update 5/1/15 - On a different instance of Mongo, I had run the command noted below and got errors. However, this worked:
mongoimport --db mean-dev -c points --file "points.geojson" --jsonArray
Let me save you the hours lost in trying to figure out getting GeoJSON features into individual documents in a collection versus one document with nested features.
MongoDB 3.0.2. Valid GeoJSON file full of 809 features.
Using this code:
mongoimport --db test --type json --file ./'mobilemaps.geojson'