Do you think that converting special separator characters like colon, dash,
and period to underscore as the default convention for creating environment
variables would work?


On Thu, Feb 6, 2014 at 4:57 PM, Michael Elsdörfer
<notifications@github.com>wrote:

> In expose.go:
>
> > +	"os/exec"
> > +	"strings"
> > +	"sync"
> > +	"syscall"
> > +	"time"
> > +)
> > +
> > +type dependencySpec struct {
> > +	service, targetVar string
> > +}
> > +
> > +// A flag.Value that is a list of dependencies
> > +type depSlice []dependencySpec
> > +
> > +func (s *depSlice) String() string {
> > +	return fmt.Sprint("ENV:service-name, -d=service-name")
>
> @progrium <https://github.com/progrium> suggested to follow the variables
> that docker --link uses. This currently isn't done. It is a good idea, but
> apart from the ${name}_PORT variable, all the others include the actual
> port number, which would mean parsing the value returned from discoverd.
>
> Part of what I am struggling with here is that I see myself using symbols
> in the service names. I want to differentiate between app1:db and app2:db.
> So you can't just uppercase it to convert it to an env var.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/flynn/sdutil/pull/6/files#r9523176>
> .
>



-- 
Jeff Lindsay
http://progrium.com