Closed jippi closed 2 months ago
That's because the latest
image tag doesn't include the streaming support yet (asciinema.org runs off of a branch based on develop
which has it).
I've now merged this new stuff into main
(stable) branch and tagged as v20240427. Github workflow which builds docker images for new releases seems to be failing/timing out, so need to figure this out before the new image will be available.
Meanwhile, if you want, you can build the image yourself by checking out the main
branch and running docker build -t ghcr.io/asciinema/asciinema-server:latest .
Hi @ku1ik
Thanks for the quick (!) response ❤️
In between posting and just now, I ended up doing pretty much what you suggested, I cloned main
into a sub-folder to my docker-compose project changed my file to the follow - and then it worked 🎉
app:
image: asciinema:local
build:
context: src/
restart: unless-stopped
env_file: env.production
environment:
UPSTREAM_NAME: asciinema
VIRTUAL_PORT: 4000
volumes:
- ./data/uploads:/opt/app/uploads
links:
- db
- redis
ports:
- 4002:4002
Re your CI pipeline issue, it exits with exit code: 137
which is usually "out of memory" issue 😱
You might need to pick up something along the lines of this https://github.com/rust-lang/cargo/issues/10781#issuecomment-1163819998 :)
@ku1ik this should fix your build issue https://github.com/asciinema/asciinema-server/pull/439
ghcr.io/asciinema/asciinema-server:latest
has been successfully pushed. Enjoy, and thanks again!
Describe the bug I'm trying to setup and test the new streaming features in the v3 CLI, however, when running the Docker image
ghcr.io/asciinema/asciinema-server:latest
I do not see the "Stream" option in the UI and running v3 cli yieldsLooking in the logs, it seems the endpoint being hit returns 404.
Is there a flag/setting that need to happen for it to be enabled? I tried poking around in the code, and couldn't find anything conditional that seem to trigger streaming on/off - maybe I'm missing something?
Docker-Compose file:
Versions: