Fixed Readme Link

.dockerignore

@@ -0,0 +1 @@
+.gitignore

.env.example

@@ -8,6 +8,8 @@
 #GITHUB_CLIENT_ID=<Make your own client>
 #GITHUB_CLIENT_SECRET=<Make your own client>
 
+#AUTH_OIDC_PROVIDER='{"issuer":"http://localhost:8080/realms/dev_realm","clientId":"dev_client","clientSecret":"your_generated_secret"}'
+
 #DATABASE_URL=postgresql://postgres:postgres-mqf3nzx@localhost:5438/postgres
 #REDIS_URL=redis://default:redis-mqf3nzx@localhost:6380
 #KAFKA_BOOTSTRAP_SERVERS=localhost:19092

.github/ISSUE_TEMPLATE/issue-template.md

@@ -0,0 +1,34 @@
+---
+name: Issue template
+about: Template for creating issues, both bugs and feature requests
+title: ''
+labels: ''
+assignees: vklimontovich
+
+---
+```
+┌─────────────────────────────────────────────────────────────────────────────────────────────────┐
+│ IMPORTANT: GitHub is for discussing issues of self-hosting Jitsu. Please make sure that your    │
+│ issue can be reproduced for self-hosting environment. If you're experiencing problem with your  │
+│ Jitsu Cloud account, please contact [email protected]                                           │
+└─────────────────────────────────────────────────────────────────────────────────────────────────┘
+
+Please delete this block before submitting the issue
+```
+
+## Summary
+
+<!-- Please put a summary of the issue with a clear context and motivation -->
+
+## System configuration and versions
+
+<!-- 
+Is it Jitsu Classic or Jitsu Next? What is the version of Docker images you're using? 
+-->
+
+## Artifacts (logs, etc)
+
+<!-- 
+If you're reporting a problem, please attach logs. 
+If possible, attach all log entries, not only lines with error message. Make sure to remove or mask any sensitive information such as api keys, IP addresses etc 
+-->

.github/workflows/close-stale-issues.yml

@@ -0,0 +1,23 @@
+name: Close inactive issues
+on:
+  schedule:
+    - cron: "30 1 * * *" #once a day at 1:30am
+
+jobs:
+  close-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/stale@v5
+        with:
+          days-before-issue-stale: 60
+          days-before-issue-close: 60
+          stale-issue-label: "🕰️Stale"
+          exempt-issue-labels: "⏳Postpone"
+          stale-issue-message: "This issue is stale because it has been open for 60 days with no activity."
+          close-issue-message: "This issue was closed because it has been inactive for 60 days since being marked as stale."
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          repo-token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/docker-build.yml

@@ -0,0 +1,46 @@
+name: Jitsu 2.0 Build Docker Images
+on:
+  push:
+    branches:
+      # todo - change with main
+      - feat/newjitsu/self-hosted-revamped
+
+jobs:
+  build:
+    name: Build Project
+    timeout-minutes: 60
+    runs-on: ubuntu-latest
+    steps:
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Install Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+
+      - uses: actions/checkout@v3
+      - name: Get pnpm store directory
+        id: pnpm-cache
+        shell: bash
+        run: |
+          echo "STORE_PATH=$(pnpm store path)" >> $GITHUB_OUTPUT
+
+      - uses: actions/cache@v3
+        name: Setup pnpm cache
+        with:
+          path: ${{ steps.pnpm-cache.outputs.STORE_PATH }}
+          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-pnpm-store-
+
+      - name: Install dependencies with pnpm
+        run: pnpm install --no-frozen-lockfile
+
+      - name: Build Beta Images for AMD64
+        run: pnpm build-scripts docker --platform linux/amd64 --tag beta --push-git-tag --push-docker --logs

.github/workflows/test-and-build.yml

@@ -1,29 +1,30 @@
-name: Build and Test
+name: Jitsu 2.0 Test and Build
 on:
   push:
     branches: [newjitsu]
   pull_request:
     branches: [newjitsu]
+  workflow_dispatch:
 
 env:
-  #container jitsucom/node16builder:latest has playwright browsers binaries preinstalled on this path:
+  #container jitsucom/node18builder:latest has playwright browsers binaries preinstalled on this path:
   PLAYWRIGHT_BROWSERS_PATH: /root/.cache/ms-playwright
 
 jobs:
-  test:
-    name: Test and Build project
-    container: jitsucom/node16builder:latest
+  build:
+    name: Build Project
+    container: jitsucom/node22builder:latest
     timeout-minutes: 60
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - name: Get pnpm store directory
         id: pnpm-cache
         shell: bash
         run: |
           echo "STORE_PATH=$(pnpm store path)" >> $GITHUB_OUTPUT
 
-      - uses: actions/cache@v3
+      - uses: actions/cache@v4
         name: Setup pnpm cache
         with:
           path: ${{ steps.pnpm-cache.outputs.STORE_PATH }}
@@ -34,18 +35,27 @@ jobs:
       - name: Install dependencies with pnpm
         run: pnpm install --no-frozen-lockfile
       - name: Check code format
-        run: pnpm format:check
+        run: pnpm format:check:all
       - name: Run linter
         run: pnpm lint
       - name: Build project
         run: pnpm build
-      #      - name: Publish canary versions
-      #        run: pnpm build
       - name: Run Tests
         run: pnpm test
-      - uses: actions/upload-artifact@v3
+      - uses: actions/upload-artifact@v4
         if: always()
         with:
           path: libs/jitsu-js/playwright/artifacts
           name: artifacts/@jitsu/js
           retention-days: 30
+      - name: Notify Slack
+        uses: rtCamp/action-slack-notify@v2
+        # Do not send notification for PRs, feature branches, or forks
+        if: ${{ env.SLACK_WEBHOOK != '' && github.ref == 'refs/heads/newjitsu' }}
+        env:
+          SLACK_USERNAME: "GitHub Actions"
+          SLACK_WEBHOOK: ${{ secrets.SLACK_DEV_CHANNEL }}
+          SLACK_COLOR: ${{ job.status }}
+          MSG_MINIMAL: "true"
+          SLACK_ICON_EMOJI: ":github-mark:"
+          SLACK_MESSAGE: "${{ job.status }}: Jitsu 2.0 Build: ${{ github.event.head_commit.message }}"

.gitignore

@@ -1,4 +1,5 @@
 node_modules
+**/node_modules
 .idea
 .env.local
 .turbo
@@ -8,3 +9,15 @@ node_modules
 
 /libs/jitsu-react/dist/
 /examples/nextjs-app/.next/
+/examples/hubspot-function/dist/
+/cli/jitsu-cli/compiled/
+/cli/jitsu-cli/dist/
+/types/protocols/dist/
+/libs/functions/dist/
+/docker/data/**
+/cache/**
+/cli/build-scripts/compiled/
+/cli/build-scripts/dist/
+/libs/jsondiffpatch/coverage/
+/libs/jsondiffpatch/dist/
+/devenv-*

.prettierignore

@@ -6,6 +6,7 @@
 # bundle stats
 *.mdx
 *.md
+
 jitsu
 # configs -- will keep multi-line json arrays
 .eslintrc.json
@@ -24,4 +25,7 @@ pnpm-lock.yaml
 /webapps/console/prisma/schema
 /libs/jitsu-js/__tests__/playwright/artifacts
 /libs/jitsu-js/compiled/
-libs/jitsu-js/dist/
+libs/jitsu-js/dist/
+/cli/jitsu-cli/compiled/
+/cli/jitsu-cli/dist/
+/libs/functions/dist/

.versions.json

@@ -0,0 +1,4 @@
+{
+  "beta": "2.3.*",
+  "latest": "2.2.*"
+}

CONTRIBUTING.md

@@ -1,24 +1,37 @@
 # Prerequisites
 
-- `node: 16.x`
-- `pnpm: >= 7.15.0`
+- `node: 18.x`
+- `npx`
+- `pnpm: >= 8.2.0`
+- `docker: >= 19.03.0`
 
 # Commands
 
 - `pnpm install` - Install dependencies
 - `pnpm build` - Build the project
-- `pnpm format` - Apply prettier to the project
-  - `pnpm format:check` - Check if prettier needs to be applied
+- `pnpm format` - Apply prettier to the project, only to changed files
+  - `pnpm format:check` - Check if prettier needs to be applied, check only changed files
+  - `pnpm format:check:all` - Check if prettier needs to be applied. Check all files
+  - `pnpm format:all` - Same as `pnpm format`, but check all files, regardless of changes
 - `pnpm lint` - Run linter
 - `pnpm test` - Run tests
-- CI runs equivalent of `pnpm install && pnpm format:check && pnpm build && pnpm lint && pnpm test`.
+- CI runs equivalent of `pnpm install && pnpm format:check:all && pnpm build && pnpm lint && pnpm test`.
 - `pnpm factory-reset` - if you have any problems
 
 
-# Releasing
+# Releasing NPM packages
 
-We use [monorel](https://github.com/jitsu/monorel) to publish releases.  At the moment only `@jitsu/jitsu-react`, and `@jitsu/js` are published to npm. To avoid confusion, 
-always release them together, even if only one of them has changes.
+We use [monorel](https://github.com/jitsucom/monorel) to publish releases to npm.
+
+## Packages
+
+- `@jitsu/protocols` (./types/protocols) - Base types for JS and React SDKs and Functions library
+- `@jitsu/jitsu-react` (./libs/jitsu-react) - React SDK
+- `@jitsu/js` (./libs/jitsu-js) - JS SDK
+- `@jitsu/functions-lib` (./libs/functions) - library for Jitsu Functions
+- `@jitsu/jitsu-cli` (./cli/jitsu-cli) - CLI to create, debug and deploy Jitsu Functions
+
+To avoid confusion, always release all npm packages together, even if only one of them has changes.
 
 ## Common steps
 
@@ -28,15 +41,50 @@ always release them together, even if only one of them has changes.
 
 ## Canary releases
 
- - `pnpm exec monorel  --filter '@jitsu/js' --filter '@jitsu/jitsu-react' --filter '@jitsu/protocols' --version '1.1.0-canary.{rev}.{time}' --npm-tag canary` - to **dry-run** publishing
- - Same command, but with `--publish` - to **publish**.
+ - `pnpm release:canary` - to **dry-run** publishing
+ - Same command, but with `pnpm release:canary --publish` - to **publish**.
 
-> **Note**
-> Replace `1.1.0` in `--version '1.1.0-canary.{rev}'` to the version that makes sense
 
 ## Stable releases
 
-- `pnpm exec monorel  --filter '@jitsu/js' --filter '@jitsu/jitsu-react' --filter '@jitsu/protocols' --version '**<put new version>**' --npm-tag latest` - to **dry-run** publishing
+- `pnpm release --version <put a version here>` - to **dry-run** publishing
 - Same command, but with `--publish` - to **publish**.
 
+
+# Releasing Docker packages
+
+We use [build-scripts](https://github.com/jitsucom/jitsu/tree/newjitsu/cli/build-scripts) along with `all.Dockerfile` to publish releases to Docker.
+
+## Packages
+
+- `jitsucom/console` (./webapps/console) - UI for Jitsu
+- `jitsucom/rotor` (./services/rotor) - Functions Server for Jitsu
+
+To avoid confusion, always release all packages together, even if only one of them has changes.
+
+## Common steps
+
+- Make sure that you are logged to your docker account `docker login`
+- `pnpm install && pnpm format:check && pnpm build && pnpm lint && pnpm test` should succeed
+- All changes should be committed (check with `git status`). It's ok to release canary from branches!
+
+## Beta releases
+
+- `./release.sh --dryRun` - to **dry-run** publishing.
+- `./release.sh` - to actually **publish** beta.
+
+## Stable releases
+
+- `./release.sh --release latest --dryRun` - to **dry-run** publishing.
+- `./release.sh --release latest ` - to actually **publish** latest image.
+
+## Bumping versions
+
+For initial release or to bump major/minor version pass `--version` argument to `./release.sh` script.
+
+- `./release.sh --version 2.5.0`
+- `./release.sh --release latest --version 2.5.0`
+
+
+
 

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2021 Jitsu Labs, Inc
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.