https://typesense.org logo
Join Slack
Powered by
is 0.25-join ready for production uses?
# community-help
u
is 0.25-join ready for production uses?
k
Yes, it's in the final stretches of testing before release. We already have several customers using it on production.
u
it's glad to hear that. In fact, I believe that bazel will do a good job, but the only doubt is could I run into the same dependency problems like that?
k
Bazel builds everything in a sandbox so you should not face any issues. I've built it several times on vanilla VMs so it should build fine.
u
great👍, thanks a lot
k
Btw, the Typesense Docker images themselves use 
ubuntu:22.04
as base image.
The 
development.Dockerfile
uses an old image because we wanted an older glibc version so we can target older distros. That's used only for building the binary.
u
fantastic👍
hi Kishore, I also would like to know your workflow, like what kind of dev containers you use to view and edit code, and the ones you use to build the production-ready binaries
k
I don't use containers. That's one of the main reasons to switch to Bazel. The build is well sandboxed and just works so I just use native binary + development flow.
Clion / VS Code should support Bazel projects out of the box with appropriate plugins.
u
thanks🙂
yw 1
p
Is there a documentation for joins some where ?
k
That branch began for 
join
related work but we since decided to defer parts of it to 0.26 release so it's not fully functional.
u
hi, Kishore，I'm now on a centos7-based linux VM, using bazel 4.2.1 to build branch v0.25-join with command `bazel build ://typesense-server`like what you told me before，and still ran into problems. Could you plz help me here
Seems related to my local env, like gcc, make libs, etc. Maybe I should run bazel in a standard env like a docker ?
k
What version of gcc do you have on that machine?
u
8.2.0
k
I think that might be too old a version. Try with GCC 10.x or 11.x
u
should I use 1 or 2 for building typsense?
these 2 files are newly from v0.25-join compared to v0.24.1
k
Can you explain to me the rationale for building the Typesense Docker image again?
baze_dev.Dockerfile
just creates an image from Ubuntu 14.10 that contains GCC and Bazel. So that once it's created, you can build Typesense from within that container.
If you installed GCC 10 locally and tried the native Bazel build, it should work.
u
cool, that's what I need
@Kishore Nallan following your instruction, I finally suceed to build typesense-server with bazel, thanks a lot. Worth to point out, the original 
baze_dev.Dockerfile
was still not available for bazel building. Then I switch ubuntu image tag to 18.04, and it worked
k
Good to hear and thanks for the heads up.
Open in Slack
PreviousNext
Powered by