[v1.13.1] Release Date Request

[AlperRehaYAZGAN]

[v1.13.1] Release Date Request

[vi]

Why specifically a release is needed?
Maybe just point it to a commit you need?

[AlperRehaYAZGAN]

For our specific use case, we are using websocat in our development environment with pre-defined Dockerfiles. This setup ensures user dev ide (like gitpod) and stream some OS information to our servers. Currently we solve it in staticly Dockerfile CMD and username:password from explicitly format (which new process could see password with "ps aux"). But it would be a great to just inject as ENV value and then new processes could not access websocat password by just typing "ps aux".

I requested this feature cause in Dockerfile we are writing multistage to build ENV supported version instead of "apk add websocat". But if you release with new version i will just reduce one stage and env value format that easy to manage. Its a presonal request actually 😅.

Yeah exact commit version clone and build from source code with Rust solves currently. Thanks for this amazing product.🔥

[AlperRehaYAZGAN]

I tried this and if anyone read this issue later. Maybe below code helps.

# stage 2 - build websocat
FROM rust:1.78.0-alpine3.19 as buildsocat

WORKDIR /tmp

# websocat build from source:
# Issue: https://github.com/vi/websocat/issues/240
# Resolved: https://github.com/vi/websocat/tree/e289e9f039169e2bc9df3c0b1aaf15a59f948aac
RUN apk add --no-cache git openssl libressl-dev

RUN git clone https://github.com/vi/websocat.git \
    && cd websocat \
    && git checkout e289e9f039169e2bc9df3c0b1aaf15a59f948aac

WORKDIR /tmp/websocat

RUN cargo build --release --features=ssl

# Stage 3 or later you can copy executable like below.
COPY --from=buildsocat /tmp/websocat/target/release/websocat /usr/bin/websocat