#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.

1mo

Join the chat

Oct 18, 2023 (1 month ago)

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.

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.

Photo of md5-e9650f83698ba5d9d8c7319af1a16ea4

KC

07:46 PM

We integrated it with Magento.

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

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Discussing Features for Typesense Cloud Dashboard

Stephano expressed the need for a Typesense Cloud dashboard to manage collections. Jason confirmed its development, also including features like editing and deleting items. James and Mica added comments about API key management and self-hosted Typesense compatibility.

32mo

Contributing to project using JS, TS, Go and PHP

Matthew volunteered to contribute to the project using JavaScript, Typescript, Go, and PHP. Jason assigned two tasks, including Laravel integration and nest.js library. hi019 encouraged Matthew to try out the Laravel integration.

29mo

Understanding and Implementing Typesense Dart Library with Flutter

Alexandro sought help with the Typesense Dart library. Jason explained that the library is in progress, discussed utilizing other HTTP libraries, and provided detailed instructions on utilizing Typesense with Flutter. Alexandro provided feedback on the Typesense UI and expressed interest in creating a tutorial video.

32mo