tomit4
/
siimee
forked from fyindr/siimee
Watch 1
Star 0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
54 Commits
1 Branch
Tree: 2598a2829c
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '2598a2829c'
${ noResults }
siimee/backend
j 2598a2829c :sparkles: adding http requesting of form questions | generating forms on response 4 years ago
..
db :sparkles: adding http requesting of form questions | generating forms on response 4 years ago
lib :sparkles: adding http requesting of form questions | generating forms on response 4 years ago
server :sparkles: added ability to send responses and creat new profile 5 years ago
tests :fire: more linting 5 years ago
.eslintrc :recycle: just cleaning up config stuff 5 years ago
.nycrc :recycle: just cleaning up config stuff 5 years ago
.prettierrc :pencil: added formatting and style rules for eslint and prettier 5 years ago
README.md :gear: altering response_key schema | :pencil: outlined backend object use 4 years ago
knexfile.js :recycle: formatting all the things 5 years ago
package-lock.json :recycle: formatting all the things 5 years ago
package.json :recycle: formatting all the things 5 years ago

README.md

siimee backend API

An API for the siimee application

:white_check_mark: Prerequisites

You will need…

Node.js 14+

:package: Installation

  1. Install dependencies with npm install
  2. Copy the environments sample file from ./server/.env.sample and rename it to ./server/.env
  3. Fill out your database connection details in ./server/.env
  4. A test database container is provided and can be started with docker-compose --env-file ./backend/server/.env up -d
  5. Populate some basic tables for your database using npx knex migrate:latest

:package: Migrations

We use Knex.js,which comes with a couple nice database migration and seeding tools. Migrating tracks changes in schema. Migration steps are contained in the ./db/migrations folder. Seeding adds dummy data once our database tables have been created and schemas are set. Starting seed steps are contained in ./db/seeds and use the mock.js file as the main dummy data source.

Migrating

  • Run npm run migrate to run all migrations and establish the base schema
  • Run npm run unmigrate to roll back one migration

Seeding

  • Run npm run seed to seed the database with dummy data

Restarting

Since we can’t unseed the database, it’s best to destroy the dev database and rebuild it.

  1. Stop the database by navigating to the project root directory cd ../ and running docker-compose down
  2. Destroy the database volume docker volume rm siimee_siimee_db. BE CAREFUL.
  3. Restart the database while still at the project root with docker-compose --env-file ./backend/server/.env up -d
  4. Recreate schemas and tables but navigating to ./backend and running npm run migrate
  5. Reseed the dummy data with npm run seed

:electric_plug: Run

  1. Run npm run start to start up the server
  2. Check http://localhost:3001/documentation to see the interactive API documentation

:robot: Deployment

TBD

:pill: Tests & Code Quality

Tests are run with AVA with code coverage reporting via nyc. Look at the example test for ideas, as well as the ava documentation

  • Run tests with coverage report with npm test

:heart: Built With