Skip to content
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

Add a new blog article for Ray Serve #31531

Merged
merged 1 commit into from
Jan 9, 2023
Merged

Conversation

jbesomi
Copy link
Contributor

@jbesomi jbesomi commented Jan 9, 2023

I recently discovered Ray.io and think it's fantastic! Congratulations on creating such a great tool. I tried to set-up Ray Serve on a remote cluster last week and found the documentation to be missing some important information, so I wrote an article about it in the hopes of helping others better understand how to use it. Keep up the great work! 💪

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.

I recently discovered Ray.io and think it's fantastic! Congratulations on creating such a great tool. 
I tried to set-up Ray Serve on a remote cluster last week and found the documentation to be missing some important information, so I wrote an article about it in the hopes of helping others better understand how to use it. 
Keep up the great work! 💪

Signed-off-by: Jonathan Besomi <jonathanbesomi@gmail.com>
@jbesomi jbesomi requested a review from a team as a code owner January 9, 2023 12:57
Copy link
Contributor

@richardliaw richardliaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey this is awesome! thanks a bunch for your contribution!

how do we improve our documentation, if you don't mind me asking?

@richardliaw richardliaw merged commit 667b595 into ray-project:master Jan 9, 2023
@jbesomi
Copy link
Contributor Author

jbesomi commented Jan 9, 2023

I don't mind at all.

I would organise the content in a more structured way as well as reduce the levels of nested content.

For instance, assuming each service has it's own CLI, I would opt for a structure like:

Tool A:

  • CLI Tool A
  • ...

Tool B

  • CLI Tool B
  • ...

As of now, to find the "Ray Serve Config" one needs to go to (Ray Serve > User Guides > Production Guide > Serve Config Files).

Hope this helps. Happy to provide more advices/support if needed.

@richardliaw
Copy link
Contributor

I just realized.... you're the texthero author? I love that package :)

@richardliaw
Copy link
Contributor

And thanks for the feedback btw! I've forwarded it to the team.

@jbesomi
Copy link
Contributor Author

jbesomi commented Jan 12, 2023

Glad you like Texthero :) I am currently working on a new next-gen package/product for ML (and considering using ray for the cloud/compute part), hopefully you will love that too 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants