Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Updates to README to be more accurate. #267

Merged
merged 5 commits into from
Feb 8, 2024

Conversation

aulorbe
Copy link
Collaborator

@aulorbe aulorbe commented Jan 25, 2024

Problem

Quick updates to README to reflect current state of things.

Solution

Describe the approach you took. Link to any relevant bugs, issues, docs, or other resources.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Infrastructure change (CI configs, etc)
  • Non-code change (docs, etc)
  • None of the above: (explain here)

Test Plan

Describe specific steps for validating this change.

@aulorbe
Copy link
Collaborator Author

aulorbe commented Jan 25, 2024

@igiloh-pinecone Review?

README.md Outdated
@@ -258,6 +258,8 @@ To run the canopy server for production, please run:
gunicorn canopy_server.app:app --worker-class uvicorn.workers.UvicornWorker --bind 0.0.0.0:PORT --workers WORKER_COUNT
```

Note: replace `PORT` and `WORKER_COUNT` with values.
Copy link
Contributor

Choose a reason for hiding this comment

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

No, no, that's actually a typo 🤦 .
This was supposed to be $PORT and $WORKER_COUNT. And I guess these come from our docker image, where we explicitly set these env vars (with default, even if the user hasn't provided them).
Can you fix the typo please?

Copy link
Contributor

@igiloh-pinecone igiloh-pinecone Jan 25, 2024

Choose a reason for hiding this comment

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

Actually, I'm not even sure why @miararoy has changed the main README to use these env vars - unlike in the docker case, if someone just pip install canopy, he is not guaranteed to have those env vars at all. I think we should just revert to what we had before:

--bind 0.0.0.0:8000 --workers <number of desired worker processes>

@miararoy ?

Copy link
Contributor

@igiloh-pinecone igiloh-pinecone left a comment

Choose a reason for hiding this comment

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

@aulorbe all in all LGTM.

Please see my comment about that PORT and WORKER_COUNT thing. I think we should just go back to the original phrasing, and then we don't need more explanations later.

Changed the production recommendation - docker first, running gunicorn as alternative
Finalized reversing docker and gunicorn order
@igiloh-pinecone igiloh-pinecone added this pull request to the merge queue Feb 8, 2024
Merged via the queue into pinecone-io:main with commit a2cf274 Feb 8, 2024
7 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants