pulserver 0.0.2__tar.gz

pulserver-0.0.2/.claude/skills/build-and-test/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: build-and-test
+description: Build pulserver from this checkout and run its formatter, linter, test suite and documentation build. Use before reporting any change complete, and whenever a test result or a skip has to be quoted rather than assumed.
+---
+
+# Build and test
+
+The extension `pulserver._ext` is compiled from `src/cpp/` and `src/c/`, so a
+checkout has to be installed before anything imports `pulserver`. Run the whole
+sequence and report the results it actually produced.
+
+```bash
+pip install -e '.[dev,doc]'
+bash scripts/format_and_lint.sh --check
+pytest -q -ra
+bash scripts/build_docs.sh
+```
+
+`scripts/format_and_lint.sh` runs `ruff format` and `ruff check`; without
+`--check` it rewrites the files instead of reporting them. It is the entry point
+pre-commit and CI use, so a style failure in CI is reproducible here.
+
+## Interpreting the run
+
+- The install needs a C compiler, a C++17 compiler and CMake. `src/c/` is
+  compiled with `-std=c90 -pedantic-errors`: a C99 construct is a build error,
+  not a warning to silence.
+- `tests/test_ir.py` compiles `src/c/` as a 32-bit scanner build and skips
+  without a 32-bit toolchain (`gcc-multilib`). Report that skip; it is not a
+  pass.
+- The CUDA leg of the `device` fixture skips without a device.
+- The scanner-sequence plugins under `tests/plugins/` bind arguments of the
+  installed pypulseqpp's sequence functions. A failure naming an argument the
+  function does not take means the plugin and the installed pypulseqpp
+  disagree; check `pip show pypulseqpp` against the floor in `pyproject.toml`
+  before changing either.
+- `tests/test_docs.py` runs the user-guide doctests and holds every public name
+  to its API page; a new public name needs a row there.
+
+## Documentation
+
+Documentation changes are validated by the documentation build and
+`tests/test_docs.py`, not by reading the source. See the `write-documentation`
+skill.

pulserver-0.0.2/.claude/skills/write-documentation/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: write-documentation
+description: Write, move or audit pulserver documentation — docstrings, user-guide, explanation, API and developer-guide pages, and the README. Use before creating or substantially modifying any documentation, and when deciding which documentation type a piece of material belongs to.
+---
+
+# Write documentation
+
+Two documents govern documentation and both are binding. Read them before
+writing:
+
+- `docs/developer-guide/documentation.md` — what belongs in each form of
+  documentation and how each is written.
+- `docs/developer-guide/terminology.md` — terminology, register, units,
+  frames, safety language and source-of-truth rules.
+
+The `Docstrings` and `Comments` sections of `AGENTS.md` govern docstrings and
+comments.
+
+## Choose the type first
+
+| Location | Type | Answers |
+|---|---|---|
+| `docs/user-guide/` | How-to | How do I install, run and extend pulserver? |
+| `docs/explanations/` | Conceptual explanation, one flat list in data-flow order | Why does it work this way? |
+| `gallery/01-course/` | Course lessons, read in order | What does a new user need to work independently? |
+| `gallery/02-tours/` | Tours: applications, advanced branches, specialised workflows | What does a representative workflow look like? |
+| `docs/api/` | Reference, from the docstrings | What exactly does this object do? |
+| `docs/developer-guide/` | Contributor procedure | How is this repository developed? |
+| `docs/developer-guide/internals/` | Implementation design | How is it built, and what does a playout rely on? |
+| `README.md` | Project summary and documentation landing page | What is this, and where is the rest? |
+
+Material in the wrong type is moved, not deleted. Implementation design found
+on an explanation page — file layouts, memory budgets, tolerances, test
+inventories — moves to `docs/developer-guide/internals/`, and the explanation
+links to it.
+
+A lesson belongs in the course only if it is on the shortest coherent path
+that gives a new user the framework's core mental model and enough practical
+competence to work independently; anything else is a Tour. A lesson has an
+introduction, a *Learning objectives* list and previous/next lines; a Tour
+opens with its objective and a prerequisites line and has neither.
+
+The IR is written in PulSeg's terms — base block, virtual segment, segment
+instance, execution stream — and *repetition* is the period
+`pypulseqpp.Sequence.repetition()` reports. Never "repeating unit", never
+"app" for a sequence function (`terminology.md`).
+
+## Verify before writing
+
+State nothing the code does not do. Read the implementation, its callers and
+its tests, and the C or C++ behind it when there is any. For the file formats
+and wire protocols, the authorities are the code in `src/pulserver/protocol/`,
+`src/c/include/pulseg/` and `src/pulserver/recon/_runtime/`. Flag a discrepancy
+you cannot resolve rather than guessing.
+
+## Mechanics
+
+- A runnable example on a user-guide page is a `pycon` block with `>>>`
+  prompts, ending with a blank line before the closing fence; it is executed
+  by `tests/test_docs.py`. An example that needs a running service or a data
+  file is a plain `python` block.
+- An API page lists its subpackage's public names in `| Object | Description |`
+  tables of `{obj}` links under a `currentmodule` directive.
+  `docs/api_objects.py` writes the per-object stubs from those tables into
+  `docs/generated/`, which is not tracked.
+- An explanation page ends with a `## See also` list linking the how-to and
+  the API pages it relates to. One with more than one `##` section opens with
+  a TL;DR admonition, ```` ```{admonition} TL;DR ```` and `:class: tldr`,
+  directly under its title; no landing, API or example page has one.
+- A figure takes its style from `docs/figure_style.py`; a script sets no font
+  size, DPI or colour literal and imports the colours it needs. A static
+  figure is a light/dark SVG pair written by `scripts/make_artwork.py` and
+  shown with `only-light` and `only-dark`.
+- A new page is added to the table and the hidden toctree of its section's
+  `index.md`.
+- A new gallery script goes into its section's directory under `gallery/`,
+  named with a numeric prefix, and gets a row and a toctree entry on the
+  section's landing page under `docs/examples/` (`course.md` or `tours.md`). A new section is a directory
+  with `README.rst` and `_gallery_header.md`, an entry in `GALLERY_SECTIONS`,
+  and a landing page listed in `docs/examples/index.md`.
+
+## Validate
+
+```bash
+pytest -q tests/test_docs.py tests/test_docstrings.py tests/test_docstring_defaults.py
+bash scripts/build_docs.sh
+```
+
+Open `docs/build/html/index.html` and check the rendered pages in the light
+and the dark theme, and the sidebar: User guide, Developer guide, Explanations,
+Examples (Course, then Tours), API, Misc.

pulserver-0.0.2/.dockerignore

@@ -0,0 +1,11 @@
+# The image is built from the sources alone; its version is pretended.
+.git
+**/__pycache__
+.pytest_cache
+.ruff_cache
+.coverage
+build
+dist
+wheelhouse
+docs/build
+docs/generated

pulserver-0.0.2/.gitattributes

@@ -0,0 +1,16 @@
+* text=auto eol=lf
+
+*.png binary
+*.jpg binary
+*.svg text
+*.npy binary
+*.npz binary
+*.mat binary
+*.h5 binary
+*.dcm binary
+# The IR cache a sequence is converted to.
+*.pseg binary
+
+# Sequence files written by pypulseqpp for the tests: collapsed in diffs and
+# left out of the language statistics.
+tests/fixtures/** linguist-generated=true

pulserver-0.0.2/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,43 @@
+name: Bug report
+description: Report reproducible incorrect behaviour or a documentation defect.
+labels: ["bug"]
+body:
+  - type: dropdown
+    id: subsystem
+    attributes:
+      label: Affected area
+      options:
+        - "Scanner sequences (pulserver.design, pulserver.protocol)"
+        - "Design calls and the design store (pulserver.host)"
+        - "IR conversion or the C cache library (pulserver.ir, src/c)"
+        - "Reconstruction proxy and enrichment (pulserver.proxy)"
+        - "Reconstruction plugins and MRD data (pulserver.recon, pulserver.mrd)"
+        - "Documentation"
+        - "Other"
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed and expected behaviour
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Smallest reproducer
+      description: >
+        Self-contained Python code, a plugin file, a minimal `.seq` file, or the
+        design call and its reply. Prefer synthetic data to a scanner
+        acquisition.
+      render: python
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: pulserver, pypulseqpp and Python versions, plus OS and architecture.
+      placeholder: "pulserver 0.x; pypulseqpp 0.x; Python 3.12; Ubuntu 24.04 x86-64"
+    validations:
+      required: true

pulserver-0.0.2/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question or idea
+    url: https://github.com/pulserver/pulserver/discussions
+    about: Ask about usage, or propose something before it is a bug report.
+  - name: Security vulnerability
+    url: https://github.com/pulserver/pulserver/security/advisories/new
+    about: Report privately. Please do not open a public issue.

pulserver-0.0.2/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,36 @@
+name: Feature request
+description: Propose a narrowly scoped addition to pulserver.
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Scientific or technical use case
+      description: State the missing capability and the acquisition or reconstruction workflow it serves.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed interface or behaviour
+      description: Include primary literature, a vendor or MRD convention, or an existing implementation where relevant.
+    validations:
+      required: true
+  - type: dropdown
+    id: layer
+    attributes:
+      label: Where it belongs
+      description: >
+        Sequence design belongs to pypulseqpp and reconstruction algorithms to
+        bartorch; pulserver holds the orchestration between them and the scanner.
+      options:
+        - "pulserver"
+        - "pypulseqpp (sequence design)"
+        - "bartorch (reconstruction)"
+        - "Not sure"
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered

pulserver-0.0.2/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+## What changed
+
+<!-- Concise implementation summary. -->
+
+## Why
+
+<!-- Problem and relevant issue or discussion. -->
+
+## Validation
+
+<!-- Exact commands and results. Include tests added for new behaviour. -->
+
+## Documentation impact
+
+<!-- User-facing changes, or "None" with a reason. -->

pulserver-0.0.2/.github/dependabot.yml

@@ -0,0 +1,40 @@
+version: 2
+updates:
+  # The Actions in .github/workflows pin third-party code that runs with
+  # repository credentials, so these are the updates worth having weekly.
+  - package-ecosystem: github-actions
+    directory: "/"
+    target-branch: main
+    schedule:
+      interval: weekly
+      day: monday
+    labels: ["dependencies", "ci"]
+    commit-message:
+      prefix: "ci"
+    groups:
+      actions:
+        patterns: ["*"]
+
+  - package-ecosystem: pip
+    directory: "/"
+    target-branch: main
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 5
+    labels: ["dependencies", "python"]
+    commit-message:
+      prefix: "deps"
+    groups:
+      # The sequence engine's signatures are what the scanner plugins bind to,
+      # so its bumps arrive alone and get a full run of their own.
+      engine:
+        patterns: ["pypulseqpp"]
+      mr-data:
+        patterns: ["numpy", "ismrmrd", "pydicom"]
+      build:
+        patterns: ["scikit-build-core", "pybind11", "setuptools_scm"]
+      dev-tooling:
+        patterns: ["pytest*", "coverage", "ruff", "pre-commit", "build"]
+      docs:
+        patterns: ["sphinx*", "myst-parser", "linkify-it-py", "matplotlib"]

pulserver-0.0.2/.github/workflows/codeql.yml

@@ -0,0 +1,36 @@
+name: CodeQL
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  analyze:
+    name: Analyze ${{ matrix.language }}
+    runs-on: ubuntu-latest
+    # Code scanning on a private repository needs GitHub Advanced Security,
+    # and uploading results without it is a hard error rather than a warning.
+    # The job stands down while the repository is private and starts working
+    # on its own once it is made public.
+    if: github.event.repository.visibility == 'public'
+    permissions:
+      security-events: write
+      packages: read
+      actions: read
+      contents: read
+    strategy:
+      fail-fast: false
+      matrix:
+        # c-cpp covers src/c, the library a scanner links, and src/cpp.
+        language: [python, c-cpp]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: github/codeql-action/init@v4
+        with:
+          languages: ${{ matrix.language }}
+          build-mode: none
+      - uses: github/codeql-action/analyze@v4
+        with:
+          category: "/language:${{ matrix.language }}"

pulserver-0.0.2/.github/workflows/console.yml

@@ -0,0 +1,39 @@
+# The console of the virtual scanner with Gadgetron behind pulserver's proxy,
+# composed from docker/ and driven through one exam and one scan.
+name: Console
+
+on:
+  workflow_dispatch:
+  pull_request:
+    paths:
+      - docker/**
+      - src/pulserver/virtual/_console.py
+      - src/pulserver/proxy/**
+      - .github/workflows/console.yml
+
+permissions:
+  contents: read
+
+jobs:
+  compose:
+    runs-on: ubuntu-latest
+    timeout-minutes: 60
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+      - name: Start the console, the proxy and Gadgetron
+        run: docker compose -f docker/compose.yaml up -d --build
+      - name: Scan through the console
+        run: |
+          pip install websockets pydicom numpy
+          python docker/smoke.py ws://127.0.0.1:8765
+      - name: Logs
+        if: always()
+        run: docker compose -f docker/compose.yaml logs --no-color
+      - name: Stop
+        if: always()
+        run: docker compose -f docker/compose.yaml down -v

pulserver-0.0.2/.github/workflows/docs.yml

@@ -0,0 +1,133 @@
+name: Docs
+
+# Builds the documentation and publishes it to GitHub Pages, which serves the
+# gh-pages branch. The site holds one directory per version: main publishes
+# `latest`, a release tag publishes `vX.Y.Z` and copies it to `stable`, and the
+# root redirects to whichever of the two a reader should see.
+#
+# A pull request builds only when a maintainer comments `/build-docs` on it,
+# and the build answers on the pull request with its result. That build
+# publishes nothing; main publishes after the merge.
+#
+# The branch is the site's archive. GitHub Pages can be deployed from an
+# artifact instead, but a deployment replaces the whole site, so publishing one
+# version would drop the others.
+
+on:
+  push:
+    branches: [main]
+    tags: ["v[0-9]+.[0-9]+.[0-9]+"]
+  issue_comment:
+    types: [created]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+# Every publish commits to the same branch, so main, the tags and a manual run
+# share one group and wait for each other rather than racing to push. A pull
+# request publishes nothing and gets a group of its own.
+concurrency:
+  group: docs-${{ github.event.issue.number || 'publish' }}
+  cancel-in-progress: ${{ github.event_name == 'issue_comment' }}
+
+jobs:
+  docs:
+    if: >-
+      github.event_name != 'issue_comment' ||
+      (github.event.issue.pull_request &&
+       startsWith(github.event.comment.body, '/build-docs') &&
+       contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write # the publish step pushes the built site to gh-pages
+      pull-requests: write # a requested build answers on its pull request
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          # A comment runs on the default branch; the build is of the pull
+          # request's head.
+          ref: ${{ github.event_name == 'issue_comment' && format('refs/pull/{0}/head', github.event.issue.number) || '' }}
+          fetch-depth: 0 # setuptools_scm reads the tags
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Name this version
+        id: version
+        # A release is built as `stable`, the URL a reader should land on, and
+        # archived under its tag as well; the canonical link in both copies
+        # points at `stable`.
+        run: |
+          if [ "$GITHUB_REF_TYPE" = tag ]; then
+            echo "dir=$GITHUB_REF_NAME" >> "$GITHUB_OUTPUT"
+            echo "canonical=stable" >> "$GITHUB_OUTPUT"
+          else
+            echo "dir=latest" >> "$GITHUB_OUTPUT"
+            echo "canonical=latest" >> "$GITHUB_OUTPUT"
+          fi
+
+      # autodoc imports the package, so the compiled extension is built too.
+      # The gallery reconstructs with the shipped pics plugin, on bartorch
+      # over torch's CPU build.
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install torch --index-url https://download.pytorch.org/whl/cpu
+          python -m pip install '.[doc]'
+
+      - name: Build
+        env:
+          PULSERVER_DOCS_VERSION: ${{ steps.version.outputs.canonical }}
+          PULSERVER_DOCS_RELEASE: ${{ steps.version.outputs.dir }}
+        run: bash scripts/build_docs.sh
+
+      - name: Check that the site is only the site
+        # Sphinx caches parsed documents in the output directory unless given
+        # `-d`, and the cache is far larger than the pages. Publishing commits
+        # whatever is there to a branch that is never pruned.
+        run: |
+          if [ -e docs/build/html/.doctrees ]; then
+            echo "::error::The doctree cache is inside the built site and would be published." >&2
+            exit 1
+          fi
+
+      - name: Publish
+        if: >-
+          github.event_name != 'issue_comment' &&
+          (github.ref == 'refs/heads/main' || github.ref_type == 'tag')
+        env:
+          DIR: ${{ steps.version.outputs.dir }}
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          site="$RUNNER_TEMP/pages"
+          remote="https://x-access-token:$GH_TOKEN@github.com/$GITHUB_REPOSITORY"
+          # The branch does not exist before the first publish.
+          if ! git clone --depth 1 --branch gh-pages "$remote" "$site"; then
+            git init -b gh-pages "$site"
+            git -C "$site" remote add origin "$remote"
+          fi
+
+          # Only this version's directory is replaced; a release refreshes
+          # stable only when it is the newest, and the root and the switcher's
+          # list are rewritten from what the site then holds.
+          python scripts/publish_docs.py docs/build/html "$DIR" "$site"
+
+          git -C "$site" add -A
+          git -C "$site" -c user.name='github-actions[bot]' \
+            -c user.email='41898282+github-actions[bot]@users.noreply.github.com' \
+            commit -m "Documentation for $DIR from $GITHUB_SHA" \
+            || { echo "No documentation change to publish."; exit 0; }
+          git -C "$site" push origin gh-pages
+
+      - name: Answer on the pull request
+        if: always() && github.event_name == 'issue_comment'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          RESULT: ${{ job.status }}
+          RUN: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: |
+          gh pr comment ${{ github.event.issue.number }} --repo "$GITHUB_REPOSITORY" \
+            --body "Documentation build: $RESULT ($RUN)"

pulserver-0.0.2/.github/workflows/fields.yml

@@ -0,0 +1,72 @@
+# BrainWeb's head in the virtual scanner's coils: each coil's transmit and
+# receive maps and the transmit coils' VOPs, solved by mariepy's
+# examples/brainweb.py and published as an image that holds only those files,
+# which docker/Dockerfile copies in by digest. mariepy runs here as a program;
+# none of its code enters pulserver or its image.
+name: Fields
+
+on:
+  workflow_dispatch:
+    inputs:
+      mariepy:
+        description: mariepy commit the fields are solved with
+        required: true
+      resolution:
+        description: Voxel pitch of the head, in mm
+        required: false
+        default: "5"
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  solve:
+    runs-on: ubuntu-latest
+    timeout-minutes: 360
+    env:
+      RESOLUTION: ${{ inputs.resolution }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          repository: pulserver/mariepy
+          ref: ${{ inputs.mariepy }}
+          fetch-depth: 0 # setuptools_scm reads the version from the history
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+
+      - name: Install mariepy
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install torch --index-url https://download.pytorch.org/whl/cpu
+          python -m pip install . brainweb-dl scipy
+
+      - name: Solve
+        run: python examples/brainweb.py --out fields --resolution "$RESOLUTION"
+
+      - name: Record what solved them
+        env:
+          RUN: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: >-
+          printf '{"mariepy": "%s", "resolution_mm": %d, "run": "%s"}\n'
+          "$(git rev-parse HEAD)" "$RESOLUTION" "$RUN" > fields/provenance.json
+
+      - uses: actions/upload-artifact@v7
+        with:
+          name: brainweb-fields
+          path: fields
+
+      - name: Publish
+        env:
+          TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          ACTOR: ${{ github.actor }}
+        run: |
+          image="ghcr.io/pulserver/brainweb-fields:$(git rev-parse --short HEAD)-${RESOLUTION}mm"
+          echo "$TOKEN" | docker login ghcr.io -u "$ACTOR" --password-stdin
+          printf '%s\n' 'FROM scratch' \
+            'LABEL org.opencontainers.image.source=https://github.com/pulserver/pulserver' \
+            'COPY . /' | docker build -t "$image" -f - fields
+          docker push "$image"
+          echo "Published $(docker inspect --format '{{index .RepoDigests 0}}' "$image")" >> "$GITHUB_STEP_SUMMARY"

pulserver-0.0.2/.github/workflows/image.yml

@@ -0,0 +1,57 @@
+# pulserver's image, whose default command is the console of the virtual
+# scanner reconstructing in its own process: built with the coils' field maps,
+# scanned through on the BrainWeb brain it carries, which loads without a
+# network, in the head coils' maps, and published from main.
+name: Image
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    paths:
+      - docker/**
+      - src/**
+      - tests/plugins/gre2d.py
+      - pyproject.toml
+      - CMakeLists.txt
+      - .dockerignore
+      - .github/workflows/image.yml
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  image:
+    runs-on: ubuntu-latest
+    timeout-minutes: 60
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+      - name: Build
+        run: docker build -f docker/Dockerfile -t pulserver .
+      - name: Scan through its console
+        run: |
+          docker run -d --name console -p 127.0.0.1:8765:8765 pulserver
+          pip install websockets pydicom numpy
+          python docker/smoke.py ws://127.0.0.1:8765 head8/head32
+      - name: Load BrainWeb without a network
+        run: >-
+          docker run --rm --network none --entrypoint python pulserver -c
+          "from pulserver.virtual import BrainWeb; print(BrainWeb().fractions.shape)"
+      - name: Give its console options after the image's name
+        run: docker run --rm pulserver --help | grep -e --spacing
+      - name: Publish
+        if: github.event_name == 'push'
+        run: |
+          echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u "${{ github.actor }}" --password-stdin
+          for tag in latest "${{ github.sha }}"; do
+            docker tag pulserver "ghcr.io/pulserver/pulserver:$tag"
+            docker push "ghcr.io/pulserver/pulserver:$tag"
+          done
+      - name: Logs
+        if: always()
+        run: docker logs console