Denis Pisarev

I'm in favour of that, I will free us from having `openssl` as a dependency in many places. But we already wait for so long, definitely not a prio right...

Thanks for answering! That error with `

Hey, 1. As it was discussed on the Barcamp, it's worth integrating `substrate-developer-hub` into our Playground. 2. AFAIU since you are playing around with `substrate`, you definitely could make use...

To test, change the [image tag](https://github.com/substrate-developer-hub/recipes/pull/375/files#diff-b660780ad3d9fe112b50ac579ea27d55R18) to `:production`

Вот я с телефона добавляю скриншоты для наглядности:  

The pipeline design indeed seems not optimal, however https://hub.docker.com/u/paritytechno (cc https://github.com/substrate-developer-hub/substrate-docs/issues/415) is not a repository we call "official". We (CI and Infra teams) control the [following registries](https://github.com/paritytech/ci_cd/wiki/HowTo:-Create-an-image-and-push-it-to-docker-hub-in-a-pipeline#intro). Please take a...

Please see details in #1051, we don't have creds from this dockerhub registry.

there was an old plan to publish some stuff there, AFAIRC because of the documentation. But if we're ready to publish something to crates.io, usually the doc goes straight there...

I suggest let's rewrite https://github.com/substrate-developer-hub/substrate-docs/issues/182 into a better plan.

> rustdocs deployment design for substrate, polkadot, and cumulus I think we should target all our rust projects