3Di wrote: ↑Tue Apr 28, 2020 4:38 am
You should not deploy teh development code on a production site.
Just use the official download package and follow the instructions.
Crizzo wrote: ↑Sun May 03, 2020 7:40 pm
he could simple use the release tags and then the version is the same as on the download package.. Don't see what is against that.
Even this is not ready to go, you need to run composer to get the third-party libraries pulled in. We don't provide official support in the main support forums for folks running off git due to the extra unknowns of the setup (commit/tag they're on, has composer been run recently, etc.).
Crizzo wrote: ↑Sun May 03, 2020 7:40 pm
he could simple use the release tags and then the version is the same as on the download package.. Don't see what is against that.
Even this is not ready to go, you need to run composer to get the third-party libraries pulled in. We don't provide official support in the main support forums for folks running off git due to the extra unknowns of the setup (commit/tag they're on, has composer been run recently, etc.).
Well, this is not a big step.
The version of the third-party libraries is freezed with the composer.lock file and if he checks out like: "release-3.3.0" and runs "composer.phar install" nothing i wrong with that version.
3Di wrote: ↑Tue May 05, 2020 12:27 am
Not to mention new migrations and the likes, no... it is a very bad idea .
What do you mean? What "likes"? Why should that not work?