While I understand that local containers are intended for a quick cycle of charms development, it'd be great if there was an easy way to expose them to the world - so you could use juju on your server or home computer as a server.
I understand there is the packaging system, tasksel and PPAs - but the first two are too restrictive in admissions and thus have a lower selection of software available. PPAs are great, but aren't suited for DevOps like juju is exactly intended for. While I understand juju is headed for the cloud, the ease with with you can setup charms locally is amazing and the charm store is a pretty brilliant idea that already seems to be bristling with a variety of software even though it's in beta.
All that's missing though is exposing the LXC instances over the network - and it's a bit of a complicated business for someone who doesn't reason in networking too well. If this was easily available, then it'd be great to be able to use juju charms locally or on your non-cloud server, and would expand juju's field of possible applications, if the designers agree with it.
I've been close to getting this to work by installing an NGINX reverse proxy on the Host OS and configuring it to redirect incoming HTTP and HTTPS to the HOST IP to that of the Juju-GUI IP in a local provider LXC container.
The juju-gui menu appears with a spinning disk & message "Connecting to juju environment" and just keeps spinning.
So far I think the problem may be connected with juju-gui's use of websocket back to the remote pc//laptop via the Host IP & the Reverse Proxy.
Anyway... I too would like to see this use-case supported somehow.