pewdiepie-archdaemon/odysseus

Took a crack at this on my fork ([phetzy:feat/ghcr-prebuilt-images](https://github.com/phetzy/odysseus/tree/feat/ghcr-prebuilt-images)). There is some overlap with #165 since it already does the build-and-push-to-GHCR part, I just went a somewhat different route and figured I'd put it out there.

What I did differently:
- Left docker-compose.yml alone so contributors keep build: ., and added a separate docker-compose.prebuilt.yml that pulls the image instead. So the no-build path is opt-in and nobody's dev setup breaks.
- Builds arm64 alongside amd64 on releases — saw the zimaOS/Pi asks above and wanted those covered.
- Added an "Option 2: Prebuilt image" blurb to the README quickstart, since the issue specifically asked for an example
compose.
- Kept the workflow lean: packages: write only, no auto-tagging, build cache, and PRs just build-validate without pushing
anything.

Totally fine if you'd rather go with #165 or have me fold these bits into it — whatever saves every...

+1 For prebuilt images.

> > manually pull, update, and build
>
> It's not that much work to just copy paste this block
>
> git clone https://github.com/pewdiepie-archdaemon/odysseus
> cd odysseus
> cp .env.example .env # optional, but recommended for explicit defaults
> docker compose up -d --build
>
> in your terminal.

on the other hand why have all these cpu & bandwith wasted if we could all just download one clean artifact?

My bad! I sent the wrong link. This actually uses bcrypt hashing. Try this:
https://bcrypt-generator.com/

> I managed to kinda force myself in by creating my own user. Go to `/data/auth.json`
>
> {
> "users": {
> "admin": {
> "password_hash": "(hashed password)",
> "is_admin": true
> },
> "admin2": {
> "password_hash": "(insert password hash here)",
> "is_admin": true
> }
> }
> }
> I went to this website https://emn178.github.io/online-tools/sha256.html to create a hashed password, copied it and pasted it for the new admin user.

Thanks I tried that and got - Unexpected token 'I', "Internal S"... is not valid JSON.

I've never known it to be so hard to get a local app running. Ridiculous!!!

I managed to kinda force myself in by creating my own user.
Go to ```/data/auth.json```

```json
{
"users": {
"admin": {
"password_hash": "(hashed password)",
"is_admin": true
},
"admin2": {
"password_hash": "(insert password hash here)",
"is_admin": true
}
}
}
```

I went to this website https://emn178.github.io/online-tools/sha256.html to create a hashed password, copied it and pasted it for the new admin user.

It only gives you the temporary password during the initial installation. The username is always **Admin**.

okay, how about these questions…

## **is Obsidian compatibility appropriate?**

what even is this project? can it replace a file based notes app like Obsidian? how similar are this project's note features to Obsidian's?

*I was recently trying to set up my Obsidian vault inside Open WebUI. keeping everything in sync was a bit painful. to me, it makes sense for notes, document lookup/metadata and research tools to live together, but I haven't figured out the workflow yet.*

## **vaults and filesystem**

### **how does this thing even store notes?**

does this project store notes in a database, or as plain files (with metadata in the database)?

if it's a one way trip to a database, then we can't reopen files in the vault in other programs anymore (e.g. editing an SVG in inkscape)

what would it take to reproduce vaults/notes as raw markdown files, with version history, RAG indexing and whatever else in the database?

### **can we import an Obsidian vault directory?**

e.g.

* a contain...

Thanks very much for the help. However unfortunately, teh system is not giving me any login details on setup.py. It's skipping it.

PS D:\> cd odysseus\odysseus
PS D:\odysseus\odysseus> python setup.py

=== Odysseus Setup ===

1. Creating directories...
[ok] data/
[ok] data\uploads/
[ok] data\personal_docs/
[ok] data\personal_uploads/
[ok] data\tts_cache/
[ok] data\generated_images/
[ok] data\deep_research/
[ok] data\chroma/
[ok] data\rag/
[ok] data\memory_vectors/
[ok] logs/

2. Environment file...
[skip] .env already exists

3. Checking dependencies...
[ok] All core dependencies installed

4. Initializing database...
[ok] Database initialized

5. Creating initial admin...
[skip] auth.json already exists

=== Setup complete ===

Start the server with:
uvicorn app:app --host 0.0.0.0 --port 7000

Then open http://localhost:7000
Login with the admin username and temporary password printed above.

PS D:\odysseus\odysseus>

> Took only two simple fixes to get it to start up at least, the only immediate blockers to getting the main UI were use of pty and fcntl in shell_routes.py. Install pywinpty and winfcntl with pip and replace the imports for them at the top of shell_routes.py with this:
>
> ```
> import winpty as pty
> import winfcntl as fcntl
> ```
>
> Also, if you have git automatically convert line endings (or maybe just in general due to Windows vs Linux file loading) your _serve_html_with_nonce on line 601 of app.py may error out after login, just adding a ", encoding='utf-8'" to the open on line 603 resolved that. I'm sure I'll run into more issues, but that got me in at least.
>
> Quick edit: someone already beat me to the pull request, it's at [#149](https://github.com/pewdiepie-archdaemon/odysseus/pull/149)

thx a lot for your explanatin but it changed nothing on my side, also i tried with py3.14.5 ans 3.12.7 but nothing change.
i still get the exact same output as rocantonio

> https://www.youtube.com/watch?v=rAzT5lcezPs&t=938s

But there is a Windows install instruction in the Readme!

can someone tell me how to get past the login screen with any auth details? I haven't set anything and so have no clue how to get in.

Took only two simple fixes to get it to start up at least, the only immediate blockers to getting the main UI were use of pty and fcntl in shell_routes.py. Install pywinpty and winfcntl with pip and replace the imports for them at the top of shell_routes.py with this:

```
import winpty as pty
import winfcntl as fcntl
```

Also, if you have git automatically convert line endings (or maybe just in general due to Windows vs Linux file loading) your _serve_html_with_nonce on line 601 of app.py may error out after login, just adding a ", encoding='utf-8'" to the open on line 603 resolved that. I'm sure I'll run into more issues, but that got me in at least.

Quick edit: someone already beat me to the pull request, it's at #149

> It's not that much work to just copy paste this block
>
> git clone https://github.com/pewdiepie-archdaemon/odysseus
> cd odysseus
> cp .env.example .env # optional, but recommended for explicit defaults
> docker compose up -d --build
>
> in your terminal.

That wouldn't work on something like zimaOS.

Edit: Yes, ZVM is an option, but that sounds like an annoying way to do it.

https://www.youtube.com/watch?v=rAzT5lcezPs&t=938s