---
title: "Dominic Rockson (@psrockstar098) | Hashnode"
description: "Dominic Rockson (@psrockstar098) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@psrockstar098"
---

@psrockstar098

# Dominic Rockson

@psrockstar098 · Joined September 2026

### [Yatta JS 1.0.5: WebDAV, OAuth 2.0, OIDC and an MCP server — still one process](https://psrockstar098.hashnode.dev/yatta-js-1-0-5-webdav-oauth-2-0-oidc-and-an-mcp-server-still-one-process?utm_source=hashnode&utm_medium=feed)

When Yatta JS 1.0.0 launched on npm in October, the pitch was simple: the whole backend in one Bun process. Database, auth, mail, storage, realtime, jobs, observability — no separate services to provi

2 min read · [psrockstar098.hashnode.dev](https://psrockstar098.hashnode.dev/yatta-js-1-0-5-webdav-oauth-2-0-oidc-and-an-mcp-server-still-one-process?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/yatta-js-1-0-5-webdav-oauth-2-0-oidc-and-an-mcp-server-still-one-process/6af99d0950d49e344069be96)

### [Your whole database is one file you can copy](https://psrockstar098.hashnode.dev/your-whole-database-is-one-file-you-can-copy?utm_source=hashnode&utm_medium=feed)

The scariest sentence in side-project life is "the database is down." The second scariest is "we need to migrate the database." Both of those sentences assume your database is a server — a separate ma

2 min read · [psrockstar098.hashnode.dev](https://psrockstar098.hashnode.dev/your-whole-database-is-one-file-you-can-copy?utm_source=hashnode&utm_medium=feed)

[5d ago](https://hashnode.com/posts/your-whole-database-is-one-file-you-can-copy/6af45833e2b9f7f37ab82475)

### [Ship it without the YAML: Yatta JS's one-command deploy](https://psrockstar098.hashnode.dev/ship-it-without-the-yaml-yatta-js-s-one-command-deploy?utm_source=hashnode&utm_medium=feed)

The part of shipping a side project nobody warns you about isn't writing the code. It's the afternoon you lose to deployment: the platform account, the YAML file, the environment variables you set in

4 min read · [psrockstar098.hashnode.dev](https://psrockstar098.hashnode.dev/ship-it-without-the-yaml-yatta-js-s-one-command-deploy?utm_source=hashnode&utm_medium=feed)

[Nov 7](https://hashnode.com/posts/ship-it-without-the-yaml-yatta-js-s-one-command-deploy/6aef11803bcdd20dc6b40d50)

### [Your first backend in one afternoon: database, auth, jobs and realtime in a single Yatta JS process](https://psrockstar098.hashnode.dev/your-first-backend-in-one-afternoon-database-auth-jobs-and-realtime-in-a-single-yatta-js-process?utm_source=hashnode&utm_medium=feed)

Most side projects don't die because the idea is bad. They die in the gap between "it works on my machine" and "it's a real backend" — the week you lose wiring up a database, auth, a queue, WebSockets

3 min read · [psrockstar098.hashnode.dev](https://psrockstar098.hashnode.dev/your-first-backend-in-one-afternoon-database-auth-jobs-and-realtime-in-a-single-yatta-js-process?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/your-first-backend-in-one-afternoon-database-auth-jobs-and-realtime-in-a-single-yatta-js-process/6ae87987daa1ffd7c04c0865)

### [Your first Yatta JS backend, in three moves: data, realtime, jobs](https://psrockstar098.hashnode.dev/your-first-yatta-js-backend-in-three-moves-data-realtime-jobs?utm_source=hashnode&utm_medium=feed)

Most backend tutorials teach you one piece at a time, and each piece brings its own service: a database here, a WebSocket server there, a queue somewhere else. By the time the pieces talk to each othe

3 min read · [psrockstar098.hashnode.dev](https://psrockstar098.hashnode.dev/your-first-yatta-js-backend-in-three-moves-data-realtime-jobs?utm_source=hashnode&utm_medium=feed)

[Oct 29](https://hashnode.com/posts/your-first-yatta-js-backend-in-three-moves-data-realtime-jobs/6ae3334d861cc6a4558f8052)
