zeekay
0e6dc33027
A version written into a manifest is written into every manifest that wants it, which is how eslint came to exist in a hundred and four forms across this estate and how a package came to resolve twice at run time. The catalog moves the number out of the manifest: a manifest names the package, the workspace names the version. Four are held below their latest because the newer release cannot be used, and the reason is recorded rather than the version alone: @noble/hashes 2 renamed every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels 3 points its types condition at the bundle.
Payload Blank Template
A blank template for Payload to help you get up and running quickly. This repo may have been created by running npx @hanzo/create-cms-app@latest and selecting the "blank" template.
See the official Examples Directory for details on how to use Payload in a variety of different ways.
Development
To spin up the project locally, follow these steps:
- First clone the repo
- Then
cd YOUR_PROJECT_REPO && cp .env.example .env - Next
beta && beta dev(ordocker-compose up, see Docker) - Now
open http://localhost:3000/adminto access the admin panel - Create your first admin user using the form on the page
That's it! Changes made in ./src will be reflected in your app.
Docker
Alternatively, you can use Docker to spin up this project locally. To do so, follow these steps:
- Follow steps 1 and 2 from above, the docker-compose file will automatically use the
.envfile in your project root - Next run
docker-compose up - Follow steps 4 and 5 from above to login and create your first admin user
That's it! The Docker instance will help you get up and running quickly while also standardizing the development environment across your teams.
Production
To run Payload in production, you need to build and start the Admin panel. To do so, follow these steps:
- First invoke the
payload buildscript by runningbeta buildornpm run buildin your project root. This creates a./builddirectory with a production-ready admin bundle. - Then run
beta startornpm run startto run Node in production and start Payload from the./builddirectory.
Deployment
Check out the deployment documentation for details on how to deploy your project.
Questions
If you have any issues or questions, reach out to us on Discord or start a GitHub discussion.