-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A start for setup instructions #6
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
Initial setup | ||
============= | ||
```bash | ||
git clone --recurse-submodules [email protected]:gtfierro/hoddb.git | ||
cd hoddb | ||
``` | ||
|
||
Install go | ||
========== | ||
* [Install go](https://golang.org/doc/install) | ||
* source setup.sh: | ||
```bash | ||
. /setup.sh | ||
Comment on lines
+11
to
+13
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I remember correctly, dependencies should be taken care of by the existing Go tooling. Just run
from inside the project directory. I'd prefer to handle dependencies that way, as it is standard for most Go projects. Also, the |
||
``` | ||
|
||
You should now be able to run: | ||
```bash | ||
make proto | ||
make build | ||
make test | ||
make run | ||
``` | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
export PATH=$PATH:/usr/local/go/bin | ||
# the following will place three binaries in your $GOBIN ($HOME/go/bin) | ||
go get -u github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway | ||
go get -u github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger | ||
go get -u github.com/golang/protobuf/protoc-gen-go | ||
export PATH=$PATH:$HOME/go/bin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Headers in Markdown are
Can we put the contents of
setup.md
intoREADME.md
under a## Setup
heading? I think it is best to have all of this in one location