drivent-backend

Driven.t

ℹ️ About

The Driven.t project’s mission is to create an event management system, focusing on providing a customizable application for each specific event. Using the White Label concept, Driven.t allows customers to have a unique application for each event they want to manage. The system has a timer that releases access on the start date of event registration and offers features such as registration (online or in person), choice of accommodation for in-person events, payment options, selection of activities at the event and the issuance of certificates of participation. The application is a web application and its development can be started by following the configuration and execution instructions in the development environment provided in the project repository.

---

---

🔸 Demo: https://drivent-frontend-kohl.vercel.app/

🔸 Driven.t Organization: https://github.com/drivent-ed

---

⚙️ How to run for development

1. Clone this repository
2. Install all dependencies

npm i

1. Populate .env file based on .env.example. REACT_APP_API_BASE_URL should point to your API server (driven.t-back)

2. Run the back-end in a development environment:

npm run start

---

🛠️ Building and starting for production

npm run build
npm start

---

🚀 Running application locally or inside docker

.env.development and .env.test must be changed if you and to run the application locally or inside docker. You can populate files based on .env.example file, but you need to consider the following:

• Running application locally (postgres and node):

Add your postgres credentials and make sure to create given database before running the application.

• Running application inside docker (postgres and node):

Set POSTGRES_HOST to drivent-postgres-development for .env.development and drivent-postgres-test for .env.test file. It is the name of the postgres container inside docker-compose file. Docker Compose will start the postgres container for you, create the database and host alias for you.

• Running application locally (node) but postgres is running inside docker:

Set POSTGRES_HOST to localhost for .env.development and localhost for .env.test file. Docker compose is configured to expose postgres container to your localhost.

---

🖇 What to do when add new ENV VARIABLES

Please notice that every ENV that should be available on browser should start with REACT_APP_ prefix. There are several things you need to do when you add new ENV VARIABLES:

• Add them to .env.example file
• Add them to your local .env file
• Add them to your docker-compose.yml file (just the name, not the value). Only envs listed in the environment section will be exposed to your docker container.
• Add them (prod version) to your github repo secrets. They will be used to generate the .env file on deploy.

---

How to Contribute

Contributions are always welcome! If you find any bugs or have suggestions for new features, feel free to open an issue or pull request.