Magictallguy

Hmm, could Cloudflare be doing the derp on an old resource? @Dayo

Adding a mobile screeny for the light theme to confirm This is very likely a caching issue - we're on CSS build 8 now

Looks like your browser simply failed to grab the site's CSS properly. Clear the cache and try again 🙂 Chiming in with mobile screenshot too! Samsung Galaxy S23

I have not as I wasn't thinking of backwards compatibility. This change is part of a rolling set of changes I intend to make to suit more recent technologies. As for the claim that "nobody" has PHP 8.4 yet; SiteEU, WebWiz, HawkHost, Kinsta, SwitchWeb, NameCheap, GoDaddy, Google Cloud Hosting and AWS absolutely do support it. Honourable mention to cPanel's EasyApache which added PHP 8.4 support in December just gone. Again, I will add backward compatibility for PHP 8.0. Might send up a couple of branched releases so people can select their desired version.

You changed setenv to getenv? Of course that wouldn't work

Back when I was on Windows, I loved mLocati's PowerShell PHP Manager - you may wish to consider looking into it. Its primary purpose is to provide an easy way to install multiple PHP versions and choose whichever one the system considers active. As for your host, perhaps a request to their support might be fruitful.

PHP 8.4 required. I'll push an 8.0-friendly version shortly

I decided it's time to blow off the dust and give this project some TLC. So, a small update list! now comes with a Docker configuration no longer relies on Composer There will be more updates to come as the longer I look, the more I kick my younger self 😄

Head up to the object/property declarations and initialise the $querystring property Find: protected string $querystring; Replace with: protected string $querystring = '';

That's the installation of Composer itself. You now need to run `composer install` on the command line in the project's root to grab the 3rd-party dependencies. A future release will factor out the Composer reliance. But for now, that's the way

The autoload file is generated after running `composer install` in the project's root directory.

Instructions are available at https://getcomposer.org/

You'll probably need to your files over to the Docker with COPY

Oop, my mistake, forgot to include the watch directive. Assuming the docker-compose.yml you posted earlier is up to date services: # PHP service (for Laravel) php: build: context: . dockerfile: Dockerfile container_name: php volumes: - .:/var/www/ networks: - portfolio_network working_dir: /var/www/ # Nginx service nginx: image: nginx:latest container_name: nginx volumes: - ./:/var/www - ./nginx/:/etc/nginx/conf.d/ ports: - "80:80" depends_on: - php networks: - portfolio_network develop: watch: - action: sync path: . target: /var/www # MySQL service mysql: image: mysql:5.7 container_name: mysql environment: MYSQL_ROOT_PASSWORD: MySQLPass MYSQL_DATABASE: portfolio_db MYSQL_USER: portfolio_user MYSQL_PASSWORD: portfolio_password volumes: - mysql_data:/var/lib/mysql networks: - portfolio_network volumes: mysql_data: networks: portfolio_network: driver: bridge Addition started line 27

docker compose watch Ctrl + C Does it build?