The Bitnami MEAN Stack provides a complete development environment for the leading noSQL database, MongoDB. It includes the latest stable release of MongoDB, Express, Angular, Node.js, Git, PHP and RockMongo.
Why use the Bitnami MEAN Stack?
Bitnami makes it easy to run MEAN in the cloud, locally or virtually. The Bitnami MEAN Stack is:
We track every release of MEAN and update our stack shortly after it's released.
If serious security issues are discovered, we provide new versions of MEAN as soon as possible, often within hours of the availability of a fix.
With Bitnami, you get the same software stack and configuration regardless of where you are deploying MEAN or other Bitnami Applications. This makes it easy to migrate between different platforms.
With the Bitnami MEAN Stack compiling, configuring and all of its dependencies are taken care of, so it works out-of-the-box.
Reviews of Bitnami MEAN Write a Review →
Can I know how my status I. Bitnami ??? Since the cloud engine and setting are wrong I confuse and don know what should do please support and give me some instruction and help for my status thanks a lot
Instructions were mostly old but could read in a couple of other places and install. I ended up creating my own video with easy to follow instructions - search on youtube for "Setting up MEAN stack application on Amazon Web Service (AWS)"
From a ~beginner (lots of code experience but no back-end) perspective, this stack has been a massive headache. Getting the stack to display on port 3000 is relatively simple after you figure everything out. When they tell you to run the program ./bin/www, it should say node ./bin/www so that you can exit out of it with Ctrl+C, if you do not run it that way you have to use ctrl+z, which instance, but keeps node running causing errors if you try and reload it. I have spent a week and a half @ 10-12 hours per day getting my server up and using this config (the ++ is that everything is configured for me, the -- is that I have (or had) no idea what so many things do in the environment. The documentation is good to install it, but when you want to actually deploy an app using the express project folder they tell you to build, on something other than port 3000, have fun figuring that out. The bitnami splash html file is fun to find (/opt/bitnami/htdocs/). Jade sucks balls, they should use something that can read .html natively, and isn't so sensitive to indentation, so you can migrate pages you have created without having to format everything to jade. Like I said, after a week + of trying to figure this out, I am still no further really (other than a crap ton of new knowledge, but none of bitnami's doing), I can get the server going with static html files (no thanks to the stack documentation) by calling "node ./bin/www" and having edited the app.js to include express.static, the main start page is still located in an /htdocs/ folder and not linked to project folder (an still have not figured out how to point to the project bin/www as the main start page).. In 2 months, this stack might be good if I understood how each piece worked individually, and was able to edit config files to make it do what I want, and to know where everything goes etc., but then why use a stack? I was under the impression this was install, upload, and go (even though it is "beta" which just means bugs to me)...
Documentation is terrible. Even deploying a simple mean stack website can be frustrating. The bitnami website can not find the vm i got through google cloud either. What a waste of time.
First I downloaded the VMWare image and after a quick BIOS change on my laptop, got that up and running in minutes.
After that, I decided to get the installer and install on my new Ubuntu 16.04 LTS VM, so that I can have the windowed UI, etc and once again, was up and running successfully in minutes!