be52a203a3
Follow up to #12404. Templates include a custom route for demonstration purposes that shows how to get Payload and use it. It was intended that these routes are either removed or modified for every new project, however, we can't guarantee this. This means that they should not expose any sensitive data, such as the users list. Instead, we can return a simple message from these routes indicating they are custom. This will ensure that even if they are kept as-is and deployed, no sensitive data is leaked. Payload is still instantiated, but we simply don't use it. This PR also types the first argument to further help users get started building custom routes.
Payload Payload + Remix Example
This example is built based on an old version of the website template.
The objective is to show to use the Local API with Remix framework. This is achieved through monorepo with 2 apps: payload - Next.js admin panel and definition of the Payload config. website - Remix website, imports the payload config from payload
## Setup
cp ./payload/.env.example ./payload./.env(copy the payload .env.example file to .env)cp ./website/.env.example ./website/.env(copy the website .env.example file to .env)pnpm installpnpm run dev:payloadpnpm run dev:website(in a separate terminal)