Local Setup
Last updated
Was this helpful?
Last updated
Was this helpful?
Inji Certify is a robust platform that enables issuers to connect with an existing Credential Registry to issue verifiable credentials. Issuers can configure credential schemas for various types of certificates they wish to issue. Certificates are generated in JSON-LD format as per the W3C Verifiable Credentials (VC) v1.1 standard.
This guide is designed to help developers set up Inji Certify in their local environment, providing detailed instructions to replicate the platform's functionality for development or testing purposes.
To begin, visit the Inji Certify repository on GitHub:
Repository Link:
The repository contains all the necessary files and instructions to set up Inji Certify on your local machine.
Before proceeding with the installation, ensure you have the following installed:
Docker (26.0.0)
Docker Compose (2.25)
shell to run the scripts, if on Windows
installed, if on Mac
A URL to host your DID for verifying VCs(Verifiable Credentials) can use here or any other self-hosted server which is highly available for use by verifiers.
Please visit the section in the ReadME file to explore in detail.
The setup involves deploying using Docker Compose. Follow the steps given in the within the Inji Certify repository.
Once the setup is complete, you can start exploring the functionality of Inji Certify:
Configure Credential Schemas: Set up schemas for various types of certificates you wish to issue.
For additional configuration and usage instructions, consult the documentation included in the repository.
For further insights and guidance on using Inji Certify effectively, refer to the following:
Interact with the System: Test the issuance and management of credentials through our reference platform Inji Web. Please click to explore the steps!
To explore all the available APIs of Inji Certify, refer to the provided within the platform. This will allow you to interact with the various endpoints and understand their functionality in detail.
Comprehensive Documentation: Available within the repository’s file.
Support: Engage with the developer or seek support for any issues encountered during the setup.