Find a file
2023-02-14 10:07:37 +01:00
app Initial commit 2023-02-11 03:14:14 +01:00
prisma Initial commit 2023-02-11 03:14:14 +01:00
public Initial commit 2023-02-11 03:14:14 +01:00
.editorConfig chore: setup project configs 2023-02-14 10:07:37 +01:00
.env.example Initial commit 2023-02-11 03:14:14 +01:00
.eslintrc.js Initial commit 2023-02-11 03:14:14 +01:00
.gitignore chore: setup project configs 2023-02-14 10:07:37 +01:00
CHANGELOG.md chore: setup project configs 2023-02-14 10:07:37 +01:00
commitlint.config.js chore: setup project configs 2023-02-14 10:07:37 +01:00
LICENSE Initial commit 2023-02-11 03:14:14 +01:00
package.json Initial commit 2023-02-11 03:14:14 +01:00
README.md Initial commit 2023-02-11 03:14:14 +01:00
remix.config.js Initial commit 2023-02-11 03:14:14 +01:00
remix.env.d.ts Initial commit 2023-02-11 03:14:14 +01:00
tsconfig.json Initial commit 2023-02-11 03:14:14 +01:00
yarn.lock Initial commit 2023-02-11 03:14:14 +01:00

Welcome to Remix!

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