I will start with some general points on why we don't recommend using the AtoM Vagrant box in production:
First, the box has not been scaled with enough resources for production level use - the amount of memory, disk space, and CPUs assigned to the virtual appliance are limited. However, these are things you can potentially modify.
Second, Virtualbox is what is known as a Type-2 hypervisor
, and it is designed primarily for "workstation virtualization" - that is Desktop virtualization, which requires a full operating system installed below it. Other virtualization tools such as VMWare ESX/ESXi or Xen are what are known as Type-1 or "bare metal" hypervisors - these run directly on the host hardware, and are tiny operating systems designed only to run VMs and as such, have a smaller footprint. While desktop virtualization does technically have everything you need for virtualization just like a Type-1 hypervisor, a lot more system resources are consumed maintaining the desktop environment and other applications, tools, etc. included in the image, leaving less available for AtoM. I've also read that Virtualbox's networking speed can be slow, and that long-time high performance requires much more host RAM then normal usage would.
Overall, remember that AtoM is intended to be installed on a server (which is likely why you had issues translating the instructions and installing on a Mac computer) - if you are installing this on a desktop (even if it is virtualized), then it will likely not have the stability, persistence, and scalability to maintain sustained use in production! It can be done, but it is not recommended!
In your particular case:
It sounds like you want to use the Vagrant box for local data entry, and then you will extract a sqldump of the data (and the uploads directory for any uploaded digital objects) and migrate those to an actual server installation for public access - is this correct?
If so, this is certainly better than trying to simply spin up the Vagrant box and use it for ongoing public access. However, I don't believe we've ever tested using a Vagrant image across multiple machines via port forwarding on a network. I strongly recommend that you create some kind of cron job to regularly back up the database and uploads directory as you do this, so if the Vagrant box crashes, you don't lose all of your work!
As for the 500 errors:
The first thing I always recommend is to take a look at the Nginx error logs for more information on the nature of the error. See:
If you're not sure what the error messages mean and can't find related posts in this forum, feel free to post the message here and we'll do what we can to help troubleshoot. That said, your idea of increasing the PHP execution limits is a good one - we have some further information on doing so here:
You might also want to take a look at the Troubleshooting page we've added to the 2.5 documentation for ideas - they should all apply to 2.4.x as well: