-
Notifications
You must be signed in to change notification settings - Fork 515
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
docs: update the image in the USER_GUIDE.md #1683 #1689
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1689 +/- ##
==========================================
+ Coverage 72.41% 73.99% +1.57%
==========================================
Files 133 86 -47
Lines 5728 2615 -3113
Branches 666 668 +2
==========================================
- Hits 4148 1935 -2213
+ Misses 1337 680 -657
+ Partials 243 0 -243
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@nic-chen @Firstsawyou @liuxiran can you check for the failing test? |
Hii, it seems the failed test is unrelated to this PR. Can we retrigger the actions @juzhiyuan? |
This isn't my fault ,then? |
Yes i think we have to retrigger |
@bisakhmondal @iamayushdas Ya, that's due to Backend, just wait for @nic-chen @starsz to fix. |
This is because when verifying the version number, the You could submit another commit to avoid this problem. To fix this problem, we could change this line of code if [[ `grep -c -w "${VERSION}" ${STDOUT}` -ne '1' ]]; then I think you could submit another PR to fix it. Thanks. |
On it! 😊 |
related PR: #1696 |
Could you please retrigger CI @juzhiyuan |
Since PR #1696 is merged. I think you should merge the master branch and fix the conflicts. |
Have a review to this😀 |
@juzhiyuan have a look to this |
@@ -59,7 +59,7 @@ We can debug a route both published or offline with the online debug function, w | |||
|
|||
2. Debug a offline route | |||
|
|||
![route-debug-offline](../../assets/images/route-debug-offline.png) | |||
![route-debug-offline](https://user-images.githubusercontent.com/40708551/112923419-e5cd7280-912b-11eb-8e7e-57c3c4fe31ef.png) |
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.
actually, it supports not only Upstream URL, but also API Gateway's Endpoint
|
||
We support the monitor page by referencing it in [iframe](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe). Before accessing [Grafana](https://grafana.com/), please Enable [`allow_embedding=true`](https://grafana.com/docs/grafana/latest/administration/configuration/#allow_embedding), which defaults to `false`. This causes the browser to fail to render Grafana pages properly due to security policies. | ||
|
||
![metrics-en](../../assets/images/metrics-en.png) | ||
![Dashboard-en](https://user-images.githubusercontent.com/40708551/112922395-0eed0380-912a-11eb-8c92-4c67d2bae4a8.png) |
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.
@iamayushdas thank you for this. I was wondering that where the new image file is located.
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.
GitHub CDN?
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.
GitHub CDN?
Yep, absolutely I think. My concern is how could us maintain these images. Previous images were maintained in this repository, while the new images seem not.
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.
@iamayushdas thank you for this. I was wondering that where the new image file is located.
My pleasure sir!
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.
🤔 that's a problem.
- If we put them in our repo, it's easy to maintain actually, but will make the
pull
action slower; - if we put them in the CDN, we need to upload them when updating the images, but will speedup the pull action.
Both are ok to me, how about others' opinion?
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.
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.
Hii all, want to add something. We could also go for git lfs
(faster pull). The CDN approach is okay until we need to update those static files in future releases where pinpointing the content through its CDN URL will be a huge pain in the neck. On the other hand, relative links .... (you know, just update the static file, that's it, hehe) :)
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.
but don't you think we should only go for that if we are handling large files?
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, there is no exact threshold to consider what is a large file, isn't it!! Just said about another available option with better docs management (IMO) :)
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 😊
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
Thank you @iamayushdas .
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, thanks a lot
do we need to update docs about how to upload images when someone, like me not familiar with Github CDN, wants to update the images in the user_guide? @juzhiyuan
ya, we could move this part to our website :) |
Anyone would like to crate an issue to track this? |
ya sure! |
@juzhiyuan there is a problem i guess. See: here in docs its perfectly ok |
alive now, that's due to we need to rebuild our website./ |
While editing the |
Please answer these questions before submitting a pull request, or your PR will get closed.
Why submit this pull request?
What changes will this PR take into?
updated the screenshots of USER_GUIDE
Please update this section with detailed description.
Related issues
fix/resolve #1683
Checklist: