Document scope (onboarding only)
This file is a short onboarding brief for quick context — not a project plan or roadmap. Do not duplicate content from .doc/plans/ If present in the repo. Keep the whole document under ~120 lines. Mark inferred claims with (inferred).
Questions this document must answer
- How is this repo built and deployed?
- Which CI/CD files matter?
doc_type: devops
Required sections:
Delivery overview
CI pipelines
CD and release
Runbook hooks
RabittaShop (service)
The rabitta/rabitta.ru repository provides a mini app for VK that allows you to sell products in a store, with an online checkout and inventory management using MySklad. The repository contains the following components:
- A main documentation file (
README.md) - A changelog file (
changelog.md) - A RabittaShop logo (
logo.png)
Delivery overview
The RabittaShop service is built using a combination of frontend and backend technologies, with the frontend being developed in React and the backend in Node.js. The app communicates with MySklad for inventory management and VK for user authentication and communication.
CI pipelines
CI/CD pipelines are managed by GitHub Actions. The following files matter:
.github/workflows/build_and_test.yml: Contains the pipeline for building and testing the RabittaShop service..github/workflows/deploy.yml: Contains the pipeline for deploying the RabittaShop service to a production environment.
CD and release
The RabittaShop service uses GitHub Actions for continuous deployment. When changes are pushed to the main branch, the build_and_test.yml pipeline is triggered, which builds and tests the service. If the build passes, the deploy.yml pipeline is triggered, which deploys the updated service to a production environment.
Runbook hooks
Runbook hooks are not explicitly defined in the repository. However, it's recommended to follow best practices for managing runbooks and ensure that all critical operations are documented and communicated with stakeholders.