-
Notifications
You must be signed in to change notification settings - Fork 21
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
Improve documentation and README #82
Conversation
README.md
Outdated
@@ -9,16 +14,22 @@ The easiest way to deploy **dashboard** is using *Docker*. | |||
docker run -p 8080:80 bblfsh/dashboard -bblfsh-addr <bblfsh-server-addr> |
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.
include a header to say that is the recomended way.
README.md
Outdated
If you don't have a bblfsh server running you can execute the dashboard and the server using the following command: | ||
If you don't have a bblfsh server running, please read the [getting started](https://doc.bblf.sh/user/getting-started.html) guide, to learn more about how to use and deploy a bblfsh server. | ||
|
||
If don't want to run **dashboard** using our *Docker* image you can download a binary from [releases](https://github.com/bblfsh/dashboard/releases) page and run it as |
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.
make a header, to clarify that this is not the recomended way, or just simple remove this paragraph.
README.md
Outdated
``` | ||
|
||
Please read the [getting started](https://doc.bblf.sh/user/getting-started.html) guide, to learn more about how to use and deploy a bblfsh server. | ||
## Architecture |
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.
This is not relevant for user, only for contributors, remove from here and place in a CONTRIBUTING.md
file.
README.md
Outdated
@@ -41,6 +52,18 @@ make serve | |||
|
|||
And access the dashboard through http://localhost:9999 | |||
|
|||
### Hot reloading mode |
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.
Not relevant for the user, remove from here.
README.md
Outdated
|
||
It's user-friendly tool for testing and research how babelfish parse code. | ||
|
||
![Screenshot](docs/screenshot.png?raw=true) |
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.
move the image to a images
folder or something
I moved all developer-related information to |
CONTRIBUTING.md
Outdated
|
||
Contributions require sign-off. The sign-off is a simple line at the end of the commit message for the patch or pull request, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch. The rules are pretty simple: if you can certify the below: | ||
source{d} go-git project is [GPLv3](LICENSE) and accept |
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.
go-git? ;)
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.
haha. thanks!!!
README.md
Outdated
``` | ||
|
||
### Access the dashboard locally | ||
### Not recommended |
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.
Just say standalone or something, is ok if the people want to used :D
README.md
Outdated
```sh | ||
make assets | ||
docker run -p 8080:80 bblfsh/dashboard -bblfsh-addr <bblfsh-server-addr> |
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.
Maybe we can explain a little bit more, about, the por being opened, etc.
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.
Very nice!
One minor thing - can we please link CONTRIBUTING.md from the README i.e by having a development section, same way as we point out location of the LICENSE file?
This would remove unnecessary guesswork for the first-time contributors.
Updated. |
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.
Great! At least we have more info on how to launch the dashboard! Good work;
I'd consider the following
|
||
```sh | ||
docker run --privileged -d -p 9432:9432 --name bblfsh bblfsh/server | ||
docker run -p 8080:80 --link bblfsh bblfsh/dashboard -bblfsh-addr bblfsh:9432 |
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.
I don't think it's a good idea to hide this info. People might find useful to launch the dashboard without knowing about docker or bblfsh, and these 2 lines solve it without extra effort on our side.
(It may be moved to the CONTRIBUTING#development
section)
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.
I just did what Maximo said:
#66 (comment)
CONTRIBUTING.md
Outdated
|
||
The dashboard contains 2 parts: | ||
|
||
- Single page react application |
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.
I'd add:
bootstrapped with [Create React App](https://github.com/facebookincubator/create-react-app)
so people will be able to dig a bit more into its architecture.
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.
not sure it worth to mention, but added
CONTRIBUTING.md
Outdated
- Single page react application | ||
- Go web server to proxy and transform requests to bblfsd server | ||
|
||
For production usage we embed static javascript into go server using [go-bindata](https://github.com/jteeuwen/go-bindata). |
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.
Not only js code; I'd reword to something like:
For production usage, all static files are served from the go server after being embed in the server itself using go-bindata.
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.
👍
```sh | ||
make assets | ||
``` | ||
|
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.
I'd add how to run the tests:
CI=true yarn test`
go test ./server/...
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.
by the way why CI=true? usually CI env variable means to change output format (from human readable to CI readable), but in our case there is no difference.
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.
added sections about running tests
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.
the default format when CI
is not set is "interactive" what is a pain for me. But ok, lets the user to decide about it
CONTRIBUTING.md
Outdated
|
||
Dashboard will be available on http://localhost:3000 | ||
|
||
But it still requires go server on `9999` port to be available. |
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.
To do so it can be run:
go install github.com/bblfsh/dashboard/server/...
bblfsh-dashboard -bblfsh-addr=0.0.0.0:9432
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.
better go run server/cmd/bblfsh-dashboard/main.go
, not sure it worth to mention here though. make serve
mentioned before works just fine.
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.
I agree with the go run
instead of the go install + run it
. Way simpler.
About if it worth to mention it, I think it does. In this section, it is said how to run (for development purposes) the dashboard, and it is warned that the server is needed if it's proceded that way.
I think it worth to mention it to let the user launch the front and the back separately and explore its internals. Using make serve
for this purpose is more confused because it does things not really needed for this goal and way slower by the same reason.
README.md
Outdated
|
||
And access the dashboard through http://localhost:9999 | ||
Please take a look at [CONTRIBUTING](CONTRIBUTING.md) file to see how to contribute in this project. |
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.
I'd add something like:
and get more info about the dashboard architecture and how to launch it for development purposes
With links to that sections.
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.
👍
Great, thanks, |
Added. |
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.
LGTM
Since all comments has been already addressed, you can now squash and merge 💃
Fix #37 Signed-off-by: smacker <max@smacker.ru>
Fix #37
I tried to keep it short and simple.