Closed titaniumbones closed 5 years ago
+1 and as an open source org we should adopt documentation practices as part of development flow! Needs to support new contributors as well as be flexible to participants who drop in/out as their availability changes
Figured it out!
Prereq for doing anything:
To just run locally:
go get github.com/edgi-govdata-archiving/eis-search
, (run this from any directory)cd
into $HOME/go/bin
, you can run ./eis-search
and it will serve up at http://localhost:8094To clone & modify (not dependent on the "just running" instructions above):
$HOME/go/src
ordinarily. go get
put dependencies in $HOME/go/bin
for you).go build
. This should make a file called eis-search
./eis-search
. Go see it at http://localhost:8094The main Go newbie gotcha, as far as I can tell:
$HOME/go
. You're supposed to do all your Go work within that folder
steps to clone/build/run on localhost are probably obvious to go people but I'm having some trouble doing this is a non-go person. Would love to see the instructions in the README so illiterates like myself can try running locally & adidng e.g. extra HTML to make some things obvious to potential users/ testers.