New year release of 0.2.0

[kcubeterm]

No matter what we will release achoz on the eve of new year for sure. This release will have following features and usable and functional.

• Logger (Logs helps in figure out issue)
• Test unit
• PDF viewer
• Video preview
• Audio preview
• Image preview
• Add support of Meilisearch as well
• Efficient indexing and more robust crawler.

Why need meilisearch ?
Meilisearch support arm and aarch64 devices unlike typesense. With meilisearch achoz will run on Android device with Termux.

[cauerego]

i would choose "efficient indexing and more robust crawler" to come next! 😁

[cauerego]

except, a "general viewer" is very important!

let me explain...

in theory, we will always have terminal (at least SSH) access to the server, right? so perhaps every search result should link to some direct way of opening files... regardless of viewers (such as pdf viewer).

[kcubeterm]

yes, every result is linked with file but indirectly. client have to request file with its id from server. this function is responsible to serve file. i used id to request files so that any type of command injection or unindexed file request could be avoided.

achoz/server.js

Line 68 in 86adaa0

function filereq(req, res) {

[kcubeterm]

also, do you mean that search result files could be open with another application in device as well ? then that could be done with xdg but only if achoz is hosted in same device

[cauerego]

if we have SSH access, it's more a matter of linking to a protocol which can be opened either locally or remotely, it shouldn't matter.

the injection prevention is fine. and showing the path to the file is already a nice touch... at least we can already manually open it.

in other words, if we have SSH access, then we should have some way to directly open the file from the web browser...

but on a second thought, to make everything easier:

just offer a link to open the file!

let the browser decide what to do with it.

[cauerego]

you sure meilisearch is needed for running on android?! 🤔

[kcubeterm]

we just need a search engine which support arm and aarch64 and as of now typesense dont support

[cauerego]

i can't imagine how any code written in the past decade wouldn't be able to compile in any end user processor... what do you mean, it doesn't support arm?

[cauerego]

got my answer directly from the source... Kishore:

Typesense and its dependencies make some assumptions about an X86 architecture which must be addressed before we can build on ARM.

but even before that, he gave us another idea:

run Typesense as a service and use the Java client for access.

makes sense? 😁

[kcubeterm]

Make sense offcourse and it has already implemented. If this would be case then user just need to tweak "TypesenseHost" and "TypesenseApi" in config.json

[cauerego]

to me, i still can't make much sense why they needed to make those assumptions... 🤣

feels way too much like over optimization.