#community-help

Discussing Implementation of Typesense without Source Code Access

TLDR Helder queries about installing typesense without source code access for client-side e-commerce. Michael expresses doubts and recommends direct dev team involvement or access granting. KC mentions their integration with Magento. The discussion remains open-ended.

Powered by Struct AI
Oct 18, 2023 (1 month ago)
Helder
Photo of md5-8b19dd62e3d1daa2a391387ff467175e
Helder
11:10 AM
Hi everyone, in order to be easier to install typesense in some of my clients ( we are a digital marketing agency ), in which we have not developed the E-commerce, and normally we have limited access to source code. We are thinking of developing something like doofinder has. A simple configuration and a JS import that builds the search interface.
Michael
Photo of md5-ab9a5d60cb7ebd0211d1a368b45a0473
Michael
11:19 AM
I'm truly wondering how you'd tackle this without access to the source code? There are API keys etc... involved to connect (which I would not put in any source code openly) the schema needs to be built and so on. Without source code access and data filtering that seems hard to do.

If we come accross these kind of clients, that only use us for digital marketing, we bounce the ball back and tell them flat out:

Hey let your dev team implement this or ... allow us to take part of the development and give access.

It's much better than trying to build "bandaid" solutions, almost the same as throwing an accessibility modal thing and hoping it complies to everything.
KC
Photo of md5-e9650f83698ba5d9d8c7319af1a16ea4
KC
07:46 PM
We integrated it with Magento.
Helder
Photo of md5-8b19dd62e3d1daa2a391387ff467175e
Helder
08:42 PM
Hi Michael, when you build an interface using a client side ( per example nodejs )
08:42
Helder
08:42 PM
the api keys are exposed