-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
feat: local deployment #26
Conversation
…eat/local-deployment
…at/local-deployment
apps/processing/Dockerfile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this file should be deleted right? is the Dockerfile for the Indexer not the processing service
apps/processing/.dockerignore
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete too
docker-compose.yaml
Outdated
env_file: | ||
- .env | ||
environment: | ||
POSTGRES_DB: ${ENVIO_PG_DATABASE} | ||
POSTGRES_USER: ${ENVIO_PG_USER} | ||
POSTGRES_PASSWORD: ${ENVIO_POSTGRES_PASSWORD} | ||
healthcheck: | ||
test: ["CMD-SHELL", "pg_isready -U ${DATALAYER_PG_USER}"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
test: ["CMD-SHELL", "pg_isready -U ${DATALAYER_PG_USER}"] | |
test: ["CMD-SHELL", "pg_isready -U ${ENVIO_PG_USER}"] |
@@ -69,7 +70,7 @@ export class EnvioIndexerClient implements IIndexerClient { | |||
if (error instanceof InvalidIndexerResponse) { | |||
throw error; | |||
} | |||
throw new IndexerClientError(JSON.stringify(error)); | |||
throw new IndexerClientError(JSON.stringify(error, Object.getOwnPropertyNames(error))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥴 xd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will be fixed on the following pr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should update .env.example file too
README.md
Outdated
|
||
``` | ||
docker-compose up -d --build | ||
``` | ||
|
||
Once the deployment is complete, you can access Hasura by navigating to: | ||
2. After starting Docker Compose, run the following command to apply the database migrations: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we should clarify that you need to setup the .env
file inside apps/scripts
folder before running the scripts
f89c568
to
070a503
Compare
🤖 Linear
Closes GIT-82
Description
Set up for local deployment and short docs.
Checklist before requesting a review