apart from the missing turn server configuration talk already works in Cloudron. So your app request probably should be for a dedicated turn server app.
even with 1 GB of memory assigned, I get a "ran out of memory" quite often
currently the app is quite unresponsive as it's searching for favicons (as I can see from the logs)
Importing from Enpass 6 (json) worked fine for me
This probably depends quite a bit on the amount of data you throw at it. I actually started with an empty vault since password history etc would not have carried over anyways. But in my case it's easy to keep a portable version of keepass around if I need a password from the old database.
Maybe the icon caching is causing some troubles for you? You could deactivate this from the settings. Probably also a good idea to get in touch with the upstream project if they are already aware on this and if there is anything to lighten the load a bit
how are updates done? Or will your app eventually become an "official" cloudron app?
My idea is to have a good base so that @nebulon can make this an official app.
@gml thanks. I have fixed the location of the config.json created by the admin panel. Settings can now be stored (but SMTP settings should probably be done in start.sh instead). I have also added your logo.
The password prompt is actually expected since ldap auth is used in the webserver. The only way around the prompt would be to use oauth instead, but in previous attempts (the cloud torrent app) I did not get this to run.
I've now spent a bit of time to get the admin page "properly" working. Registrations are now disabled in the app itself, but users that are in the cloudron admin group can login to /admin to create the required users.
Stuff like Websockets support (for folder notifications) is still missing, as well as automatic SMTP configuration but I would say the general app is "done".
Looking forward to feedback.
@gml yes, the ldap invite tool would be nice. I think the best for the moment would be to slap Apache Infront of bitwarden (would be needed anyways for the websocket part) and hide the admin panel behind ldap auth (only allow admin users from within cloudron). Then invites and open registration can be disabled and admins can manually create accounts as needed.
Hi @csilvav ,
the config.json of Mattermost is stored in /app/data and should therefore be writable to the admin (the file is created in https://git.cloudron.io/cloudron/mattermost-app/blob/master/start.sh#L7)
basic prototype now lives in https://git.cloudron.io/fbartels/bitwardenrs-app
cannot build it at the moment, though. since its stuck at
$ cloudron build Building email@example.com Build scheduled with id 9fcf31f1-04f9-445e-b687-79b2f7d54659 Waiting for build to begin, this may take a bit...
@girish is the backend maybe hanging?
edit: by now the build has finished
Docker has recently been updated on the cloudron buildserver, which means multi stage builds and
COPY --from now works within Dockerfiles.
I have a longer train ride on friday, maybe I can now make something happen with Bitwarden_rs.
With the above dockerfile cloudron build now succeeds.
I have a longer train ride on friday, maybe I can make something happen with bitwarden during it.