Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

Repository files navigation

SpeakHer Backend

This project is a prospective backend for https://speakher.jp. It is not currently used, but we may resume it in the future.

This project contains is a Ruby on Rails API app, serving REST endpoints to fetch and manipulate the data.

Specs:

  • Web server: Puma (default for Rails apps)
  • Database: PostgreSQL
  • Architecture: MVC, where Views are the API response templates (JSON)
  • Host/deploy: Heroku

If you're new to Ruby on Rails, here's some useful reading to get started (you can ignore most parts related to views and ERB files, since this is an API only app):

Local setup

System dependencies:

  • ruby 2.7.2 (rbenv is recommended to install and manage ruby versions)
  • Bundler ($ gem install bundler)
  • PostgreSQL Database (install and make sure it's on your PATH)
  • Some gems on Gemfile may require extra dependencies. If you run into any errors when running bundle install below, follow the instructions on the error messages to install the missing dependencies

Setup the app on your local environment:

  1. Clone the project or your fork of the project on your local machine
  2. Install the dependencies
$ cd speak-her-db/server
$ bundle install
  1. Setup and seed the database. This will seed the database with the core data like Locations, Languages and Topics.
$ rails db:create db:migrate db:seed
  1. If you need, you may populate the database with a fake list of speakers
$ rake mock:speakers
  1. Run the rails server
$ rails s

Database manipulation

If you need to reset your database from scratch, you can always run

$ rails db:drop db:create db:migrate db:seed

Don't ever run this command in production.

As a general rule do not edit existing DB migrations (under db/migrations). Migrations are a registry of how we altered the database over time, which means that each migration represents a state/version of the database schema at some point in time and should not be altered.

Rails also keep a pointer to the last migration you ran, so when you pull the project and there are new migrations, you should run rails db:migrate to apply the new migrations. That's also why if there is a change on an old migration that was already executed, it will not be applied when you run rails db:migrate, unless you drop your database and recreate it from scratch.

To alter the database schema in any way (create or alter tables, create indexes, etc) you must create a new migration with the changes you need. Read more about Rails migrations on RailsGuides.

Checking or updating the seed data

You can re-seed the core data (Languages, Topics, Locations) at any time running

$ rails db:seed

This command will load the json files on the db folder and either create the records if they don't exist yet or update the attributes if the record already exists (find by name match). You can check or update the behavior of this task on db/seeds.rb.

To add a fake list of speakers, you can use the mock speakers rake task:

$ rake mock:speakers

You can check or update the behavior of this task on lib/tasks/mock_data.rake. You can change the mock data on lib/tasks/speakers.json

Checking or updating records using the Rails console

Access the rails console

$ rails c
Running via Spring preloader in process 86090
Loading development environment (Rails 6.0.3.2)
irb(main):001:0>

The Rails console is basically a ruby console loaded with your development environment (classes, models, db connection), so you basically run any Rails code from there. For example, you can manipulate your data using your models and ActiveRecord methods:

irb(main):001:0> Topic.count
=> 47
irb(main):002:0> Topic.create!(name: "My new topic")
=> #<Topic id: 48, name: "My new topic", name_ja: nil, created_at: "2021-01-01 11:12:24", updated_at: "2021-01-01 11:12:24">
irb(main):003:0> Topic.count
=> 48
irb(main):004:0> Topic.last
=> #<Topic id: 48, name: "My new topic", name_ja: nil, created_at: "2021-01-01 11:12:24", updated_at: "2021-01-01 11:12:24">

You can check how to use the basic ActiveRecord CRUD methods on RailsGuides.

Cheking & updating API endpoints

Check the API routes typing this command on your terminal

$ rails routes

Alternatively, when your server is running, you can see all available routes at localhost:3000/rails/info/routes. Response formats are under the /views folder. More info:

Writing & running tests

Rails apps come built-in with Minitest. If you're new to Rails or testing, read the RailsGuides for Testing Rails Apps.

All tests are under the test folder. You can also check and update mock test data under test/fixtures.

Run tests locally with the following commands:

$ rails test ==> run all tests
$ rails test [filepath] ==> run a specific test file
$ rails test [filepath:line_number] ==> run a specific test case defined at line_number of the file

How to deploy or access production

This API server is deployed on Heroku. To trigger a manual deploy or run any commands on the production server, you will need to install the Heroku CLI and follow some of the commands below. Only members of the SpeakHer team on Heroku have access to production and triggering deploys.

Once you have Heroku CLI installed, authenticate your Heroku account with:

$ heroku login

Connect your local repo with the Heroku remote:

$ heroku git:remote -a speak-her-jp

From the repo root folder (outside /server), run the following command to deploy the master branch to Heroku:

$ git subtree push --prefix server heroku master

WIP: CD is not configured yet. We'll condigure automatic deploys from github master branch soon.

Useful CLI commands:

Further reading:

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages