Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Review/env fix #6

Merged
merged 2 commits into from
Sep 29, 2022
Merged

Review/env fix #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c1e8d00
README.md fix
fersirni Sep 28, 2022
584df52
env.sample fix
fersirni Sep 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .env.sample
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
NODE_ENV=development
PORT=8080
NODE_ENV=production
PORT=5000
LOG_NAME=ink-substrate-explorer-api
LOG_LEVEL=debug

Expand Down
17 changes: 8 additions & 9 deletions README-es.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,14 @@ El servicio se recargará si realiza ediciones.

## **Levantando el servicio (PROD)**

Para iniciar los contenedores del servicio de backend, la BD y pgAdmin ejecutar el siguiente comando:

```sh
docker-compose up -d
```
**Nota**: Se requiere una base de datos postgres en funcionamiento y una conexión válida a un nodo de Substrate.
Opcionalmente, comente el servicio de back-end en el archivo docker-compose si desea ejecutar la imagen localmente.

## Ejecutar la imagen de Docker del servicio back-end

### Descarga la imagen de DockerHub
Expand All @@ -157,7 +165,6 @@ docker network create ink-explorer-network
docker run -it -p 5000:5000 --network ink-explorer-network --env-file {pathToEnvFile} blockcoders/ink-substrate-explorer-api:latest
```


#### Verifique que la imagen comenzó a ejecutarse

```sh
Expand All @@ -171,14 +178,6 @@ CONTAINER ID IMAGE COMMAND
f31a7d0fd6c8 blockcoders/ink-substrate-explorer-api "docker-entrypoint.s…" 15 seconds ago Up 14 seconds 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp funny_lumiere
```

Después de que se inició el servidor, los bloques deberían guardarse en la base de datos.

Para iniciar tanto el contenedor del servicio de back-end como el contenedor de la base de datos, ejecute:

```sh
docker-compose up -d
```

El servicio se conectará al contenedor DB y comenzará a procesar bloques.

## **Testing**
Expand Down
16 changes: 8 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,14 @@ The service will reload if you make edits.

## **Starting the project (PROD)**

To start the backend service, DB and pgAdmin containers run the following command:

```sh
docker-compose up -d
```
**Note**: A postgresDB up and running and a valid connection to a substrate node are required.
Optionally comment the backend service in the docker-compose file if you want to run the image locally.

## Running the Back-end service Docker image

### Download the image from DockerHub
Expand Down Expand Up @@ -170,14 +178,6 @@ CONTAINER ID IMAGE COMMAND
f31a7d0fd6c8 blockcoders/ink-substrate-explorer-api "docker-entrypoint.s…" 15 seconds ago Up 14 seconds 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp funny_lumiere
```

After the server started, the blocks should be being saved on the DB.

To start both the Back-end service container and the DB container run:

```sh
docker-compose up -d
```

The service will connect to the DB container and start processing blocks.

## **Testing**
Expand Down