Proposal: build separate binaries for proxy & registry about athens HOT 8 CLOSED

how could we keep the existing "buffalo dev" workflow?

from athens.

we can experiment and see how much "buffalo dev" is tied to the layout of the project.

from athens.

My original thought was to put a full buffalo application into each of cmd/proxy and cmd/registry, so you would run buffalo dev inside of either directory. This fits nicely into the standard buffalo tooling without any modifications.

The only thing that I'm sure of with buffalo dev itself is that it needs the .buffalo.dev.yml to run, and I think it needs a main. I know you and @markbates figured some things out and I'm not caught up on that.

I'd just advocate for keeping plain buffalo dev without any additional setup (besides DB setup) on the machine. In other words, I'd like to keep the workflow this:

# do this once
$ git clone [email protected]:gomods/athens.git
$ cd athens
$ docker-compose up -d
$ buffalo db migrate up

# now do this as many times as you want
$ buffalo dev

(note - our README describes almost all of this flow, except for the buffalo db migrate up part)

from athens.

I agree with Aaron. Also, you could make a grift task in Athens that did all the docker, migration, seed, etc… then no matter happens the docks say run buffalo t setup the first tome. :)

from athens.

ooooh, the grift for all the migration etc... is an awesome idea. thanks @markbates!

from athens.

I'll take this one

from athens.

See #87, close together

from athens.

#91 fixes this, closing

from athens.