Rps Html

Standard Workflow

1. Fork to your own account.
2. Clone to your computer.
3. In the GitHub Desktop app, create a branch for your work.
4. Open the entire folder you downloaded in Atom.
5. Make your first change to the code. (You could modify this README.md file by adding your username next to the project in the heading, for example.)
6. In the GitHub Desktop app, create a commit. You must type a "summary"; "description" is optional.
7. Click Publish. Verify that your branch is now visible on your fork at GitHub.com in the "Branch" dropdown.
8. Commit and Sync often as you work.
9. Make new branches freely to experiment! You can always switch back to an older branch using the dropdown in the Desktop App, and all of your files will instantly snap back to their older state. So, when in doubt, create a branch, especially before starting on a new task.
10. You don't need to merge back into your master branch; in the end, just stay on whatever your best branch is. (In the real world, you would ultimately merge your best branch back into your master branch and deploy it to your production server.)
11. Run rails grade as often as you like to see how you are doing.
12. You can push commits and rails grade right up until the due date.
13. If you have a question about your code, a great way to get feedback is to open a Pull Request. After creating it, if you include the URL of your Pull Request when you post your question, reviewers will be able to easily see the changes you've made and leave comments on each line of your code with suggestions.

Project Specific Instructions

1. cd into the folder you downloaded.
2. bundle install (or bundle for short)
3. rails server (or rails s for short)