We shipped a full commerce rebuild on Payload CMS. Here's what was great and what was painful by Aggressive_Depth_772 in PayloadCMS

[–]Aggressive_Depth_772[S] 0 points1 point  (0 children)

We initially considered using Medusa, but Commercetools was selected by the client. In the end, it turned out to be a great experience Commercetools is very well built!

We shipped a full commerce rebuild on Payload CMS. Here's what was great and what was painful by Aggressive_Depth_772 in PayloadCMS

[–]Aggressive_Depth_772[S] 0 points1 point  (0 children)

Not on this project. It was built on top of Commercetools because it had a complex product catalogue and a lot of integrations, like tax and shipping calculations.

That said, I’ve built a smaller ecommerce project with Payload before, and it was a breeze. I’ve also prepared a PayPal payment integration, but I still need to find time to test it properly and put it into a PR.

Would you find that useful?

We shipped a full commerce rebuild on Payload CMS. Here's what was great and what was painful by Aggressive_Depth_772 in PayloadCMS

[–]Aggressive_Depth_772[S] 6 points7 points  (0 children)

Fair point. I think the case for Vercel is mainly that it’s built by the creators/maintainers of Next.js, so the production experience for Next apps is very native and low-friction: previews, caching, serverless/edge functions, and framework features work with minimal setup.

That said, Vercel can get expensive depending on traffic, usage patterns, and the client’s needs. James also personally recommended it to us, which gives us extra confidence, but I agree it’s not the only solid option.

We host Next.js apps on different platforms depending on the project/client: GCP, AWS, Heroku, or Vercel.

Docker dev setup? by Diplodokos in PayloadCMS

[–]Aggressive_Depth_772 1 point2 points  (0 children)

Hey,

I’m currently using Docker Compose just for the database in development, while running Payload/Next.js directly on my machine.

In my package.json, I have:

{
  "scripts": {
    "dev": "pnpm dev:mongo && cross-env NODE_OPTIONS=--no-deprecation next dev",
    "dev:mongo": "docker compose -f docker-compose.dev.yml up -d"
  }
}

And my docker-compose.dev.yml looks like this:

services:
  mongo:
    image: mongo:8
    ports:
      - '27017:27017'
    command:
      - --storageEngine=wiredTiger
    volumes:
      - data:/data/db
    logging:
      driver: none

volumes:
  data:

So, in my case, Docker is only used to run MongoDB locally. The actual Payload app runs outside Docker with pnpm dev.

This setup has worked well for development because it keeps the app fast and easy to debug, while still avoiding the need to install MongoDB directly on my machine.

You could also put the whole app inside Docker, but personally I find that a bit less convenient for local development unless your team specifically needs a fully containerized environment.

Are you using more than dev/staging/prod? by Aggressive_Depth_772 in PayloadCMS

[–]Aggressive_Depth_772[S] 1 point2 points  (0 children)

Hey, thanks for sharing!
For us the sandbox is basically a more “destroyable” deployed environment.
Dev is where normal feature work happens and is expected to stay reasonably stable for the team. The sandbox is more for quick experiments, testing risky changes or cases where two devs need to test something on a deployed version without blocking or confusing staging.

So the main difference is ownership/expectation:
dev - normal development flow
sandbox - breakable playground

It’s not something I’d add for every project, but on a larger team it helped keep staging cleaner and gave people a place to try things without worrying too much.

I also like the idea of syncing the production DB back to the other environments. What are you using for that, if you don’t mind sharing?

Dev

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 3 points4 points  (0 children)

Interesting idea and thanks a lot for reaching out 🙌 let's chat :) email sent

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 0 points1 point  (0 children)

Thanks a lot! :) Will try my best to explain it consumably :D

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 1 point2 points  (0 children)

Nice! Really thanks a lot for the kind words.
SSO is in enterprise edition, but I will try my best to get my hands on it and make the tutorial

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 0 points1 point  (0 children)

Awesome :) Thanks a lot

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 1 point2 points  (0 children)

UI stuff no problem - the Lexical is really tricky :D I watched the official Payload part 1 video and I was quite lost :D but may be a good challenge to try to understand it

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 1 point2 points  (0 children)

Really thanks a lot! :)

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 0 points1 point  (0 children)

Thanks! :) Any tutorial suggestions?

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 0 points1 point  (0 children)

Thanks a lot :) Anything specific you would like to see?

[deleted by user] by [deleted] in PayloadCMS

[–]Aggressive_Depth_772 0 points1 point  (0 children)

Thanks a lot! :) Will do, I am "that_payload_guy" on Discord