You are working for a company developing an E-Commerce Application. Your team is working in a service-oriented architecture, meaning the front and back ends of this application are separate and communicate via APIs. Your job is to expose the data that powers the site through an API that the front end will consume.
Visit the site »
Report Bug
·
Request Feature
The Rails Engine API is built with Ruby on Rails using a relational database. Project management was completed using Agile methodologies and scrum ceremonies. As for testing, GitHub Actions was used for continuous integration and continuous deployment with unit testing completed via RSpec and SimpleCov.
Follow the instructions listed below to get the application up and running.
- Clone the repo
git clone git@github.com:ozzman84/rails-engine-api.git
- Run bundle
bundle install
- Run migrations
rails db:{create,migrate,seed}
See the open issues for a full list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
| Back-end Team |  |
 |
|---|---|---|
| Ozzie Osmonson | link | link |