Add new section on how to update locally

[fiedsch]

This is a first draft for the new section (see #575). Comments and suggestions are welcome. Especially regarding the section "Ausblick" where I'm not sure if that makes sense, as a developer should know how to do that and it might look "frightening" to the non technical user. My current opinion: do not include it—the example is only half of the job anyway.

An english translation will follow once we agree on the german version.

[fkaminski]

I would keep the paragraph "Ausblick" and possibly rename it to "Alternative Vorgehensweise über die Konsole" to make clear that this is just a different approach.
Maybe with a link to https://docs.contao.org/dev/reference/commands/ and then optionally with your further script examples for automation.

[fkaminski]

Possibly mention that this procedure is also possible/useful for new Contao installations (in a info box maybe).

[fritzmg]

Btw. what about doing it via the Contao Manager locally?

[fiedsch]

Btw. what about doing it via the Contao Manager locally?

Why would I want to do this if I have the power of the command line ;-)

Serious reason for not recommending this:

The Contao Manager has enabled the resolver cloud by default. IMO this would generate a lot of unnecessary traffic for the Cloud Resolver (still people seem to do this as questions concerning the Manager where also XAMPP or MAMP are mentioned can be seen now and then).

Additionally: what would be the benefit compared to using the Manager on the web hosting?

[fritzmg]

Why would I want to do this if I have the power of the command line ;-)

Well this guide is targeted towards people who would usually use the Contao Manager and the Cloud Resolver, isn't it?

The Contao Manager has enabled the resolver cloud by default.

You need to disable that of course and mention that in the guide.

Additionally: what would be the benefit compared to using the Manager on the web hosting?

The benefit would be to resolve the dependencies locally, instead of using the Cloud Resolver.

[fiedsch]

I see. Having never used the manager locally I‘ll try this myself first and then update the PR.

Thanks for the feedback!

[fkaminski]

I see. Having never used the manager locally I‘ll try this myself first and then update the PR.

Thanks for the feedback!

Möglichkeit Neu Installation über den CM:
Kopiere composer.json und composer.lock in das Hauptverzeichnis oberhalb von »web«.
Der CM erkennt dies und bietet eine Installation (via composer install) an

Möglichkeit bei bestehender Installation über den CM:
Kopiere composer.json und composer.lock in das Hauptverzeichnis oberhalb von «web«.
Aktiviere einen composer install im CM über »Systemwartung/Composer-Abhängigkeiten/Installer«.

[fkaminski]

The Contao Manager has enabled the resolver cloud by default.
You need to disable that of course and mention that in the guide.

I am not sure if this is necessary when using the .lock with composer install via the CM?

[fritzmg]

I am not sure if this is necessary when using the .lock with composer install via the CM?

This is a guide on how to resolve the dependencies locally.

[fkaminski]

I am not sure if this is necessary when using the .lock with composer install via the CM?

This is a guide on how to resolve the dependencies locally.

You are absolutely right - Sorry ...

[fiedsch]

As suggested by @fritzmg I added a section on using the contao manager locally.

I additionally removed the section "Ausblick", as i rather see that as a new section in "Guides".

As I'm not a manager user, could you please check if the descriptions make sense? Thanks!

[fritzmg]

lgtm 👍 (disclaimer: I am not a CM user either).

[netzarbeiter]

Thank you, Andreas.

[netzarbeiter]

Suggested change

	```
	}

[fiedsch]

@netzarbeiter I do not get, what that change is supposed to correct.

The suggested change removes the closing ``` and inroduces a }. Do you want to add the } as the closing brace of "require": { block? The backticks to close the code block would still be required though.

[netzarbeiter]

I was trying to get rid of that.

[fiedsch]

looks like the unclosed } of the pseudo json code caused the error