markmiro-astro

Original README.md from astro: README_ASTRO.md.

To use with VSCode with prettier, follow this guide.

Development

Install dependencies

bun install

Run the dev server:

bun run dev

Testing

End-to-end tests use Playwright and live in tests/. They start their own dev server on port 4322, so they won't conflict with bun run dev.

Install the browser once:

bunx playwright install chromium

Run the tests:

bun run test
bun run test:ui # interactive mode

Pages that list S3 objects while rendering (like /projects/jpeg-degrader) are only checked when AWS_PROFILE or AWS_ACCESS_KEY_ID is set.

S3 Files

Use the dedicated S3-only AWS profile. Follow the local AWS S3 access guide to sign in and configure a new machine before running these commands.

Download the bucket before building or deploying. The jpeg-degrader page reads image sizes from the local copy at build time, and bun run deploy uploads the local copy first, so both fail without it.

Locally, the files should be one level above this root directory (../s3). I tried to get Vercel to ignore the files when placed in the repo directory, but Vercel would still try to upload them. The path is relative to the checkout, so each clone or worktree needs its own download.

To download, run:

export AWS_PROFILE=markmiro-s3
bun run s3-down

To upload, run:

bun run s3-up

Deploying

Refresh the local bucket copy first. deploy uploads ../s3 before building, so a stale copy would overwrite newer files in the bucket.

export AWS_PROFILE=markmiro-s3
bun run s3-down
bun run deploy

Troubleshooting

I disabled Vercel git integration because of env var issues.

For some reason, I've been getting ENV variable issues with AWS S3. The env vars are available for static builds locally, but it seems that Vercel doesn't inject them because it thinks the vars could be included into the client?

Deploy this way if build works locally but fails on Vercel:

vercel build
vercel deploy --prebuilt

Production build

vercel build --prod
vercel deploy --prebuilt --prod