https://github.com/pirs-io/pirs

P.I.R.S. is cloud-first business process register for internal or public use.
https://github.com/pirs-io/pirs

bpm bpmn business-process cloud go grpc microservices petriflow

Last synced: 27 days ago
JSON representation

P.I.R.S. is cloud-first business process register for internal or public use.

• Host: GitHub
• URL: https://github.com/pirs-io/pirs
• Owner: pirs-io
• License: gpl-3.0
• Created: 2022-08-09T16:35:12.000Z (about 2 years ago)
• Default Branch: master
• Last Pushed: 2023-05-31T15:33:29.000Z (over 1 year ago)
• Last Synced: 2024-09-30T08:23:16.476Z (about 1 month ago)
• Topics: bpm, bpmn, business-process, cloud, go, grpc, microservices, petriflow
• Language: Go
• Homepage: https://pirs.io
• Size: 3.48 MB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE.txt
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
# P.I.R.S.

> Process Integrated Register Systems

P.I.R.S. is a cloud-first business process (BPM) register. It can be deployed for internal use or for public access.

PIRS consists of several microservices to manage register of business processes. PIRS deployments can be connected

together to make large network of accessible business processes.

---

## requiments

* go 1.20

* docker (optional)

* docker-compose (optional)

## code organization

### docs

technical and business documentation

### k8s

k8s deployment scripts

### pkg

all go microservices

### gateway

java gateway microservice

## running solution

this solution is intended to run in cloud and consist of more than serval microservices so getting it up and running can

be a bit tricky but

docker-compose_dev.yml can be used to run services that are defined there. also some changes in respective microservices

config files may be needed.

also, no guarantee that this compose file will be always upo to date.

for development purposes of individual microservices usage of mocks and high unit test coverage are highly encouraged so

each microservice can

be developed truly independently of whole solution.

## releasing

```docker-compose_release.yml``` is used for creating new image releases, when creating release change version number of

release tag in current versions section

and then run ```docker-compose -f docker-compose_release.yml build``` and then push images to registry.

releasing is done manually in this development stage and will be automated with RC CI jobs