If private network settings are used for Vagrant machine and the following occurs:
Command: ["hostonlyif", "ipconfig", "vboxnet2", "--ip", "10.0.0.1", "--netmask", "255.255.255.0"]
Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
It is not an issue with Vagrant itself, but rather with VirtualBox. Seems that latest versions of it restrict certain private network addresses.
Running Symfony based application in vagrant environment most likely would yield in cache issues.
In order to fix this, we need to instruct Symfony framework to place it's cache outside the vagrant synced folder. Luckily, it's easy and supported by the framework itself.
Check on How to Override Symfony's default Directory Structure (Symfony Docs)
Running npm install in a vagrant made environment is most likely to cause weirdo errors, spoiled or missing packages.
The issue is that node_modules directory is located in same directory as the project source files and during npm install the contents of this folder are attempted to be synced between virtual and host machines, therefore causing errors.
The solution is to use a bind mount on node_modules folder.
There was a time when Diablo2 took many of my hours in front of the screen and with a remastered version it was just a question of time when it would catch me again. I occasionally play the Resurrected remaster and one of the main scopes of the game is searching for runes. Same way it was in the original.
For an overview on how runes in Diablo2 are upgraded, check out the visualizer at https://d2r.annoyed.dev/.
The article describes on how to make use of HTTP/2 protocol in Apache2 when serving web content.