You can configure nginx and some sort of init tool to run your server in the background. As an example, here is a possible nginx configuration for the musicbrainz server:
Musicbrainz have traditionally used daemontools to run the application server in the background (http://cr.yp.to/daemontools.html). There is a sample file to start the application in fcgi mode here: https://github.com/metabrainz/musicbrainz-server/blob/62dee4ae7ca65b306b7aeef618037ad4bfcc380c/admin/nginx/service/run
I've also had success using supervisor (http://supervisord.org/) to run the server in fcgi mode.
Your way of running the server in the background is definitely a method that will work, but remember that you won't get any management tools to check the status of the process, or be able to automatically restart the process on reboot or if it crashes.
As we don't really support any other method other than the virtual machine it's difficult for us to support these kind of setups because they can differ so much from one to another - it can take a lot of effort for us to understand someone else's setup so that we can help them, which often uses up time that we don't have. You're welcome to use these examples as starting points, but we may not be able to help you with specific fixes to problems that you may have on your infrastructure.