You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: