🍕 Open Sauced Insights API 🍕

The path to your next Open Source contribution

• api.opensauced.pizza
• beta.api.opensauced.pizza

In order to run the project we need the following software binaries installed on our development machines:

• node>=16.7.0
• npm>=8.0.0
• docker>=20.10.12

Before setting up your local PostgreSQL database, a Supabase instance should be created. To do this, follow these steps:

1. Create a new Supabase project: Visit Supabase and create a new project.

2. Set Environment Variables in .env file: Once your project is created, Supabase will provide a URL and an API key. Set these in your project's .env file:

SUPABASE_URL=your_supabase_url
SUPABASE_API_KEY=your_supabase_api_key
SUPABASE_JWT_SECRET=your_supabase_jwt_secret
API_DOMAIN=your_api_domain

Replace your_supabase_url, your_supabase_api_key, your_supabase_jwt_secret, and your_api_domain with the actual values provided by Supabase and your project's settings.

A PostgreSQL Docker container has been set up to facilitate local development. After navigating to the dev/ directory, this container can be set up as follows:

1. Obtain SSL Certificates:
For secure SSL communication, you need a pair of SSL certificates: server.crt and server.key. You can generate self-signed certificates by using OpenSSL:

openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365 -nodes -subj "/CN=localhost"

Please note that this generates self-signed certificates which should only be used for local development.

2.Build the Docker image:

docker build -t my_postgres_image -f Dockerfile.local-postgres .

This command will build the Docker image using the Dockerfile in the current directory. The previously generated SSL certificates will need to be in the same directory as the Dockerfile.

3.Run the Docker container:

docker run --name my_postgres_container -p 25060:5432 -d my_postgres_image:latest

This command will start a new Docker container named my_postgres_container, mapping port 25060 on your local machine to port 5432 on the Docker container.

Once the database is stood up, can use the dev/apply-migrations.sh script to apply all the migrations in the migrations/ directory.

To install the application:

npm ci

To start a local copy of the app on port 3001:

npm run start:dev

For running the test suite, use the following command. Since the tests run in watch mode by default, some users may encounter errors about too many files being open. In this case, it may be beneficial to install watchman.

npm test

You can request a coverage report by running the following command:

npm run test:coverage

For writing tests, the rule is move business or service logic to the lib folder and write unit tests. Logic that needs to be in a React component, then leverage tools like Cypress or Vitest mocking to write tests.

A development preview can also be run from docker:

docker build -t api.opensauced.pizza .
docker run -p 8080:3001 api.opensauced.pizza

Alternatively you can pull the production container and skip all builds:

docker run -dit -p 8080:3001 ghcr.io/open-sauced/api.opensauced.pizza

To check the code and styles quality, use the following command:

npm run lint

This will also display during development, but not break on errors.

To fix the linting errors, use the following command:

npm run format

It is advised to run this command before committing or opening a pull request.

When making API changes, make sure to run npm run generate:swagger to generate any new Swagger document bits.

We have a couple of scripts to check and adjust missing types.

In order to dry run what types would be added to package.json:

npm run types:auto-check

In order to add any missing types to package.json:

npm run types:auto-add

A production deployment is a complete build of the project, including the build of the static assets.

npm run build

This API integrates with the pizza service to accept requests for ingesting commits to the database. The environment variables for this are:

PIZZA_OVEN_HOST="http://example.com"
PIZZA_OVEN_API=80

Click the image to see the schema diagram full documentation.

We encourage you to contribute to Open Sauced! Please check out the Contributing guide for guidelines about how to proceed.

Got Questions? Join the conversation in our Discord.
Find Open Sauced videos and release overviews on our YouTube Channel.

Below is visual representation of our code repository. It is generated by Octo Repo Visualizer.

This visualization is being updated on release to our default branch by our release workflow.

MIT © Open Sauced