> For the complete documentation index, see [llms.txt](https://divoc.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divoc.digit.org/platform/installation/skills-needed-to-set-up-divoc.md). # Skills needed to set up DIVOC ## What does this section cover? * Skills needed for a simple setup scenario * Skills needed for a complex setup scenario ## **Simple setup: Only setup and configuration** This includes: 1. Setting up infrastructure on cloud or on-premise. 2. Deployment of application components/services. 3. Configuration of components to connect to work as a single system: \- Configure templates, such as data import templates for facility registry. \- Keycloak to change OTP-based login in keycloak to password-based login. \- Configuration of certificate templates. ## Skills the team should have: * Experience in setting up Kubernetes cluster / Docker-based deployment. * Experience in setting up and configuring platforms such as Kafka, Redis, Postgres, and Keycloak. * Experience in HTML templates design. ## Complex setup: Setup, configuration, and customisation Customise DIVOC as per the country-specific requirements and its implementation need, such as: 1. Changes in registry schema: This includes changes in the type of information being captured on various events. 2. UI: This includes applying country-specific branding on the various UI pages of the portal. 3. Add and Update APIs: This includes the introduction of new API calls within as well as with third-party applications, such as integration with the supply chain system to provide updates on the stock used at the facility level. It also involves updating existing APIs, such as changing mandatory fields to non-mandatory in API payloads and changing response structure, among others. ## Skills the team should have: * Experience in technologies such as HTML, Jquery, React, JavaScript for UI level changes. * Experience in technologies such as Go for API-related changes. * Experience in OpenSaber and Postgres for registry-related changes. * Experience in integrating platform services used in selected components for customisation and implementation. [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://divoc.digit.org/platform/installation/skills-needed-to-set-up-divoc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.