CrazyMax

@PowerCoder As explained [on this page](https://portapps.io/doc/reporting-issue/), "We are aware of and notified of new application updates. So there’s no need to create an issue to update an application.". Concerning Waterfox...

Hi @OrangeDrangon, I will take a look on your request. Thanks for your input ;)

@RoyiAvital Chrome and by definition all browsers based on its engine cannot be fully portable. See portapps/brave-portable#4 for more information. This PR brave/brave-core#795 could solve this on Chrome btw ;)

> I know it can be portable as PortableApps does it. No it's not. Try to move your Chrome portable to another computer and check your extensions.

When I say "check your extensions" it's because they will be removed on an other computer as well as passwords, cookies, etc... So portable behavior is lost. Check [this thread](https://github.com/portapps/brave-portable/issues/4)...

For signed release see #68. PGP could be an alternative

Hi @devsporadic, yes we could add it through the setup. I will move this issue to the core repository as it's a global behaviour.

According to their [EULA](https://www.sandboxie.com/EndUserLicenseAgreement), it's not allowed to redistribute their product.

@Erriez > ### Issue 1 The image will be already loaded to Docker for the default [`image-local` target](https://github.com/crazy-max/docker-samba/blob/cb8edcdb1b27e326ca5220da16257203f220b173/docker-bake.hcl#L21), no need to add the `--load` flag: ```shell $ docker buildx bake...

> My proposal is to create two separate `wsdd` and `avahi` containers which can be launched via `docker-compose.yml`, for example in my forked `dperson/samba`: https://github.com/Erriez/docker-samba/blob/master/docker-compose.yml Yes indeed, the idea is...