tgxn @tgxn commented 4 months ago
It appears this uses MSSQL and .NET for deployment which can be rather resource-intensive within cloudron. (I don't believe any other apps are using this approach to store data)
.NET Core 2.x SDK
SQL Server 2016 or 2017 (2017 for cross-platform)
(from https://github.com/bitwarden/core)

Owner Some people on a HN thread mentioned that despite being .net, it runs on linux and mysql.

the Dockerfile in the git repo of bitwarden_rs makes use of multi stage building. is that already supported in cloudron build? If so then is should be trivial to adapt the last stage of the build process.

Edit: to answer myself. Cloudron currently does not seem to support multi stage docker builds.

I made a few tests today since I remembered that there is a dockerImage value in CloudronManifest.json, but I am not quite sure how to use it.

My current experiment is at https://github.com/fbartels/bitwarden_rs/tree/cloudron/cloudron. It uses a new Dockerfile that uses the multi stage Dockerfile as a base and uses a Cloudron Base Image for the last stage. But it seems he does not take my dockerImage. The only way he pulls in my image is by calling cloudron install --image fbartels/bitwarden-cloudron from the commandline.

For everyone else reading this. This is up until now only a build, the app is still missing all integration pieces and won't work withing Cloudron (yet).

I would say even the recently introduced admin panel is already a good step. This could be secured via http basic auth and only allowed for admins in Cloudron. The last point in the ldap sync topic was afair that this will be implemented as a standalone tool (which then will give the challenge on how to integrate both parts in the same image).

@fbartels The tool will likely be written as a static binary which can be downloaded and installed within the same container. Then it can be executed by Cloudron using the scheduler. Roughly the same way other periodic tasks are executed.