Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

This Week in microVMs

A TWiR-style newsletter repository for This Week in microVMs.

This is intentionally shaped after the public workflow used by rust-lang/this-week-in-rust:

  • draft/ contains the next issue and DRAFT_TEMPLATE
  • contributors submit PRs against the current draft
  • content/ stores published issues
  • publishing/ owns build/email commands
  • just website builds a local static site
  • just email generates an email-ready HTML file
  • link style and editorial rules live in the README

Fast path

just setup
cp .env.example .env
just next
just check
just website
just email
just buttondown-draft

Docker path, close to This Week in Rust

From the repo root:

just website
just email

Or directly from the publishing directory:

cd publishing
just website
just email

The publishing/justfile builds a Docker image and runs the local builder inside it. This mirrors the TWiR habit of keeping publishing/build concerns isolated from the editorial repo.

PRs for next issue

To propose content for inclusion in the next newsletter, create a pull request updating the current file in draft/.

You can also open an issue using the link suggestion template.

What do we look for?

This Week in microVMs is intended to highlight practical work in microVMs, secure sandboxes, lightweight virtualization, and AI-native runtime isolation.

Generally good:

  • maintainer updates from relevant projects
  • deep dives about Firecracker, Cloud Hypervisor, Kata, QEMU, KVM, Lima, Incus, Wasm sandboxes, or similar systems
  • practical walkthroughs with enough technical depth
  • security research about isolation, sandbox escapes, egress policy, or runtime trust boundaries
  • release notes that explain why changes matter, not just raw changelogs
  • talks, papers, slide decks, demos, podcasts, and videos
  • calls for participation in relevant open source projects
  • relevant events and jobs

Generally not good:

  • pure marketing copy
  • bare GitHub repo links with no explanatory writeup
  • duplicated links from recent issues
  • paywalled links unless clearly marked and unusually important
  • links requiring email capture to access
  • rants or personal attacks
  • undisclosed LLM-written articles

Link style guidelines

  • Link text should generally match the page title.
  • Use the canonical URL.
  • Remove unnecessary tracking parameters such as utm_source and utm_campaign.
  • Prefix media where useful:
    • [video]
    • [audio]
    • [slides]
    • [paper]
    • [series]
  • Use two-letter language prefixes for non-English content, such as [ZH], [ES], [FR].

Community sub-categories

Editors sort community links into sub-categories:

  • Official / Maintainer Updates
  • Project / Tooling Updates
  • Newsletters
  • Research
  • Observations / Thoughts
  • Walkthroughs
  • Security / Isolation
  • AI Agent Sandboxes
  • Miscellaneous

Publishing

From publishing/:

just website
just email

Outputs:

publishing/output-website/
publishing/email/

The email artifact is:

publishing/email/latest-email.html

Link queue

TWiR mostly treats the live draft as the queue. This repo keeps that model, but also includes queue/links.md as your personal scratchpad.

Use queue/links.md for rough capture. Move final items into draft/YYYY-MM-DD-this-week-in-microvms.md before publication.

Future mvm integration

This repo deliberately keeps the builder command-oriented:

twimvmbuilder check
twimvmbuilder build-site
twimvmbuilder build-email

Later, mvm can wrap those commands without changing the editorial workflow.

Root commands

just setup                 # create .venv and install local builder
just new-draft 2
just check
just website
just email
just build
just serve
just publish

The builder is installed from tools/twimvmbuilder, so development stays local and editable.

Date handling

new-draft now defaults to today's date:

just new-draft 2

Use an explicit date when planning a future issue:

just new-draft-date 2 2026-05-20

Publishing normally uses the Date: metadata already in the draft:

just publish

If the draft slipped and you want the published issue dated today:

just publish-today

Or stamp it with a specific date:

just publish-date 2026-05-20

Buttondown integration

This starter includes a safe Buttondown draft integration.

One-time setup:

export BUTTONDOWN_API_KEY="..."

Preview what would be sent:

just buttondown-dry-run

Create a Buttondown draft from the current issue:

just buttondown-draft

Full prepare flow:

just buttondown-ready

This creates a draft only. It does not send to your subscribers. Review and send manually in Buttondown.

See docs/buttondown.md.

Email-safe output

just email now generates conservative email-safe HTML and a plain-text fallback:

publishing/email/latest-email.html
publishing/email/latest-email.txt

The default Buttondown integration sends the generated email-safe HTML as a draft. You can also send Markdown with:

just buttondown-draft-md

See docs/email-safe.md.

Easiest weekly commands

The root Justfile loads .env automatically.

just setup
cp .env.example .env
# edit .env

Start the next issue:

just next

Move private queue items into the draft:

just queue-promote

Preview the full ship flow without creating a Buttondown draft:

just ship-dry-run

Create a Buttondown draft:

just ship

Create a Buttondown draft and archive locally:

just ship-archive

Stamp the issue date to today, create a Buttondown draft, and archive locally:

just ship-today

See docs/easy-mode.md.

Additional things included for maintainability

  • .env loading from the root Justfile
  • just status to show current draft, next issue number, and Buttondown key status
  • just next to infer the next issue number automatically
  • just queue-promote to move strong candidates from the private queue into the current draft
  • just ship* commands for one-command weekly publishing prep
  • local build-local path if Docker is annoying

GitHub automation

This starter now includes a guarded weekly GitHub Action:

.github/workflows/weekly-automation.yml

It counts links, runs Codex when the threshold is met, builds the issue, creates a Buttondown draft, and can optionally send if BUTTONDOWN_AUTO_SEND=true.

If there are not enough links, it sends a maintainer email instead of forcing a weak issue.

See docs/github-automation.md.

Chrome link saver

The chrome-extension/ folder contains a small Manifest V3 extension that saves the current page as a GitHub issue labeled link-suggestion.

See docs/chrome-extension.md.

TWiR-like publishing output

just website now behaves much more like this-week-in-rust:

just website

It builds the Docker image, generates the site, prints a loud publisher banner with the latest issue URL, and starts a server on port 8000.

Use this if you only want to build without hosting:

just website-build

See docs/twir-like-publishing.md.

Command reference

The root command surface is documented in:

docs/just-commands.md

Useful shortcuts:

just help
just status
just artifacts
just ship-dry-run

Dockerfile directory model

The publishing Dockerfile now only uses the directories required for this newsletter:

content/
draft/
queue/
publishing/
tools/

It no longer references placeholder sources/, plugins/, or themes/ directories.

Simplified publishing flow

The starter no longer includes placeholder sources/, plugins/, or themes/ directories.

Those existed only to resemble the shape of the upstream this-week-in-rust repository. For this newsletter, the easiest useful publishing flow only needs:

draft/       current issue
content/     archived issues
queue/       private capture queue
publishing/  Docker publishing tools
tools/       local builder

Normal weekly path:

just next
# edit draft
just check
just website
just email
just buttondown-draft
# review/send in Buttondown
just publish-today

Fast non-interactive prep:

just ship-dry-run
just ship

v10 fixes

  • Drafts now use YAML frontmatter.
  • just website no longer tries to delete a Docker-mounted output directory.
  • The Docker image no longer copies editorial directories at build time; the repo is mounted at runtime.
  • GitHub Issues can now be pulled into the queue:
just issues-report
just issues-import-dry-run
just issues-import
just issues-import-accepted

See docs/github-issues-queue.md.

v12 just next behavior

just next is now weekly-first. It looks at the latest issue date in draft/ and content/, then creates the next draft seven days later.

For example, if the latest draft is:

draft/2026-05-13-this-week-in-microvms.md

then:

just next

creates:

draft/2026-05-20-this-week-in-microvms.md

Explicit commands:

just next              # create next weekly issue using latest issue date + 7 days
just next-today        # explicitly create today's draft
just next-today-force  # overwrite today's draft
just next-date 2026-05-20
just next-date-force 2026-05-20

v13 live preview

You can now run a live-ish preview while editing:

just watch

Then open:

http://localhost:8000/

It watches:

draft/
content/
queue/
templates/

and rebuilds the static site when files change.

Other variants:

just watch-docker
just watch-build
just watch-port 8080

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages