MEAN stack is a full a full-stack JavaScript framework based on MongoDB, Express JS, Angular JS and NodeJS, which can help you rapidly develop your applications.
In minutes, you can bring up a MEAN development stack on Google Compute Engine. With click-to-deploy, you can:
- Get started quickly with development
- Kick start your NodeJS development.
By default, the completed deployment includes one development server (virtual machine instance) with the MEAN stack installed:
After your MEAN stack is running, you can SSH to your instance to do further configuration and testing.
When you are done with your development stack, click the Delete stack button on the Click-to-Deploy web page. This will bring down all instances and destroy the associated data disks.
Objectives
- Deploy MEAN stack on a Google Compute Engine virtual machine instance
- Configure your deployment
Quickly deploy MEAN stack on Compute Engine
The Google Developers Console provides a simple interface that you can use to quickly configure your MEAN stack deployment.
-
In the MEAN stack click-to-deploy page in the Google Developers Console , specify your configuration settings or use the default values.
-
Click Deploy MEAN Development Stack
-
Optional: Install the Cloud SDK to be able to connect to your virtual machine instance when deployment finishes.
The deployment can take a few minutes, when it finishes, you can follow the
provided link to list your virtual machine instances or you can launch the
sample app at
http://<your-external-ip-address>:3000/
. You can connect to your
instances by using the
gcutil ssh <instance-name>
command to perform further
configuration or to perform other tests such as testing.
When you are finished with the virtual machine instance, you can click the Delete Stack button in the Developers Console to stop all instances, destroy the associated data disks, and delete the instances.
Next steps
You might also want to learn about how the MEAN stack was deployed. You can learn how Deployment Manager was used and extend that knowledge to your own projects.
Next: Learn how the MEAN stack was deployed
Troubleshooting
If a deployment fails to complete successfully, check the error message in the Developers Console. If the problem is a CPU quota issue or other problem that you can correct, delete the deployment, correct the problem, and try again.
If the error message on the Developers Console does not provide
sufficient detail about the failure, check the Deployment Manager output on
the virtual machine instances that were launched. On each instance, there will
be a directory
/gagent/metaOutput
with a set of numbered files:
stdoutN.txt
,
stderrN.txt
,
exitcodeN.txt
. Each set of such files corresponds to the
sequenced command that was executed by Deployment Manager for your deployment
on that instance.
To get a list of your compute engine instances, check the Compute Engine list of virtual machine instances in the Developers Console or run the following command:
$ gcloud compute instances list -l
To ssh to an instance:
$ gcloud compute ssh <instance> --zone=<zone>
If you have problems that you cannot resolve or have questions head to Stack Overflow .