Development mode: no public/build folder and no vite manifest found - Error HTTP 560

[lakano]

Hi,

I'm trying to setup a new developer installation of PILOS, but after previous issues fixed, I'm now stuck with Vite that doesn't find his manifest.json, indeed the public/build/ folder doesn't exists, but I don't known how to fix that.

May be it's related to previous issues I got because of files/directories ownership. In logs I got errors from git doing a fatal error for a« detected dubious ownership » and requesting to uses the command to fix it « git config --add safe.directory '/var/www/html' » but without success (even with a volume/file attached to /root/.gitconfig with « [safe] directory = * ». The only workaround I've found was to « chown 100999:100999 . -R ».

Then, I could uses the ./sail composer install && ./sail npm install

In the « ./sail logs app » there is no more error, it's only when I open the browser that I got a new log error :
local.ERROR: Vite manifest not found at: /var/www/html/public/build/manifest.json {"ip":"10.89.0.8","current-user":"guest"}

Do you have any ideas of why Vite doesn't do the build ? There is a way to force Vite to build ?

I use GNU/Linux Arch, so it's may be a platform specific problem

[samuelwei]

To fix the file permissions, I recommend setting WWWGROUP and WWWUSER to your current user's UID and GID, and rebuilding the docker image (./sail build).

[lakano]

I confirm, this fix the git issue !
But I still got an error on vendor/ folder :

$ ./sail composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Package operations: 152 installs, 0 updates, 0 removals

In Filesystem.php line 261:
                                                                 
  /var/www/html/vendor does not exist and could not be created:  
                                                                 

install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--download-only] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [--audit] [--audit-format AUDIT-FORMAT] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>...]

                              

It's because my « . » folder is in 755, indeed if I do a « chmod 777 . » this permit to fix this issue, but it's may be not the best way to do that

[lakano]

hmmm and in fact even a « chmod 777 . » isn't enough, the install can create the vendor and continue but then a new error occured:

(...)
  - Installing symfony/var-exporter (v7.2.0): Extracting archive
  - Installing timacdonald/log-fake (v2.3.0): Extracting archive
Generating optimized autoload files
Class Backend\Feature\api\v1\ApplicationTest located in ./tests/Backend/Feature/api/v1/ApplicationTest.php does not comply with psr-4 autoloading standard (rule: Tests\ => ./tests). Skipping.
Class Backend\Feature\api\v1\RoomTypeTest located in ./tests/Backend/Feature/api/v1/RoomTypeTest.php does not comply with psr-4 autoloading standard (rule: Tests\ => ./tests). Skipping.
Class Backend\Unit\Rules\CustomCreateMeetingParametersTest located in ./tests/Backend/Unit/Rules/CustomCreateMeetingParametersTest.php does not comply with psr-4 autoloading standard (rule: Tests\ => ./tests). Skipping.
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi
[2025-03-27 12:06:44] local.ERROR: The /var/www/html/bootstrap/cache directory must be present and writable. {"exception":"[object] (Exception(code: 0): The /var/www/html/bootstrap/cache directory must be present and writable. at /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php:179)
[stacktrace]
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(132): Illuminate\\Foundation\\PackageManifest->write(Array)
#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(108): Illuminate\\Foundation\\PackageManifest->build()
#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(91): Illuminate\\Foundation\\PackageManifest->getManifest()
#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(80): Illuminate\\Foundation\\PackageManifest->config('aliases')
#4 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterFacades.php(26): Illuminate\\Foundation\\PackageManifest->aliases()
#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(342): Illuminate\\Foundation\\Bootstrap\\RegisterFacades->bootstrap(Object(Illuminate\\Foundation\\Application))
#6 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(474): Illuminate\\Foundation\\Application->bootstrapWith(Array)
#7 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(196): Illuminate\\Foundation\\Console\\Kernel->bootstrap()
#8 /var/www/html/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#9 {main}
"} 

In PackageManifest.php line 179:
                                                                             
  The /var/www/html/bootstrap/cache directory must be present and writable.  
                                                                             

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

[samuelwei]

@lakano If you have time for a quick video conf. call this afternoon, message me on matrix @swrh68:thm.de

[lakano]

After our video conf, I've been able to isolate the problem in my case, it's may be related to podman or GNU/Linux, so if someone have the same issues, try to follow this simple step after the 1st launch of « ./sail up -d » :

./sail root-bash
# chown www-data:www-data . -R 
# exit

Then you should be able to launch the next commands without theses issues

[lakano]

My workaround isn't perfect as this also change your own host user rights and doesn't permit to edit the code in the same time. I've adjusted it like that:

After the 1st ./sail up -d :

./sail root-bash
    mkdir vendor node_modules
    chgrp www-data .
    chmod g+w .
    export LIST="public storage vendor node_modules bootstrap/cache package.json package-lock.json .env"
    chgrp www-data -R $LIST
    chmod g+w -R $LIST

[samuelwei]

After running npm install, you must either compile the frontend for production or start vite, see: https://thm-health.github.io/PILOS/docs/next/development/getting-started#finish-setup