Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/diegofcornejo/edopro-evolution-leaderboard-landing

EDOPro leaderboard landing
https://github.com/diegofcornejo/edopro-evolution-leaderboard-landing

Last synced: about 7 hours ago
JSON representation

EDOPro leaderboard landing

Awesome Lists containing this project

README

        

This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).

## Getting Started

First, run the development server:

```bash
npm run dev
# or
yarn dev
# or
pnpm dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.

This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.

## Learn More

To learn more about Next.js, take a look at the following resources:

- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!

## Deploy on Vercel

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

## Docker Compose
You need to compose the Docker image passing `--env-file .env` used for build arguments in the Dockerfile.

### Just web
```bash
docker compose --env-file .env build --progress plain
# Load env file here is important to pass the build arguments to the Dockerfile from the .env file.

docker compose up
# No need to pass the .env file again, since the environment variables are already defined in the docker-compose.yml, and they will be available during execution.
```

### With server
```bash
docker compose -f docker-compose-with-server.yml --env-file .env build --progress plain
docker compose -f docker-compose-with-server.yml up
```