Martin, You'll have to create an application with the subdomain name and point it to your (perhaps, base-derived) role.
Nick 2009/7/28 Martin Sweeney <[email protected]>: > >> Got it. No need for such complications. >> Roles -> Security groups. >> Then add ports for your app role and click "Save". > > Ah, splendid - thank you. > > Now - a further question. > > I'm currently running this instance on a separate farm for > development, but when I come to put it live on my production farm I > shall want a similar set up, with a subdomain http://comet.mydomain.com > which will forward to my instance. > > Given that my role won't be an app server role (so that it doesn't get > included in the load balancing), and there is no equivalent of app- > servers.include for other roles, how can I tell nginx to point the > subdomain to the relevant internal IP and port? > > Martin. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
