No description
Find a file
2026-03-01 10:53:58 +00:00
.github chore: Remove commit-message-generator skill definition file 2026-03-01 17:36:15 +09:00
.vscode Initial commit from Astro 2025-01-04 17:24:53 +09:00
public Added a forgejo icon 2025-04-29 20:14:59 +09:00
src docs(blog): Update Forgejo CLI article and agent shell session selection 2026-03-01 19:50:23 +09:00
.gitignore Add .agent-shell/ to .gitignore 2026-02-23 19:17:51 +09:00
astro.config.mjs feat: implement dark mode support 2026-02-11 13:15:03 +09:00
buildspec.yml Update a buildspec.yml 2025-05-08 20:48:24 +09:00
compose.yml feat(container): add SSH server and rassumfrassum for LSP multiplexing 2026-02-11 12:25:57 +09:00
Containerfile feat(container): add SSH server and rassumfrassum for LSP multiplexing 2026-02-11 12:25:57 +09:00
eslint.config.js chore: add unified ESLint config for TS, Astro, and JSX 2025-12-31 21:01:21 +09:00
package-lock.json chore: update dependencies for security 2026-02-01 15:59:26 +09:00
package.json chore: update dependencies for security 2026-02-01 15:59:26 +09:00
README.md docs: update blog post naming convention to date-based format 2026-02-16 21:49:07 +09:00
tsconfig.json chore: update Astro/Preact deps and add TS/ESLint tooling 2025-12-31 20:58:07 +09:00

Naputo - n-daisuke897's blog

Welcome to my blog repository!

Commands

All commands are run from the root of the project, from a terminal:

Command Action
npm install Installs dependencies
npm run dev Starts local dev server at localhost:4321
npm run build Build your production site to ./dist/
npm run preview Preview your build locally, before deploying
npm run astro ... Run CLI commands like astro add, astro check
npm run astro -- --help Get help using the Astro CLI

Blog post filename convention

Manage files in src/blog/ with this format:

YYYY-MM-DD-your-post-slug.md

  • Use lowercase letters, numbers, and hyphens in the slug.
  • Keep words separated by a single hyphen.
  • If two posts share the same date and slug, append -2, -3, etc.

Dependency update guidance

For security/deprecated remediation, allow breaking changes via npm audit fix --force, then verify:

  • npm audit
  • npm run build

If you use Nix, you can enter a dev shell that provides the required CLI tools for this repo:

nix develop

This is intended to provide tools like Forgejo CLI (fj) and Node.js so "when you enter the repo, everything is available":

nix develop --command fj version
nix develop --command node --version

Podman (container) development

This repo can be developed inside a Podman container to keep your host clean and improve reproducibility.

Using podman compose

export SSH_PUBKEY_PATH="$HOME/.ssh/id_ed25519.pub"
podman compose up --build

On WSL2/rootless Podman, if you hit netavark/nftables errors, this repo defaults to slirp4netns via network_mode in compose.yml.

If you want SSH access (for Emacs TRAMP /ssh:), SSH_PUBKEY_PATH must point to your public key and port 2222 will be exposed for SSH.

Then open: http://localhost:4321

Run other commands in the running container:

podman compose exec app npm run build
podman compose exec app npm run preview -- --host 0.0.0.0 --port 4321

Troubleshooting (WSL2)

If hot reload is unstable/slow, enable polling:

CHOKIDAR_USEPOLLING=1 podman compose up --build

Tip: placing the repo under the WSL filesystem (e.g. ~/project/...) is often faster than under /mnt/c.