I have plans to implement exactly this in an app I'm building with Laravel, but the initial plan was to build it myself! Thanks to this video, I'll be bringing the feature to the users much sooner than anticipated! Thank you!
If you want to be 'clever'™ and eliminate any of the config duplication between the model and the front end, you can pass the index name and the searchable fields etc as a page prop, then using the `usePage` composable bind the values directly when building up your template so they never fall out of sync
man the php stuff was so clean. install the search, install scout and you're done. as soon as we come to the frontend it just shits itself with 3 things to get going to just display this stuff.
Full text db search is good, but lacks a lot of the speed and features of a dedicated solution. In most DBs you can't do facets, highlighting, snippets, semantic search, fuzzy, etc.
@@aarondfrancis Hm... facets seem like a relatively easy feature one could implement while constructing the search query (though I admit I haven't tried in practice, so I'm not sure about the performance impact; Just based on reading about what Typesence is doing in this regard...). The other features though, yeah, ok. Highlighting and snippets I imagine would have a significant performance overhead if implemented as extra columns in the search query's output (since they're effectively searching the text again to do the extraction/replacement), and semantic/fuzzy search is outright impossible without a purpose made fulltext parser.
For the example of "boolean", shouldn't the result with the "Booleans" title be first? According to the weight configuration, you configured in the typesense configuration.
Typesense is awesome! I use it to search through my countless family photos with handwritten descriptions. Fun stuff!
You've built a family portrait application in Laravel?
@@compton8301 Yep!
Sounds super cool tbh
@compton8301 I did, indeed!
@@aarondfrancis Thanks!
I have plans to implement exactly this in an app I'm building with Laravel, but the initial plan was to build it myself! Thanks to this video, I'll be bringing the feature to the users much sooner than anticipated! Thank you!
Perfect timing. I needed this for my kanban board livestream project. Thanks! ❤
Awesome library.
Thank you so much to share this type of awesome knowledge.
Hey Aaron, awesome video as always! Would be really cool to make one regarding faceted navigation/filters.
This is great content, by a great creator.
Thanks much!
You're kind to say so! Glad you're enjoying it.
If you want to be 'clever'™ and eliminate any of the config duplication between the model and the front end, you can pass the index name and the searchable fields etc as a page prop, then using the `usePage` composable bind the values directly when building up your template so they never fall out of sync
Ok that's pretty good. Pretty, pretty good
This video was awesome! Are you willing to share you PHPStorm Color Scheme? It looks so good!
Hey Aaron, will you self deploy / hosting typesense? If so please make a video.
execuse my ignorance, but how does this compare to elasticsearch?
Wow that's amazing 😮
man the php stuff was so clean. install the search, install scout and you're done. as soon as we come to the frontend it just shits itself with 3 things to get going to just display this stuff.
Haha, so it goes
@@aarondfrancis its still much better than what it used to be.
What is the difference between using this vs. a regular "fulltext" index and operator on the database level?
Full text db search is good, but lacks a lot of the speed and features of a dedicated solution. In most DBs you can't do facets, highlighting, snippets, semantic search, fuzzy, etc.
@@aarondfrancis Hm... facets seem like a relatively easy feature one could implement while constructing the search query (though I admit I haven't tried in practice, so I'm not sure about the performance impact; Just based on reading about what Typesence is doing in this regard...).
The other features though, yeah, ok.
Highlighting and snippets I imagine would have a significant performance overhead if implemented as extra columns in the search query's output (since they're effectively searching the text again to do the extraction/replacement), and semantic/fuzzy search is outright impossible without a purpose made fulltext parser.
Aaron, could you share your PHP Storm IDE settings, keymaps, etc? I've been trying to mimic yours, but couldn't achieve some results
Yes! Which parts were you unable to replicate?
For the example of "boolean", shouldn't the result with the "Booleans" title be first? According to the weight configuration, you configured in the typesense configuration.
Good question, I don't know. I'd need to look at the data! I'd have to check how many times "boolean" appears in each transcript
Thank you :)
"No PhD required." LOL
is there a good approach to make import command auto, each time we have new data (videos in this case), without setup a cron cmd
Calling save or create on any model with `use Searachable` will automatically add or update it in the index
Which theme are you using sir?
Watch the video. It's in there.
what is your chrome theme?
C'mon man, steamed mussels are delicious!
Better than pizza?! Get outta here
@@aarondfrancis Hear me out: steamed mussels ON a pizza ....
On second thoughts, never mind. I'll get my coat...
@@prevailrob blocked and reported
What code editor do you use?
phpStorm
Yup!
When using the client side adapter and vue package, 'Importing the models' step is skipped? If yes, how does typsense know about the models?
using php artisan scout:import
Yup exactly
@@koossaayy but do we need to do it each time we have new records in the model,