TheoryOfNekomata f278a8bf4f | 1 anno fa | |
---|---|---|
.. | ||
app | 1 anno fa | |
public | 1 anno fa | |
.eslintrc.js | 1 anno fa | |
.gitignore | 1 anno fa | |
README.md | 1 anno fa | |
package.json | 1 anno fa | |
remix.config.js | 1 anno fa | |
remix.env.d.ts | 1 anno fa | |
tsconfig.json | 1 anno fa | |
yarn.lock | 1 anno fa |
From your terminal:
npm run dev
This starts your app in development mode, rebuilding assets on file changes.
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.
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/
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