• Install Docker from Docker's website.
• Clone this repo from your terminal with git clone https://github.com/PantherHackers/rails_site.git.
• Go to project (cd rails_site).
• Run docker-compose run rails bundle exec rake db:create db:migrate and wait for the containers to build.
• Copy .env.example into .env. cp .env.example .env.
• Fill in the appropriate values in .env if you will be using any of the resources (e.g. the Github API).
• If you want to populate the blog posts:
  • Create your own Github API key with the public_repo permission.
  • Add the token to the .env file under GITHUB_API_KEY.
  • Run docker-compose run bundle exec rake posts:import
• Run docker-compose up.
• Wait for the Docker images to start up.
• Go to localhost:3000.

• If you change the Gemfile, make sure to rebuild the Docker container with docker-compose build before running docker-compose up again.
• To run commands within a container (to use rake, rails, or mysql), you need to use docker-compose exec <container> <shell command>, where <container> can be rails or db depending on whether you want to access the Rails app or the MySQL database.

• In Unix systems, you can setup aliases in your .bashrc or .zshrc file to help type container commands faster:
  • alias ddb='docker-compose exec db'
  • alias dr='docker-compose exec rails'
  • alias dbe='docker-compose exec rails bundle exec'

• Feel free to play with the project, modify files, and refresh the website to see changes.
• If unfamiliar with Rails, check out their getting started guide.

If you have any questions, the instructions in this document are not clear, or the setup does not work for you, feel free to contact Luis on Slack (@luis) or shoot him an email at [email protected]