gobeam / truthy

Open source headless CMS API written using NestJS, that has pre built modules like User Management, Role Management, Permission Management, Email Module, Account Settings, OTP, Throttling, RBAC support, Localization, and many more.
MIT License
498 stars 89 forks source link
api api-rest awesome-nestjs-boilerplate boilerplate cms demo headless-cms nestjs nestjs-api nestjs-api-starter nestjs-backend nestjs-boilerplate nestjs-demo nodejs postgresql rbac-authorization realworld-backend throttle-requests typescript user-role-permission
Truthy Logo

Truthy CMS (NestJS Headless API)

This repository is Backend API part of Truthy CMS written in NestJS. For Frontend please visit https://github.com/gobeam/truthy-react-frontend. This project includes API for Authentication, User Management, Role Management, Permission Management, Email Module, Account Settings, OTP, RBAC support, Localization, and many more.


GitHub package.json version Workflow test GitHub Lines of code Open Source Helpers

Buy Me A Coffee

Created by Roshan Ranabhat (gobeam) and maintained with ❤️ by an amazing team of awesome developers.

Check Live code deployed here: Backend API Docs: Swagger Docs Frontend: Truthy CMS

Truthy CMS

## Table of Contents - [Getting Started](#getting-started) - [Prerequisites](#Prerequisites) - [Available Scripts](#available-scripts) - [Setup](#setup) - [Docker Setup](#docker-setup) - [File Structure](#file-structure) - [Application Security](#application-security) - [Contributing](#contributing) - [Sponsors](#sponsors) - [License](#license) - [Acknowledgement](#acknowledgement) --- ## Getting Started This project was created to help developers by bootstrapping basic modules that need to be present while creating a standard CMS. The main motto of this project was to save precious time while developing CMS and focus more on the core part. This project is trying to follow the best possible standard to make it optimized and production-ready. Hope you like it.
If you love it don't forget to share your experience. If you want to contribute to the Truthy CMS in any way like API, Frontend, Design, Logo you're more than welcome to do so. Our plan is to make this no. 1 CMS maintained by opensource community. --- ## Prerequisites NodeJS https://nodejs.org/en/ Typescript https://www.typescriptlang.org/ PostgresQL https://www.postgresql.org/ Redis https://redis.io/ --- ## Available Scripts ### npx truthy-api This commands downloads the latest version of truthy i.e NestJS Truthy CMS backend API. In the project directory, you can run: ### `yarn start:dev` Runs the app in the development & watch mode.
Open [http://localhost:7777/api-docs](http://localhost:7777/api-docs) to view swagger API docs in browser (only available in development mode).
You will also see any lint errors in the console. ### `yarn build` Builds the app for production to the `build` folder.
### `yarn lint` Lints all the files inside src,apps,libs,test folders and shows the results. ### `yarn format` Formats all the files inside src using prettier with config provided in .prettierrc ### `yarn format` Formats all the files inside src using prettier with config provided in .prettierrc ### `yarn coverage` Runs coverage test command and creates coverage folder with detail report which can be checked with: ```bash yarn coveralls ``` ### `yarn orm-create migration_file_name` Uses Type ORM to create a migration file. `migration_file_name` is Migration file name to be created. ### `yarn migrate` This command is used to migrate existing migration file. ### `yarn migration:rollback` This command is used to rollback migration. ### `yarn seed` This command is used to run existing seeders. --- ## Setup First, you need to install the project using npx command ```bash npx truthy-api ``` or clone it using ```bash git clone https://github.com/gobeam/truthy.git ``` **You also need to run PostgresQL for database and Redis for key-val storage which will be used for queue and throttling.** After cloning the make changes in configuration file that exists in config folder which exists in root of project. File names are named in accordance with environment you run project with. For example if you're running project in development environment you should make change in configuration of development.yml file. **Please keep in mind environment variables always overrides the config.** If you want to run locally, ```bash yarn start ``` *If you want to view swagger docs on development open http://localhost:7777/api-docs (assuming you are running application on 7777 port)* Run Migration ```bash yarn migrate ``` Run Seeders ```bash yarn seed ``` Rollback Migration ```bash yarn migration:rollback ``` --- ## Docker Setup **If you want to run project without docker you will not need to create .env file** If you want to use **Docker** to deploy it on production or development stage First create a .env file copying from .env.example and add environment for below parameters only since it will be used for building container using docker-compose ```env SERVER_PORT=7777 DB_PASSWORD=root DB_USERNAME=postgres DB_DATABASE_NAME=truthy DB_PORT=5488 REDIS_PORT=6399 ``` After creating env file make changes in configuration in accordance with you development environment. Follow setup guide in case you missed it. Now to run containers do ```bash docker-compose build . docker-compose up -d ``` These commands will run 3 containers for PostgresQL, Redis and Main API. To run migration on docker container ```bash docker exec -it yarn migrate ``` To run seeder on docker container ```bash docker exec -it yarn seed ``` --- ## File Structure This project follows the following file structure: ```text truthy ├── config * Contains all configuration files │ └── default.yml * Default configuration file. │ └── development.yml * Configuration file for development environment. │ └── production.yml * Configuration file for production environment. │ └── test.yml * Configuration file for test environment. ├── coverage * Coverage reports after running `yarn coverage` command. ├── dist * Optimized code for production after `yarn build` is run. ├── images * this folder is where uploaded profile images are stored. This folder is git ignored. ├── src │ └── * Folder where specific modules all files are stored │ └── dto * Data Transfer Objects. │ └── entity * Models for module. │ └── pipes * Includes validation pipes for NestJS modules. │ └── serializer * Includes serializer for model data. │ └── .controller.ts * Controller file. │ └── .module.ts * root module file for module. │ └── .service.ts * Service file for . │ └── .service.spec.ts * Test file for service. │ └── .repository.ts * Repository file for . │ └── .repository.spec.ts * Test file for repository. │ └── common * Common helpers function, dto, entity, exception, decorators etc. │ └── config * Configuration variables files. │ └── database * Database folders that includes migration and seeders file │ └── migrations * Migration folder includes all migration files. │ └── seeds * Seeds folder includes all seeders files. │ └── exception * Exception folder includes custom exceptions. │ └── app.module.ts * Root module of the application. │ └── main.ts * The entry file of the application which uses the core function NestFactory to create a Nest application instance. ├── test * Contains E2E tests ``` **Some important root files** ```text . ├── .editorconfig * Coding styles (also by programming language). ├── .env * Environment variables for docker. ├── .prettierrc.js * Formatting Prettier options. ├── .eslintrc.js * ESLint configuration and rules. ├── .docker-compose.yml * Docker compose configuration. ├── Dockerfile * Docker file for prod environment. ├── Dockerfile.dev * Docker file for dev environment. ├── tsconfig.json * Typescript configuration for application. ``` --- ## Application Security ### Throttle By default Throttle has been implemented for all API's. Redis is default driver to record throttle state data. You can easily change configuration from config files. ### Two Factor Authentication (2FA) User Will have 2FA authentication option available to be turned on or off. For 2FA time-based one-time password is used. A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. Applications like [Authenticator](https://play.google.com/store/apps/details?id=com.azure.authenticator&hl=en&gl=US), [1Password](https://support.1password.com/one-time-passwords/), [Authy](https://authy.com/guides/github/) etc. can be used to generate TOTP. When you enable 2FA, you will be sent a QR code in your email which should be scanned from above mentioned application and TOTP will be generated by those applications. --- ## Contributing Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate. - see `CONTRIBUTING.md` for details. **If you want to be featured in contributors list on our home page please add PR on https://github.com/gobeam/truthy-contributors to provide your details.** --- ## Sponsors - [Ekbana Solutions Pvt. Ltd](https://ekbana.com/) --- ## License Released under the MIT License - see `LICENSE.md` for details. --- ## Acknowledgement - [NestJS](https://github.com/nestjs/nest)