Stoke Finder BE

Description

Stoke Finder BE is the backend application of the Stoke Finder project. Stoke Finder is an application designed to aid users in the creation, and discovery of new outdoor adventures based on outdoor activities the user adds to their profile preferences. The purpose is to handle the consumption and creation of API's necessary for massaging and passing data to the FE application in the Stoke Finder, properly handling user authenitcation data that is passed to the BE, and demonstrating convetional means of packaging, sending, and receiving JSON responses to and from the FE server. The storage of all sensitive data that cannot be accessed through an API consumption on the FE, will be stored in the backend database. This data will be accessible for the FE through the API end points that are created on the BE application.

Versions

• Ruby 2.7.2
• Rails 5.2.6

Gems

  #Global Scope Gems 
  gem 'bcrypt', '~> 3.1.7'
  gem 'faraday'
  gem 'bootstrap', '~> 5.1.3'
  gem 'jsonapi-serializer'
  gem 'geocoder'
  
  #group :development, :test
  gem 'pry'
  gem 'rubocop-rails'
  gem 'figaro'
  gem 'factory_bot_rails'
  gem 'rspec_junit_formatter'
  gem 'faker'
  
  #group :test
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'rspec-rails'
  gem 'shoulda-matchers'
  gem 'simplecov'
  gem 'vcr'
  gem 'webmock'

Local Setup

1. Fork & Clone the repo

$ git clone [email protected]:stoke-finder-2110/stoke-finder-backend.git

2. Navigate to the directory

$ cd stoke-finder-backend 

3. Install gem packages:

$ bundle install

4. Update gem packages:

$ bundle update

5. SRun the migrations:

$ rake db:{drop,create,migrate,seed}

Schema

Learning Goals

• Create two independent applications hosted on Heroku that successfully communicate with each other
• Follow SOA convention
• Use serializers to package, and send JSON responses
• Implement OMNIAUTH authentication
• Implement sessions after user sign in
• Test API exposure
• Consume necessary APIs

Project Contributors