30 September 2020
This is a practice exercise for Epicodus to practice working with nested classes, routing, and test-driven development in Ruby. The original instructions include:
Create a website for a local festival in the woods. A user should be able to create, read, update and delete a Stage and should also be able to create, read, update and delete an Artist. Artists belong to Stages. For the purposes of this project, an Artist can only perform on a single Stage - otherwise, we'd need to use a many-to-many relationship, which is much more complicated.
Start with unit tests and get all tests passing before starting on integration testing and Sinatra. Make sure integration tests cover all the ways a user may navigate through your pages.
- Clone this project using the 'git clone' command in terminal/command line.
- Navigate to the cloned folder and run 'bundle' in your command line.
- Open the cloned repo in a text editor of your choice.
- To run tests: While in the root directory of the project, run 'rspec' in your command line.
- To run the app.rb file, run 'ruby app.rb' in the terminal.
There are no known bugs at this time.
- HTML5
- CSS/Bootstrap
- JavaScript/jQuery
Copyright (c) 2020 Alma Frankenstein, Donny Mays, and Vanessa Stewart
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.