No description
Find a file
Miro Rauhala 1d6f8e1949
Some checks failed
CI / Deploy (push) Has been cancelled
update next, fix vuln
2025-12-04 10:02:13 +02:00
.github/workflows use buildx setup 2025-01-29 19:31:25 +02:00
app skip posts to allow build 2025-02-03 21:53:56 +02:00
public Move to nextjs 2022-09-02 15:16:48 +03:00
styles animate key words 2025-01-31 20:07:34 +02:00
.eslintrc.json Move to nextjs 2022-09-02 15:16:48 +03:00
.gitignore Move to nextjs 2022-09-02 15:16:48 +03:00
.prettierrc Update design 2024-06-30 21:53:52 +03:00
docker-compose.yml name container 2025-01-29 19:41:18 +02:00
Dockerfile fix docker build 2025-01-29 18:17:14 +02:00
LICENSE Add license & tailwindcss 2022-08-20 23:03:14 +03:00
next.config.js add mdx 2025-01-29 22:17:55 +02:00
package.json update next, fix vuln 2025-12-04 10:02:13 +02:00
pnpm-lock.yaml update next, fix vuln 2025-12-04 10:02:13 +02:00
postcss.config.js update to tailwind v4 2025-01-29 22:37:59 +02:00
README.md Initial commit 2022-08-20 22:01:06 +03:00
tsconfig.json wip 2023-07-30 14:36:06 +03:00

Personal site

Development

From your terminal:

npm run dev

This starts your app in development mode, rebuilding assets on file changes.

Deployment

First, build your app for production:

npm run build

Then run the app in production mode:

npm start

Now you'll need to pick a host to deploy it to.

DIY

If you're familiar with deploying node applications, the built-in Remix app server is production-ready.

Make sure to deploy the output of remix build

  • build/
  • public/build/

Using a Template

When you ran npx create-remix@latest there were a few choices for hosting. You can run that again to create a new project, then copy over your app/ folder to the new project that's pre-configured for your target server.

cd ..
# create a new project, and pick a pre-configured host
npx create-remix@latest
cd my-new-remix-app
# remove the new project's app (not the old one!)
rm -rf app
# copy your app over
cp -R ../my-old-remix-app/app app