Can the virtualization server run “stand alone” on a machine with no connection to the Internet?
Yes. If you want to work on a machine with no access to the internet (thus precluding using XXX-XXX-XXX-XXX.ip.alfrescodemo.net as your virtualization domain), then you should set up your own name server (or reconfigure your existing one) so that it includes a wildcard domain for virtualization. If you rely on a hack like editing /etc/hosts with some pain you’ll be able to set things up for a static set of users & staging areas, but reviewers will never be able to preview content that comes to them via a workflow. This is because workflows use ephemeral AVM stores with ephemeral DNS names — it’s an ever-changing set of GUIDs. Unfortunately, there’s no way to create a DNS wildcard in the “hosts” file… you must use a nameserver (e.g.: Djbdns, or BIND). As mentioned in: Configuring the Virtualization_Server, you can configure BIND on windows or UNIX to create a wildcard DNS domain for virtualization. If you’re on a UNIX platform, you have at least two free/common options: BIND and Djbd
Related Questions
- I want to run a web and/or ftp server on one of my internal system, how can I let users on the internet to access my server behind Comtun firewall?
- Does Kernl assume that the web server and application server will run together on the same machine?
- Does Full Control Internet run on the server or the client machine?
