okada-takuya / nomnichi

Nomura Laboratory's Blog System

What is nomnichi?

nomnichi is a Nomura Laboratory’s blog system implemented in Ruby on Rails.

Setup Ruby environment

Ruby	2.2.3
Rails	4.2.4

I recommend you to install new Ruby and Bundler on the top of Rbenv before install nomnichi.

1. Install rbenv + ruby-build (check https://github.com/sstephenson/rbenv#basic-github-checkout for details)

   $ git clone https://github.com/sstephenson/rbenv.git ~/.rbenv
   $ git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build
   # Edit your shell dot files to add some path and environment variables.
       

2. Install Ruby and Bundler

   # Install ruby 2.2.3
   $ rbenv install 2.2.3
   
   # Installation check
   $ rbenv global 2.2.3
   $ ruby -v # -> You will see: ruby 2.2.3...
   
   # Install bundler for your new Ruby
   $ gem install bundler
   
   # Activate bundler
   $ rbenv rehash
   
   # Get back to your system default Ruby if you want
   $ rbenv global system # say, /usr/bin/ruby
   $ ruby -v
       

Install nomnichi

Clone nomnichi

1. Clone nomnichi from GitHub

   $ git clone [e-mail]:nomlab/nomnichi.git ~/Programs/nomnichi
       

2. Setup to use installed ruby

   $ cd ~/Programs/nomnichi
   $ rbenv local 2.2.3
   $ ruby -v # -> You will see: ruby 2.2.3...
       

Setup config files

You can setup site-local config files interactively by invoking bin/install.sh:

$ bin/install.sh

Or, you can edit config files by hand:

1. Install vendor/bundle stuffs

   $ bundle install --path vendor/bundle
       

2. Setup secret key

   $ bundle exec rake secret # -> You will see: foobarbuz... Copy the string.
   $ cp config/secrets.yml.template config/secrets.yml
   $ vim config/secrets.yml # -> Replace all <SECRETKEY> with the string outputted
       

3. Setup GitHub OmniAuth

   $ cp config/application_settings.yml.template config/application_settings.yml
   $ vim config/application_settings.yml # -> set client_id, client_secret, allowed_team_id
       

4. Setup DB

   $ bundle exec rake db:migrate
   $ bundle exec rake db:migrate RAILS_ENV=production
       

Launch nomnichi

development

You can launch server by invoking bin/server.sh:

# start
$ bin/server.sh start dev

# stop
$ bin/server.sh stop

Or, you can take these procedures by hand:

# start
$ export RAILS_ENV="development"
$ export RAILS_RELATIVE_URL_ROOT='/lab/nom'
$ export RAILS_SERVE_STATIC_FILES=true
$ bundle exec rails server -b 0.0.0.0 -p 3000 -d -e "$RAILS_ENV"
$ open http://localhost:3000/lab/nom

# stop
$ kill $(cat tmp/pids/server.pid)

production

You can launch server by invoking bin/server.sh:

# start
$ bin/server.sh start pro

# stop
$ bin/server.sh stop

Or, you can take these procedures by hand:

# start
$ export RAILS_ENV="production"
$ export RAILS_RELATIVE_URL_ROOT='/lab/nom'
$ export RAILS_SERVE_STATIC_FILES=true
$ bundle exec rake assets:precompile RAILS_ENV="$RAILS_ENV"
$ bundle exec rails server -b 0.0.0.0 -p 54321 -d -e "$RAILS_ENV"
$ open http://localhost:54321/lab/nom

# stop
$ kill $(cat tmp/pids/server.pid)