Upgrade to laravel 10 and running again

[Letsplaybar]

I upgraded the next branch to laravel 9,
updated all node modules so that no more vulnerabilities are displayed,
adjusted the changes that brought the version in
and changed from Puphpeteer to Browsershoot, since Puphpeteer is not Laravel 9 compatible.

Besides, I have everywhere adjusted the namespace at the models imports.

Last but not least I added a Dockerfile with which you can build a fully functional image,
with which I tested the platform several times.
After starting the image you only have to link the storage and execute the install/upgrade command.
In the container you have to mount the .env file and the storage folder.

[Letsplaybar]

solves Issue #99

[MarceauKa]

What a good work! Let me some time to review that correctly :)

[Letsplaybar]

how does it look, have you already taken a closer look at it in the meantime?

I'm just thinking if it would be useful to extend the link parsing that Twitter links are automatically parsed and the text + the images / videos are then displayed in the text field, or generally adjust the links so if an image is set (SEO) that this is also displayed and not only the text.

[Letsplaybar]

I have now upgraded the dependencies in the docker file and upgraded the project to Laravel 10 in my branch, since Laravel 9 will reach EOL in February. My Shaark instance is now running over the image I built over my branch and I haven't noticed any problems so far, both pdf and yt-dlp video archiving works. with the pdf you should only pay attention to the zombie processes that chromium currently generates, maybe a process manager should be included.

[Letsplaybar]

I was kind and attached my Kubernetes configuration as a helm chart of how I have it running at my setup