[DOC] More detailled installation doc

[vqlion]

What is missing in the documentation? Details during the installation process

Additional information Config: Ubuntu 22.04.3 LTS Install method: sail

Bugs and unclear parts:

• Directory not specified (didn't know where to run the commands)

• Fix: specify you need to be on the src directory

• On command composer require laravel/sail --dev during sail installation: error message saying

  maatwebsite/excel[3.1.0, ..., 3.1.25] require php ^7.0 -> your php version (8.1.2) does not satisfy that requirement.

  (this error message is somehow displayed despite having only PHP 8.1.2 installed)

• Fix: ignore the system requirements with composer require laravel/sail --dev --ignore-platform-reqs instead of the original command

• On command php artisan sail:install during sail installation you get asked what DB you want to install, which is not specified in the doc

• Fix: specify you have to choose mysql (default) after this command

• After command ./vendor/bin/sail up -d switch to docker container not really clear for new users

• Fix: separate the commands that need to be ran in the container and specify how to enter it : docker exec -it <container-id> /bin/bash(plus which one to enter to not choose the mysql container)

• After launch, the tabs "Network graph", "Field management > Fields" and "User profile" aren't working and return an exception:

  The /var/www/html/bootstrap/cache directory must be present and writable.

• Fix: change the permissions on the cache directory: chmod -R 770 bootstrap/cache/

• After launch, the "Duplicates" tab isn't showing any data (it runs properly without displaying an error message but isn't showing anything) and the Force Run button doesn't work
• Fix: run php artisan queue:work after composer update

[github-actions[bot]]

AI-Assisted Response:

Documentation Update Request: Clarifying Laravel Sail Installation Steps and Troubleshooting

Summary: The user @vqlion has reported multiple points of confusion and errors encountered while installing Laravel Sail on Ubuntu 22.04.3 LTS. The primary issues revolve around a lack of clarity in the installation instructions, specifically about where to execute certain commands, handling composer errors due to PHP version incompatibility, selection of database during the installation, and operation of Docker containers. Additionally, there are permission issues post-installation leading to non-functioning sections of the web application and problems with displaying data in the "Duplicates" tab.

Categorization: Documentation

Clarifications Sought:

1. Can you confirm if the "Network graph," "Field management > Fields," and "User profile" issues were resolved after changing the permissions on the cache directory, or are there still ongoing issues?
2. For the "Duplicates" tab, did running php artisan queue:work resolve the issue, or are there further problems with the display or functionality?
3. Could you provide more details about the context of use? For instance, is this during the development of a specific Laravel application or a more generalized issue with the installation process?
4. Are there any additional steps or configurations you performed prior to encountering these issues that may provide context or assist others in replicating the problem?
5. After applying the "fixes" you suggested, is there any additional feedback or recommendations you'd have for the Laravel Sail documentation?
6. Do you have any logs or error messages that occurred during these issues that could be helpful for diagnosis or further clarification?

This information would help in updating the documentation with more precise installation instructions and troubleshooting tips for future users.

[github-actions[bot]]

AI-Assisted Response:

Issue Summary: Documentation Update for Laravel Sail Installation on Ubuntu

Context: The issue pertains to a lack of clarity in the documentation regarding the installation process of Laravel Sail on Ubuntu 22.04.3 LTS using sail as an install method.

Clarified Details:

• The current documentation does not specify the directory for running certain installation commands. It should be noted that commands need to be run in the src directory.

• An error is encountered when executing composer require laravel/sail --dev:

  maatwebsite/excel[3.1.0, ..., 3.1.25] require php ^7.0 -> your php version (8.1.2) does not satisfy that requirement.

  Regardless of only having PHP 8.1.2 installed, the error suggests a requirement for PHP 7.x. A workaround is to use the --ignore-platform-reqs flag with composer to ignore the PHP version requirement.

• The documentation does not mention that the php artisan sail:install command will prompt the user to select a database. The documentation should specifically recommend selecting MySQL as the default option.

• Instructions are unclear on switching to the Docker container after bringing up the services with ./vendor/bin/sail up -d. It requires clearer steps about entering the correct container and avoiding the MySQL container.

• Certain tabs in the application ('Network graph', 'Field management > Fields', and 'User profile') are non-functional due to permission issues with the /var/www/html/bootstrap/cache directory. Permission changes are recommended for resolution.

• The "Duplicates" tab fails to display any data, and the Force Run button is inoperative. A potential fix involves executing php artisan queue:work following composer update.

Issue Classification: This issue primarily pertains to undocumented steps or clarifications needed within documentation. It also includes a report of permission-related problems and operational bugs after installation.

Questions for @vqlion for Issue Clarification:

1. Were there any specific steps or prerequisites performed before encountering the issues mentioned, which might not be included in the documentation?
2. Can you confirm the version of Laravel Sail that you're attempting to install?
3. Regarding the permission issues, are you using Docker volumes for the bootstrap/cache directory, and if so, are the permissions set correctly on your host machine?
4. Have you tried clearing

[create-issue-branch[bot]]

Branch doc/issue-470-_DOC_More_detailled_installation_doc created!