CentOS6.5(64bit)にMeanを入れてみた

Meanを構築してみました。
まだ１回しか構築してないので、ご参考程度に

とりあえず、vagrantとvartualBoxは導入済みのこと（そこらへんで探せばいろいろ出てくるので頑張れ）
vagrant initからスタートします。
MeanのVagrantファイルフォルダ作って

$ vagrant init CentOS6.5
$ vagrant up

■Vagrantファイルの編集
共有フォルダを作成（ローカル）

以下vagrantファイルの設定(ご参考までに)--------------------------------------------------------

# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "CentOS6.5"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080
  config.vm.network "forwarded_port", guest: 3000, host: 3000
  config.vm.network "forwarded_port", guest: 80, host: 80
  config.vm.network "forwarded_port", guest: 443, host: 443

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"
  config.vm.synced_folder "~/Documents/Mean", "/home/vagrant/mean_project"

  # If true, then any SSH connections made will enable agent forwarding.
  # Default value: false
  # config.ssh.forward_agent = true

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.

  # Enable provisioning with CFEngine. CFEngine Community packages are
  # automatically installed. For example, configure the host as a
  # policy server and optionally a policy file to run:
  #
  # config.vm.provision "cfengine" do |cf|
  #   cf.am_policy_hub = true
  #   # cf.run_file = "motd.cf"
  # end
  #
  # You can also configure and bootstrap a client to an existing
  # policy server:
  #
  # config.vm.provision "cfengine" do |cf|
  #   cf.policy_server_address = "10.0.2.15"
  # end

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file default.pp in the manifests_path directory.
  #
  # config.vm.provision "puppet" do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "site.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision "chef_solo" do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { mysql_password: "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision "chef_client" do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end

————————————————————
基本#無い部分を編集すれば良い

一旦再起動

$ vagrant halt
$ vagrant up
$ vagrant ssh

lsコマンドでフォルダができていると思う
そのフォルダがローカルと仮想で共有されるフォルダになる

■npmの導入
とりあえずスーパユーザに

$ su

pass:vagrant

epelリポジトリを追加して、yumコマンドを強化(64bit版) *32bit版は知らね

$ rpm -ivh http://ftp.riken.jp/Linux/fedora/epel/6/x86_64/epel-release-6-8.noarch.rpm
$ yum install nodejs npm --enablerepo=epel

適当にy打ってインストール

■Meanの導入

$ npm install -g mean-cli

■gruntの導入

$ npm install -g grunt-cli

■MongoDBの導入

$ vi /etc/yum.repos.d/mongodb.repo

で以下を記述しセーブ-----------------

[mongodb]
name=MongoDB Repository
baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64/
gpgcheck=0
enabled=1

$ sudo yum install -y mongodb-org

ここでとりあえずvagrant再起動
exit>exit>vagrant halt>vagrant up>vagrant ssh>su>pass:vagrant>cd mean_project/

■適当にアプリ作ってみる

$ mean init NewTechApp
? What would you name your mean app? >Enter
? Do you prefer grunt or gulp as a taskrunner? (Use arrow keys)
❯ grunt
   gulp

gruntでEnter
何か絵が出てきたら成功

■アプリ立ち上げてみる

$ cd NewTechApp
$ npm install
$ grunt

ここで落ちるはず
bowerとかいう代物のjqueryが足りてないらしい
ということでインストール

$ npm install -g bower
$ bower install jquery

以下のエラーが出る場合

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: getaddrinfo ENOTFOUND
    at errnoException (dns.js:37:11)
    at Object.onanswer [as oncomplete] (dns.js:124:16)

で、まだエラーが出る。ローカルのIPを
設定してあげないとダメみたい

$ vi config/env/development.js

debug: 'true',
hostname: '0.0.0.0', // 追加する
mongoose: {

(´・ω・｀)<むずい

■一言
参考文献なさすぎ、エラー出過ぎ。
死にかけた。が、一応初期画面までは構築できた。
多分、構築の方もかなりキツイぞこれ。。。
mongo、AngularJS、node.jsを別々に勉強してやった方が
いいのではないかと思ってきてる。。。
これを使ってrails以上に「良い！」って思える日は来るのでしょうか。。。

■参考文献
MEAN（MongoDB,Express,Angular.js,Node.js）環境を構築して簡単なアプリを作るまで
http://bibourock.hatenablog.jp/entry/2014/10/22/MEAN%EF%BC%88MongoDB,Express,Angular_js,Node_js%EF%BC%89%E7%92%B0%E5%A2%83%E3%82%92%E6%A7%8B%E7%AF%89%E3%81%97%E3%81%A6%E7%B0%A1%E5%8D%98%E3%81%AA%E3%82%A2%E3%83%97%E3%83%AA%E3%82%92%E4%BD%9C
node.jsをyumでインストールする(centos6.5)
http://qiita.com/you21979@github/items/4efd9fc4363573191b5c
CentOS6.5にMongoDBをインストールする
http://qiita.com/nownabe/items/123a8fd04ff5252b3036
Vagrantで起動したCentOSにmean環境構築して起動まで
http://qiita.com/balmychan/items/56f4526a7b47ad92cdf2

gaku様の備忘録

プログラミングとか、夢と現実と理想とか。。。

CentOS6.5(64bit)にMeanを入れてみた