chore: adopt syncNext workflow and .gitkeep convention
This commit is contained in:
5 files changed
+16
-23
No files matched your search
@@ -0,0 +1,16 @@
|
|||||||
|
name: Sync next
|
||||||
|
|
||||||
|
# Carries every change that lands on the base branch onto the paired `next`
|
||||||
|
# iteration branch, so `next` never drifts behind what has already shipped.
|
||||||
|
# `next` is created on the first run if the repo does not have one yet.
|
||||||
|
on:
|
||||||
|
push:
|
||||||
|
branches: ['main']
|
||||||
|
workflow_dispatch:
|
||||||
|
|
||||||
|
jobs:
|
||||||
|
sync:
|
||||||
|
uses: Start9Labs/start-technologies/.github/workflows/syncNext.yml@master
|
||||||
|
permissions:
|
||||||
|
contents: write
|
||||||
|
pull-requests: write
|
||||||
Whitespace-only changes.
@@ -1,18 +0,0 @@
|
|||||||
# assets/
|
|
||||||
|
|
||||||
Supplementary files that ship inside the `.s9pk` alongside your compiled code —
|
|
||||||
anything the service needs at runtime that isn't part of the upstream image.
|
|
||||||
Typical contents:
|
|
||||||
|
|
||||||
- entrypoint or wrapper scripts the daemon execs,
|
|
||||||
- configuration templates / generators,
|
|
||||||
- static files (default configs, seed data, certificates),
|
|
||||||
- an `ABOUT.md` or other docs you want bundled.
|
|
||||||
|
|
||||||
To make these files visible inside a container, mount them in `startos/main.ts`
|
|
||||||
with `sdk.Mounts.…mountAssets(…)` and exec against the mountpoint (see the
|
|
||||||
Volume Mounts section of `../../src/main.md`).
|
|
||||||
|
|
||||||
This directory is **required and must not be empty** — the build fails and git
|
|
||||||
won't track an empty directory. This README satisfies that requirement, so don't
|
|
||||||
delete it unless you're adding real assets to replace it.
|
|
||||||
Whitespace-only changes.
@@ -1,5 +0,0 @@
|
|||||||
Use the `/fileModels` directory to create separate `.ts` files to represent underlying files used by you package. The exported `FileModels` afford a convenient and type safe way to read amd write to the underlying files, as well as react to changes.
|
|
||||||
|
|
||||||
Supported file formats are `.yaml`, `.toml`, `.json`, `.env`, `.ini`, and `.txt`. For alternative file formats, you can use the `raw` method and provide custom serialization and parser functions.
|
|
||||||
|
|
||||||
It is common for packages to use a `store.json.ts` FileModel as a convenient place to persist arbitrary data that are needed by the package but are _not_ persisted by the upstream service. For example, you might use store.json to persist startup flags or login credentials.
|
|
||||||
Reference in new issue
Block a user