Revisit local dev setup with Docker

[lkostrowski]

The current saleor-platform setup seems not to work correctly.

We expect a 1-command setup of the container with Saleor core and it's dependencies.

The main target as discussed with @mirekm is a seamless setup for frontenders, who want to encapsulate Python, DB, and another core-related tooling inside containers.

One solution is to maintain a set of Dockerfiles with each tool (Dashboard, Checkout, Core...) and one or more docker-compose configs to run entire ecosystem

• Consult other issues and @peelar work
• Introduce temporary fix to Docker setup
• Consider proposal by @zaiste
• Strategic proposal / RFC on holistic dev experience of local development, cc @peelar

[lkostrowski]

Related saleor/saleor#10104

[lkostrowski]

Related saleor/saleor#9764

[lkostrowski]

Related #154

[lkostrowski]

Related https://github.com/saleor/react-storefront/issues/263

[lkostrowski]

Related #30

[peelar]

To give you some context, here is my experience with saleor-platform:

1. I begin the process of learning Saleor by going to the documentation
2. Progressing through the articles, I arrive at the Installation article that lists the commands to clone the saleor-platform repository:

git clone https://github.com/saleor/saleor-platform.git --recursive --jobs 3
cd saleor-platform
docker-compose build

3. I run all the commands, and everything is working. The only thing about that experience that can be improved is the fact that I had to run some scripts manually to apply migrations and populate the database, but that's a minor inconvenience.
4. So, saleor-platform is running, but I don't really know what to do next.

"If this is the way to run Saleor locally, then I should be able to develop and deploy it" - I thought.

However, the first words in the README of saleor-platform are the following:

Keep in mind this repository is for local development only and is not meant to be deployed on any production environment!

Given that saleor-platform may be the beginning of people's journey with Saleor, seeing "this is not meant to be deployed" with no forwarding to some other resources on deployment, is a bit like walking into a dead-end. In my opinion, there is room for improvement on how do we guide the user in that case.

The part that says "it is for local development" could use some clarification as well. If you wanted to host your own version of Saleor, you would have to fork it. So that means the purpose of saleor-platform is mostly educational: to learn the platform and its parts. If we are in agreement about this, let's think about how to communicate that better.

[lkostrowski]

I have updated local subrepos to the newest releases, everything works pretty well.

We will think with @magul if we should just update this repo (and continue updating), or we should also version it.

Some ideas are also

1. Push images to registry
2. Separate docker compose for backend-only, so if I want to use only backend, I dont want do build all frontend (slow)
3. Use makefile for scripts

[patrys]

@lkostrowski Can we consider this one closed?

[lkostrowski]

Looks like it 🚀