Mega_Aleksandar wrote a reply+100 XP
3mos ago
Hi there,
There is another way of localization -> you can find in detail information here: https://laravel.com/docs/12.x/localization
Basically, you can edit those default files, but I would advise against editing the default files unless your app trully needs (the localization parts).
Best regards
Mega_Aleksandar wrote a reply+100 XP
3mos ago
Hi there,
First that comes to mind is Laravel + Inertia (Vue or React) - it is super easy to make such things with components and props that refresh on change (Inertia is super good for this).
Maybe check those out.
Best regards.
Mega_Aleksandar wrote a reply+100 XP
3mos ago
Hi,
For dev/staging/prod environments I really suggest you try out Docker containers, as it allows you to mimic all the different server setups. If you have a client that already has a server (controlled hosting or a VPS) you can mimic their setup, even install docker on it and not worry about the environment.
As for the staging part itself, my workflow is to have a subdomain with all of the llms.txt, robots.txt, even hardcoded ips in the .htaccess so that I am sure that noone that is not allowed access the staging environment.
Hope it helps a tad bit.