Our practice is to deploy to Heroku using the release branch of the repository.
To deploy to Heroku, run git push heroku release:master. You may also need to run heroku rake db:migrate if you have added migrations since you last deployed to Heroku. Run heroku rake db:seed if you want to reseed the database.
https://www.pivotaltracker.com/n/projects/2317544
This app creates a website for the Berkeley Student Food Collective which allows their customers to explore their products and vendors and allows the volunteers to upload products and vendors for the customers to view.
The Berkeley Student Food Collective (BSFC) needed a way to better express why they choose specific products and vendors to populate their store with. This website was designed to create a way so they can better explain those choices to their customers. Pages with '/admin' allow volunteers at BSFC to put specific products and vendors on their website. Other pages allow BSFC customers to view those products and vendors.
Must have Ruby 2.4.0 to run this project locally. Run bundle install --without production to import all gems and rake db:setup to initialize the database.
Set up as a standard rails app. Notable choices include:
- All views which are associated with paths prepended with "admin" are in the folder "admin" under views.
- Partials shared among multiple views live in the "application" folder under views.
The main three models are Vendor, Product, and Tag. Certification, Nutrition, Ownership, and Packaging inherit from Tag and therefore all live in the Tag table in the database with different types. They each have a "belongs to" relationship with either a Vendor or Product model. Product_Certification, Product_Nutrition, Product_Packaging, and Vendor_Ownership are models linking the two tables they mention.
Use bundle exec cucumber to run all cucumber tests.
- How to update the banner image on the discovery page: Go into app/assets/images and add the image file. Rename it to discovery_image.jpeg