I am trying to implement saleor (from the beginning) with git submodules, help me to know if this is a correct way..
sorry maybe I need to be very explicit
git remote rename origin fork //remane my origin reference as "fork"
git remote add origin https://github.com/mirumee/saleor.git//add saleor as "origin"
With the fork already made i create two branches (dev & prod)
My team will work against the dev branch and it will receive the ascending changes by the master brach. Logically, the prod branch is for deploy proposess, but it this will merged against the dev branch.
Also the master branch receive the ascending changes for saleor "origin".
In the dev branch i create submodules. pull , commit & ,push (on fork reference) the changes. This is when you have to really start being careful with send correclty this changes.
`*fork saleor | | |_>submodule dashboard | |_>submodule storefront `
Follow this way, the master branch is outdated respect to dev...this is not a problem for my workflow ...or yes?
What is the best way to handle it?
on branch (master)
On branch master Your branch is up to date with 'fork/master'. Untracked files: (use "git add <file>..." to include in what will be committed) saleor-dashboard/ saleor-storefront/
Thanks for your time...
@/all We've seen that many of you asked for help about how to use Docker Compose. If you would like to learn how to run Saleor with Docker Compose, read our new blog article explaining the issue in detail - written by @beatboxchad.
We're also working on improvements and automatization regarding using Docker Compose for the production. Stay tuned!