- Process nested subQuestions (previously silently dropped) - Sanitize phase names for summary filenames (path traversal) - Proper urllib.request import (was __import__ hack) - Add README, MIT LICENSE, pyproject (activates CI lint/test/security) - 19 tests: validation, slug, question tree, Ollama fetch (mocked), end-to-end main()
37 lines
2.4 KiB
Plaintext
37 lines
2.4 KiB
Plaintext
## Brief Description
|
|
I have a local deployment of Meilisearch going. It's job is going to be to provide an alternative to Google for a very wide amount of resources on a local internet. The current resources the internet has are the following.
|
|
|
|
- Downloaded Youtube videos (Jellyfin Urls)
|
|
- MKV Backups of Blurays (jellyfin urls)
|
|
- A local copy of Wikipedia
|
|
- Constantly updating archive of papers from Arxiv
|
|
- Local copies of Blogs from people on substack
|
|
- Archive copies of pages from websites like reddit and many news websites (mainly available via archivebox at archive.example.com urls)
|
|
|
|
I really need a google like UI for being able to search through all of this content. You can assume some other process will handling indexing all this material,but I really need someone's help to build the UI. It needs to be responsive and fast. I'm thinking we can try making a react app, since everything is on the local network and there's no bandwidth concerns.
|
|
|
|
When typing in something to the big query bar, it'd be good if you saw suggested queries or it start auto querying and showing suggested results on the bottom. When the user presses enter, it'd be nice to show a google like interface of the top links for the person to be able to click through. And of course have pagination buttons for the user to click for the next set of links.
|
|
|
|
## Required tech
|
|
React
|
|
|
|
### Hardware running on
|
|
### CPU = AMD 9950x3d
|
|
### Ram = 192 GB of DDR5 RAM
|
|
### GPU = RTX 5090 32GB + RTX 5060 TI 16GB
|
|
|
|
## User Count = 10
|
|
## Commercial or Open Source = Open Source
|
|
## Who is it for?
|
|
|
|
Mainly humans will be using it. Once again, it's going to be an easy way to index through all the content on the server. I expect other media to come online like local social media content or pinterest like content. Maybe some iamges will get generated in the future too, so some image interface that's like google would be good too, but we don't have to do that in this prototype. Maybe mark this as a follow up though.
|
|
|
|
## Project Goals
|
|
- Goal 1: Build the UI that integrates easily into our currently running Meilisearch server
|
|
- Goal 2: Make it very similar and easy to use as Google, since that's what many of the users are already used to.
|
|
- Goal 3: Make sure we can add features like looking at just images in the future.
|
|
- Goal 4: Make sure it's pretty and very reactive. Should use a modern tech stack
|
|
## How to Test
|
|
|
|
Mainly make sure it's very pretty and of course works with a locally running Meilisearch server.
|