Learn more about Remix Stacks.

• EdgeDB for the database
• Deployment on Fly
  • Healthcheck endpoint for Fly backups region fallbacks
• GitHub Actions
• Email/password authentication with cookie-based sessions
• Tailwind
• Cypress
• MSW (request mocking)
• Vitest and Testing Library
• Prettier
• ESLint
• TypeScript

Not a fan of bits of the stack? Fork it and make it your own! Or use one of these other community-maintained stacks that combine the gloriousness of EdgeDB and Remix:

• jkcorrea/remix-chop-suey-stack
• jacob-ebey/remix-edgedb
• anubra266/chakra-remix-stack-blues-edge

View the live application: https://edgedb-remix.fly.dev

npx create-remix --template edgedb/remix

If you haven't already, install the edgedb CLI: edgedb.com/install. Then run the following command from inside your project directory.

edgedb project init

This will install the latest version of EdgeDB, spin up an instance, and apply all migrations from dbschema/migrations.

npm run seed

This creates some sample notes and an initial user with the following credentials:

• email root@remix.run
• password: remix+edgedb=awesome

This project uses cookie-based authentication that relies on a secret token. It isn't secure to hard-code this value directly into your source code, so we'll use an environment variables called SESSION_STATE. To set this variable in development, create a .env file and add the following line. Remix automatically loads environment variables from this file when running in development mode.

SESSION_SECRET="super-duper-s3cret"

In the Deployment section, we'll describe how to set a value for SESSION_SECRET in production. We also set this variable in deploy.yml so it's available when running end-to-end tests in GitHub Actions.

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

npm run dev

Go to localhost:3000, click "Sign up" to create a new account, and explore the application.

This Remix Stack comes with two GitHub Actions that handle automatically deploying your app to production and staging environments.

Prior to your first deployment, you'll need to do a few things:

fly auth signup     # sign up
fly auth login      # login

Note: If you have more than one Fly account, ensure that you are signed into the same account in the Fly CLI as you are in the browser. In your terminal, run fly auth whoami and ensure the email matches the Fly account signed into the browser.

Run fly launch --no-deploy to create a new Fly app. You'll be prompted for an app name; if you leave this blank, a name will be generated for you.

$ fly launch --no-deploy
An existing fly.toml file was found for app "edgedb-remix"
? Would you like to copy its configuration to the new app? Yes
Creating app in /path/to/project
Scanning source code
Detected a Dockerfile app
? App Name (leave blank to use an auto-generated name):
Automatically selected personal organization
? Select region: sea (Seattle, Washington (US))
Created app <random name> in organization personal
Wrote config file fly.toml
Your app is ready. Deploy with `flyctl deploy`

Once the app has been created the existing fly.toml file will be overwritten with the newly created app's information (this is intentional).

Follow EdgeDB's Fly.io deployment guide for step-by-step instructions. At the end of this process, you will have a DSN which can be used to connect to the instance. It should have the following form:

edgedb://<user>:<password>@<hostname>:<port>

Add this value to your application as a Fly secret called EDGEDB_DSN.

fly secrets set EDGEDB_DSN=<paste DSN here>

To do this you can run the following commands:

fly secrets set SESSION_SECRET=$(openssl rand -hex 32)

If you don't have openssl installed, feel free to use any tool that will generate a random string, like a password manager or online tool.

Create a new GitHub Repository and Copy the provided git@github.com:<reponame>.git URL. Then execute the following commands. Don't git push yet—we have a bit more configuration to do first.

git init
git add .
git commit -m "Initial commit"
git branch -M main
git remote add origin <paste git url here>

To do this, generate a token via the Fly dashboard, copy it, and add it to to your repo via Settings > Secrets > Actions. Click "New repository secret", name it FLY_API_TOKEN, and paste the generated token.

Now we're ready to push this to GitHub. This will start the deployment process via GitHub Actions.

git push -u origin main

Every commit to your main branch will trigger a re-deployment to your production environment.

Once the GitHub Actions have completed, your application should be live on the internet! Fly automatically provides a public-facing URL for your application: <appname>.fly.dev. Visit this URL for a fully-functional cloud hosted version of the application.

Check your fly.toml file for your app name, or go to the Fly dashboard to see more information about the application.

Getting Help with Deployment

If you run into any issues deploying to Fly, make sure you've followed all of the steps above carefully. Go to the Fly dashboard and view the deployment logs; this will often be helpful for debugging. If you're still having issues open an issue on the edgedb/remix repo.

We use GitHub Actions for continuous integration and deployment. Anything that gets into the main branch will be deployed to production after running tests/build/etc. Anything in the dev branch will be deployed to staging.

This is a pretty simple note-taking app, but it's a good example of how you can build a full stack app with EdgeDB and Remix. The main functionality is creating users, logging in and out, and creating and deleting notes.

• creating users, and logging in and out ./app/models/user.server.ts
• user sessions, and verifying them ./app/session.server.ts
• creating, and deleting notes ./app/models/note.server.ts

We use Cypress for our End-to-End tests in this project. You'll find those in the cypress directory. As you make changes, add to an existing file or create a new file in the cypress/e2e directory to test your changes.

We use @testing-library/cypress for selecting elements on the page semantically.

To run these tests in development, run npm run test:e2e:dev which will start the dev server for the app as well as the Cypress client. Make sure the database is running in docker as described above.

We have a utility for testing authenticated features without having to go through the login flow:

cy.login();
// you are now logged in as a new user

We also have a utility to auto-delete the user at the end of your test. Just make sure to add this in each test file:

afterEach(() => {
  cy.cleanupUser();
});

That way, we can keep your local db clean and keep your tests isolated from one another.

For lower level tests of utilities and individual components, we use vitest. We have DOM-specific assertion helpers via @testing-library/jest-dom.

This project uses TypeScript. It's recommended to get TypeScript set up for your editor to get a really great in-editor experience with type checking and auto-complete. To run type checking across the whole project, run npm run typecheck.

This project uses ESLint for linting. That is configured in .eslintrc.js.

We use Prettier for auto-formatting in this project. It's recommended to install an editor plugin (like the VSCode Prettier plugin) to get auto-formatting on save. There's also a npm run format script you can run to format all files in the project.