my forum (0.1.0-beta.13) is in the www/forum directory.
Now I have seen during test installation of the latest version that it is newly installed in www/forum/flaurm.
So I made a test system and moved the forum there and adjusted the webserver settings.
(now the composer also finds what it is looking for)
If I delete "minimum-stability": "beta" from now comes the following error messages: (everything except the core has "*")
`$ php ~/bin/composer.phar update -- prefer-dist --no-plugins --no-dev -a --with-all-dependencies
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires flarum/auth-facebook *, found flarum/auth-face book[dev-next-back, dev-master, dev-1359-oauth2-improvements, v0.1.0-beta.3, ... , 0.1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 2
- Root composer.json requires flarum/auth-github *, found flarum/auth-github [dev-next-back, dev-master, dev-1359-oauth2-improvements, v0.1.0-beta.3, ..., 0. 1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 3
- Root composer.json requires flarum/auth-twitter *, found flarum/auth-twitt er[dev-next-back, dev-master, v0.1.0-beta.3, ..., 0.1.x-dev (alias of dev-master )] but it does not match your minimum-stability.
Problem 4
- Root composer.json requires flarum/core 0.1, found flarum/core[v0.1.0-bet a, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
Problem 5
- cbmainz/flarum-de[0.1.11, ..., 0.2.4] require flarum/core 0.1.0-beta.4 -> found flarum/core[v0.1.0-beta.4, ..., v0.1.0-beta.16] but it does not match you r minimum-stability.
- cbmainz/flarum-de[0.2.5, ..., 0.3.1] require flarum/core 0.1.0-beta.5 -> found flarum/core[v0.1.0-beta.5, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de[0.3.5, ..., 0.6.1] require flarum/core 0.1.0-beta.6 -> found flarum/core[v0.1.0-beta.6, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de[0.7.0, ..., 0.7.1] require flarum/core 0.1.0-beta.7 -> found flarum/core[v0.1.0-beta.7, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de 0.8.0 requires flarum/core 0.1.0-beta.8 -> found flarum /core[v0.1.0-beta.8, ..., v0.1.0-beta.16] but it does not match your minimum-sta bility.
- cbmainz/flarum-de 0.8.1 requires flarum/core 0.1.0-beta.8.1 -> found flar um/core[v0.1.0-beta.8.1, ..., v0.1.0-beta.16] but it does not match your minimum -stability.
- cbmainz/flarum-de[0.9.0, ..., 0.9.1] require flarum/core 0.1.0-beta.9 -> found flarum/core[v0.1.0-beta.9, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de 0.10.0 requires flarum/core 0.1.0-beta.10 -> found flar um/core[v0.1.0-beta.10, ..., v0.1.0-beta.16] but it does not match your minimum- stability.
- cbmainz/flarum-de 0.11.0 requires flarum/core 0.1.0-beta.12 -> found flar um/core[v0.1.0-beta.12, ..., v0.1.0-beta.16] but it does not match your minimum- stability.
- cbmainz/flarum-de[0.12.0, ..., 0.12.1] require flarum/core 0.1.0-beta.13 -> found flarum/core[v0.1.0-beta.13, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de[0.13.0, ..., 0.13.1] require flarum/core 0.1.0-beta.14 -> found flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1, v0.1.0-beta.15, v0.1.0-be ta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de[0.14.0, ..., 0.14.3] require flarum/core 0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.15, v0.1.0-beta.16] but it does not match your minimum-stability.
- cbmainz/flarum-de[1.0.0, ..., 1.7.0] require flarum/core 1.0 -> found fla rum/core[v1.0.0, ..., v1.8.1] but it conflicts with your root composer.json requ ire (0.1).
- Root composer.json requires cbmainz/flarum-de * -> satisfiable by cbmainz/ flarum-de[0.1.11, ..., 0.14.3, 1.0.0, ..., 1.7.0].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and re movals for packages currently locked to specific versions.
Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
`
can someone help me?
my show -lo file