Saleor VS saleor-dashboard

Saleor Core: the high performance, composable, headless commerce API

https://github.com/saleor/saleor

Our community is most active on GitHub - for more questions, you can open discussions: https://github.com/saleor/saleor/discussions

Hi, could you please open a GitHub discussion or issue? Someone from our core team will need to take a look at it. https://github.com/saleor/saleor/discussions

Read more in the changelog: https://github.com/saleor/saleor/releases/tag/3.12.0

Read more in the changelog.

Hi! My colleague has replied to your GitHub discussion: https://github.com/saleor/saleor/discussions/11594

Saleor: https://saleor.io/

So far I tried to integrate dj_rest_auth, which failed. Then looked into Saleor project, but found it too overwhelming and I couldn't comprehend the code.

With the API for our Django app scaffolded, we’re ready to define a frontend service to consume it. The Saleor platform deployed on Heroku includes the saleor-dashboard, so we’ll define this in our Blueprint next. It is a single-page Node.js dashboard app, defined in an app.json file for Heroku deployment, and uses Heroku’s static buildpack. When we migrate saleor-dashboard to Render, we’ll use Render’s static environment. This component of our infrastructure will run for free, since Static Sites are always free on Render, and Render will serve it over a global CDN with fully managed TLS certificates. Let’s add to our render.yaml.

i looked a round to see if someone else asked the same question and i found this issue #1592

The Saleor Dashboard 3.2 changelog can be found here: https://github.com/saleor/saleor-dashboard/releases/tag/3.2.0