Skip to content

Meterian installation on bbossola/sysdist #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
meterian-sca-qa wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Meterian installation on bbossola/sysdist #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
71a26c6
Added Meterian badges in README.md [skip ci]
meterian-sca-qa[bot] Feb 23, 2024
7d12c79
Added Meterian workflow [skip ci]
meterian-sca-qa[bot] Feb 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .github/workflows/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
name: vulnerability scan workflow

on: push

jobs:
meterian_scan:
name: Meterian client opensource scan
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Scan project with the Meterian client
uses: MeterianHQ/meterian-github-action@v1.0.17
with:
cli_args: "--oss" #[ Meterian CLI Options ]
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@ The sample project containing the code for my NodeJS talk about distributed syst
**Please note that this code is no more that a spike I wrote in around 4 days: be gentle with that, and do not run it in production!**
I will refactor it, tough, for the next speech :)


[![security status](https://qa.meterian.io/badge/pb/1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703/security)](https://qa.meterian.io/projects/?pid=1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703) [![stability status](https://qa.meterian.io/badge/pb/1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703/stability)](https://qa.meterian.io/projects/?pid=1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703) [![licensing status](https://qa.meterian.io/badge/pb/1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703/licensing)](https://qa.meterian.io/projects/?pid=1e2b6a8c-02c0-49c8-8dbf-4cd5711ae703)

# what does it do?
What you have here is a process capable to implement some aspects of a key-value store (namely read and write) which does it using a distributed architecture. Following the CAP theorem it can use a CA approach (two-phase commit), an AP approach (sloppy quorums) or a CP approach (majority quorums). Based on the environment variable MODE it will select the operating mode.

Expand Down