- Astral Block Explorer Astral Block Explorer
- Astral Subsquid Playground Astral Subspace SubSquid
- Health Check Subspace Network Status Page
|
|
- Explorer - Next.js app based on React and Tailwind CSS, uses Apollo Client to fetch data from Astral Subsquid
- Indexers - Includes various Subsquid indexers like blockexplorer-subsquid and other smaller Subsquid services.
- Health check - utility service to check health status of an internal service and expose it as a REST API endpoint
Ensure you have the following installed on your local development machine:
- Node.js (v18.x or later)
- Yarn (v2.x or later)
You can check your Node and Yarn versions with 'node -v' and 'yarn -v' respectively.
These step focus on setting up the development environment for the Astral Block Explorer. You can also find the instructions for setting up the Squid backend and Health check services in their respective directories.
-
Clone the repository:
git clone https://github.com/autonomys/astral.git cd astral
-
Move to the explorer directory:
cd explorer
-
Install the dependencies:
yarn install
-
Run the development server:
yarn dev
Open http://localhost:3000 with your browser to see the result.
To set up the multi-network indexers, follow these steps:
-
Navigate to the indexers directory:
cd indexers
-
Install the dependencies:
yarn
-
Build the indexers:
yarn build
-
Start the PostgreSQL database with multiple tables, Hasura, and various Subquery nodes using Docker Compose:
From the root directory, run:
docker compose up
This command will initialize a PostgreSQL database configured with multiple tables, launch the Hasura GraphQL engine, and start multiple Subquery nodes to index all networks. This setup provides all the necessary data for different sections of the explorer, ensuring a comprehensive indexing solution for the application.
We welcome contributions to this project. If you are interested in enhancing the features of the app or fixing bugs, please follow these steps:
-
Fork the Repository
Fork the project to your own GitHub account. This will be your private workspace for staging changes.
-
Create a Branch
Create a branch in your forked repository for each set of changes you intend to make or issue you are addressing.
git checkout -b your-branch-name
-
Discuss New Features
For new features, it's preferable to first open an issue to discuss potential changes. This helps ensure that your efforts align with the project direction and that duplicate work is avoided.
-
Bug Fixes
For bug fixes, feel free to create a branch and proceed with fixes. Please ensure to clearly describe the bug and how your code resolves it.
-
Make Your Changes
Make the necessary modifications to the codebase and commit them. Please keep your commits granular and well-explained.
-
Write Tests
Ensure that your code is tested to prevent regressions.
-
Pull Request
Submit a pull request to the main branch of the original repository. Provide a clear description of the problem and solution. Include relevant issue numbers if applicable.
-
Code Review
Your changes will be reviewed by maintainers, who may provide feedback or questions. Address feedback and push your fixes as additional commits.
This project is licensed under the MIT License.