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.

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

Deploy Indexer #2

Open
pifragile opened this issue Jan 17, 2023 · 2 comments
Open

Deploy Indexer #2

pifragile opened this issue Jan 17, 2023 · 2 comments
Assignees

Comments

@pifragile
Copy link
Contributor

The indexer is now ready to be deployed.

It would be great if I could have access to the machine in order to restart the indexer when making changes.

The setup is as follows:

First npm install -g @subql/cli

then

yarn install
yarn codegen
yarn build
yarn start:docker (this i often had to repeat a couple of times, no idea why)
@pifragile
Copy link
Contributor Author

The indexer is now deployed.
We are using a very simple setup for this, namely using docker-compose on a root server, which is not best practice.
Like this we cannot get horizontal scaling, load balancing, zero downtime deployment, proper health checks etc.
It might be ok for now, because we only expect a small number of requests for the indexer for now.
I suggest we start with this setup, see how resilient it is and keep in mind that we wanna properly deploy at some point in the future.
For this I see two options: Using the managed service by subquery or doing a proper containerized deployment ourselves.

@mosonyi
Copy link

mosonyi commented Feb 6, 2023

@pifragile once we're out of the test phase I can set it up and running in our Kubernetes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants