Building a modern alternative to Salesforce, powered by the community.
Go to file
Charles Bochet 180e6b17ca
Merge pull request #17 from twentyhq/charles-bochet-env-variables-2
Add environment variable to build:latest too
2023-01-28 18:36:32 +01:00
.circleci Add environment variable to build:latest too 2023-01-28 18:34:14 +01:00
front Add environment variable to build:latest too 2023-01-28 18:34:14 +01:00
infra Add environment variable to build:latest too 2023-01-28 18:34:14 +01:00
server Enable Health Check route 2022-12-28 16:59:22 +01:00
.gitignore Generate Token through Auth0 2023-01-28 10:58:04 +01:00
LICENSE Initial commit 2022-12-01 14:04:40 +01:00
README.md Generate Token through Auth0 2023-01-28 10:58:04 +01:00

Twenty

Welcome to Twenty documentation!

High Level Overview

Twenty development stack is composed of 5 different layers:

  • twenty-front: our frontend React app
  • twenty-api (Hasura): our backend presentation layer that can do straight forward CRUDs, permissionning, authentication.
  • twenty-server: our backend that contain complex logics, scripts, jobs...
  • [tbd] twenty-events (Jitsu): our event ingestor which is separated from api and server to ensure high availability
  • storages: postgres, [tbd] elasticsearch, [tbd] redis.

Development environment setup

This section only discusses the development setup. The whole developemnt environment is containerized with Docker and orchestrated with docker-compose.

Step 1: pre-requesites

Make sure to have the latest Docker and Docker-compose versions installed on your computer.

Step 2: docker build

Build docker containers.

The whole setup/development experience is happening in infra/dev folder. Make sure to be in this folder:

cd infra/dev
docker-compose up --build --force-recreate

Once this is completed you should have:

Step 3: environment file

Configure your environment by copying the .env.example file located in infra/dev folder into .env.

cp infra/dev/.env.example infra/dev/.env

Then, you'll need to replace all REPLACE_ME variable by their development value. Please reach out to another engineer to get these values (as most of them are third party credentials, sensitive data)

Step 4: API (Hasura) metadata

Browse Hasura console on http://localhost:8080, go to settings and import metadata file located in infra/dev/twenty-api folder

Developping on Frontend

The development FE server is running on docker up and is exposing the twenty-front on port http://localhost:3001. As you modify the /front folder on your computer, this folder is synced with your twenty-front container and the frontend application is automatically refreshed.

Develop

Recommended: as you modify frontend code, here is how to access twenty-front server logs in order to debug / watch typescript issues:

docker-compose up
docker-compose logs twenty-front -f

Open a shell into the container

docker-compose exec twenty-front sh

Tests

Unit tests:

docker-compose exec twenty-front sh -c "npm run test"
# coverage
docker-compose exec twenty-front sh -c "npm run coverage"

Storybook:

docker-compose exec twenty-front sh -c "npm run storybook"

Developping on API

The API is a Hasura instance which is a no-code container. To modify API behavior, you'll need to connect to Hasura console on: http://localhost:8080/console

Developping on server

Section TBD