Deployment on Render.com

[ericmand]

trafficstars

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes

• New functionality
  • Adds a deployment plan for Render.com
  • Made no changes to existing files. Just added a couple small files to support the deployment plan.

Test plan

I was able to execute the javascript example via render. I did no further testing.

Documentation Changes

I've submitted a button to docs if you want that.

[ericmand]

Note that due to https://github.com/chroma-core/chroma/pull/208 the python client won't work with this as it only works on http and Render is https. Javascript and direct to API are fine.

[ericmand]

If you like this, but don't want it in the repo, you can also point to another repo that looks like: https://github.com/ericmand/render-chroma

[jeffchuber]

thanks @ericmand !

A little background, and then a few questions.

We've decided that Clickhouse is not the right tool for the job here and we are working on a custom distributed systems backend to replace it in the client-server version of Chroma. This will take a few months of effort.

That being said: we are committed to keeping the existing stack operational for folks as well as enabling a seamless migration when the day comes to move over.

For that reason - we want people who need a hosted service today to use Clickhouse so they can get up and running, but also want to ensure that users who do that know something about devops and be able to debug issues, scale properly, etc.

For that reason, I am game to add Render as a deployment target, however for now I'd like to keep it out of the main readme. I think it is however a good idea to include it in the docs on the deployment page.

Additionally, do you think it would be possible to move the render.yaml out of the main directory as well? I don't know what flexibility Render provides there.

Let me know your thoughts!

[ericmand]

Makes sense (I thought the Clickhouse dependency seemed clever but wondered if it would be optimal). render.yaml must be in the root. Maybe the best way to accomplish what you want is to have the link in the documentation to a separate repo.

[jeffchuber]

@ericmand do you mind handling the one Readme conflict? we just keep everything in chroma:main https://github.com/chroma-core/chroma/blob/main/README.md

[ericmand]

If this isn't satisfactory I'll do a rebase.

[jeffchuber]

@ericmand following up on this! Sorry this fell through the cracks. Currently the core team is working on a large refactor of the hosted product that will change how deployment guides like this work in a large way.

I am going to close this for now and then we can re-open it once those changes have been landed assuming Render is still a good target for that infra.

thanks!