Alex Yao

[Take a look here](https://github.com/alexyao2015/BitBetter). This is setup to automatically update Bitwarden images upon release and has the ability to automatically regenerate certificates if necessary.

And... Done!

The nice thing about this is there is no need to rebuild the image for certificate replacements. It automatically replaces the certificate at runtime. Either way, there are two different...

That's correct.

There's no real work to be done anymore. There is nothing manual to do since it is all done automatically now. [See here ](https://github.com/alexyao2015/BitBetter#using-public-images) [and here](https://github.com/alexyao2015/BitBetter/actions)

Yep! It will automatically generate and store new certificates in the bwdata folder if you use the custom image. If you are already using BitBetter, you can copy over your...

It should be in .keys. The organization itself will not be invalidated. Just the licenses for it. Really not a big deal to start over with new keys. Just need...

There could simply be 3 text boxes, one for each decompiler, or 1 text box that is just appended to the chosen decompiler.

@fichtner Do you have an update on possible solutions for this? I see you've added a support label, but I don't believe this is support. Its a feature request.

https://github.com/play-with-docker/play-with-docker/issues/434#issuecomment-709639676