Skip to content

Latest commit

 

History

History
60 lines (49 loc) · 1.43 KB

README.md

File metadata and controls

60 lines (49 loc) · 1.43 KB
Raw

Microverse Gitpod Configuration

Benefits Of Using Gitpod Instead Of Your Local Machine

  • Consistent Performance
    • After the first boot-up and installing editor extensions, Gitpod is consistent, Zoom is not stressing it's CPU, Chrome is not devouring it's RAM.
  • Unlimited Internet
    • Gitpod has 1Gbps download/upload speeds, which means: No longer are you waisting your time and money (assuming capped data plan) to install Ruby, Node packages for every project.
  • Resilient
    • Your power might go out, maybe you forgot to commit and push your changes, Gitpod does not care, it's still running.

Preinstalled Tools

  • Apache2
  • C++
  • Chrome (including chromedriver)
  • ESLint
  • Firefox (including geckodriver)
  • Git
  • Go
  • Hint
  • Java
  • Lighthouse
  • Nginx
  • Node
  • NPM
  • NVM
  • PHP
  • PostgreSQL
  • Python
  • Rails
  • RSpec
  • Rubocop
  • Ruby
  • Rust
  • RVM
  • SQLite
  • Stylelint
  • Yarn

How To Utilize

  • Copy the .gitpod.yml file (with its contents) to the root folder of your Git project directory
  • Commit and push to GitHub
  • Open your GitHub project in Gitpod:
    • Example: https://gitpod.io/#https://github.com/s0kil/microverse-gitpod-test-rubyonrails

Ruby on Rails Configuration

In order for Rails server to allow Gitpod preview access, let's configure it.

In the config/environments/development.rb file, add the following:

Rails.application.configure do
  config.hosts = nil #<-- Add This Line
end

Restart the Rail server.