@Jezo247, That is very strange. That should be all you need to do.

Let's have you try this:
Open a powershell window (or terminal of some kind), then put in the following:
cd C;\PATH\TO\SCRIBERR\REPO\FOLDER
then
docker compose build

It should then build the container, once that is done:

docker compose up -d

See if that works. If you get stuck somewhere. Let me know.

This is just a temporary workaround. There should be new containers that can be pulled directly from this repo, without needing to build it.

@Jezo247, Looks like the new nightly image is there, you can change the docker image that is pulled from main to nightly. If you have the latest .env file, you specify it in there, or you can just slap it in the docker-compose.yml file, replacing this:
ghcr.io/rishikanthc/scriberr:${IMAGE_TAG:-main}
with
ghcr.io/rishikanthc/scriberr:nightly

or, if you have the new .env file from this:
IMAGE_TAG=main # Docker image tag to use for building the Docker image
to this
IMAGE_TAG=night # Docker image tag to use for building the Docker image

That should already have everything ready to go for you, no need to build anything. And there will be a Nvidia container coming soon. Just want to get my changes reviewed before pushing that change to the main branch, since it changed a decent amount of things.

Once you have the image updated for the docker-compose.yml file, and your .env file is good to go, then you just us docker compose up -d and once it pulls the image, you should be up and running.

NOTE: Make sure to clear out any of the images that are stored in docker for Scriberr. Don't delete the volumes, but delete all of the images that are associated with Scriberr, so it doesn't try to pull it from a cache on your machine instead of pulling from the repo.

OK, I deleted all containers and all images from docker.
I did the 'night' changes and ran docker compose up -d. Builds OK and app runs. I did the config step, OK. I get the 3000 interface, but get errors when uploading a file.

and

Oh that is a bit of a bug. You need to log out and back into Scriberr. I have noticed that as well.

This happens because the old login token stays cached in the browser. So we need to logout and log back in to get a new token.
The correct way to handle this is to check expiry of token and issue a new one if expired.

OK. Success! After some troubles with docker "unexpected errors" and a uninstall and re-install, I got the container erbuilt from the nightly image. The app now works well and the log-out.login solved the error from before. I even managed to get diarization working for me which had failed before. I noticed that I had to add both pyannote/diarization AND pyannote/segmentation repos to my auth access key - (this would be good to note clearly in the documentation.)
Last step that fails for me is the summarisation. I'm using ollama but it looks like the app makes an API call to OpenAI, despite leaving the key field blank and the .env setting URL pointing to my PC'sIP:11434 for ollama. Is there a setting in the .env file/docker-compose to force summarisation to use ollama?

@Jezo247, are you also adding the /v1 to the end of the host for ollama? Or are you just adding the port after it?

Ah! I missed the /v1. I'll put that in and re-test.

Ah! I missed the /v1. I'll put that in and re-test.

Not a problem! Let me know if it works.

Also for this:

I noticed that I had to add both pyannote/diarization AND pyannote/segmentation repos to my auth access key - (this would be good to note clearly in the documentation.)

I opened up #68, and will get that updated by the next full release.

ok, added the missing /v1/ but it still seems to fail on the summarisation.

You need to add a key, it can be even 1 character. But it does require a key (this is a python dependency thing, but it can be looked into to fix this for future releases).

So just put "ollama" or something for the api key and it should work.

@Jezo247, were you able to get it working?

Running the nightly build now, the app loads and runs well. We can close this issue.

@Jezo247 roger that. I will do some testing and see what is going on with it. But you may need to clear out all downloaded images as well. If it is cached locally it could cause an issue by using an old version.

FYI I did a new gitclone having deleted the previous directory and deleted all containers and images from Docker. I did one build using main, but rememebered you'd said to use night, so I deleted and redid a compose using the night image.
I even got an API key from openai and put it in the .env and compose files and did a new compose (having deleted the images and containers). I tried a summary of an already transcribed file. Same error. very odd as it shows the API key in the logs.

Interesting. Okay. I will review it today if i get a chance