Hmmm …
When we deploy to a remote Alfresco server, we don't actually create a web project. We just create a single AVM repo to store the live sites (and all snapshots of everything we've deployed). That live site repo is accessible via CIFS. Because it's not linked to a web project, it's not exposed in the GUI (GUI only exposes web project nodes, and all repos (staging, user) associated with those nodes).
You can fake out the system by creating a web project on your runtime that is named the same name as your source web project with the word 'live' appended to it. Then you can browse it in the GUI. Of course, you need to still ensure that your web forms are also available on that second system (export and import as an ACP), and you'll need to manually associate those forms again with your second server's web project.
But generally editing content on two separate servers (at least for now, until we support lock propogation across servers) isn't recommended. What are you trying to accomplish?
Kevin