The workaround I've used is to use a different yaws instance per app. I run vimagi and twoorl in the same vps but in different VMs. It only costs like $1/month to get an extra IP address for the vps.
On Tue, Nov 4, 2008 at 4:28 AM, Dmitrii Dimandt <[EMAIL PROTECTED]> wrote: > > This is a problem I ran into with ErlyWeb, but I guess this affects all > other apps running under yaws. > > If I have a component named main_controller.erl in app A and another > component named main_controller.erl in app B, they will clash. That is, the > servere will only pickup the most recently compiled component (so it seems > though I can be completely wrong). > > Is there a way to "sandbox" these apps, to shield them from each other? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" 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/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
