Workaround broken devenv up in devshell

As per https://github.com/cachix/devenv/issues/756, devenv up is broken
in the standard devshell because it can't find the devenv-up package. By
setting this line to ....procfileScript we provide devenv with the
information it needs to reactivate devenv up

Change-Id: Ie35b461c0aca899fcf366afa204273c51e3a560b
Reviewed-on: https://git.clicks.codes/c/Caramels/Lotting/+/344
Tested-by: Samuel Shuert <coded@clicks.codes>
Reviewed-by: Samuel Shuert <coded@clicks.codes>
1 file changed
tree: 083c2dcdcebdcee67e9cbc6226622c8984bcfa24
  1. app/
  2. drizzle/
  3. lib/
  4. public/
  5. .envrc
  6. .eslintrc.json
  7. .gitignore
  8. .gitreview
  9. bun.lockb
  10. drizzle.config.ts
  11. flake.lock
  12. flake.nix
  13. next.config.mjs
  14. package.json
  15. postcss.config.js
  16. README.md
  17. tailwind.config.ts
  18. tsconfig.json
README.md

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.