Could be useful, don't think we have already an app for this.
https://www.signserver.org/
https://hub.docker.com/r/primekey/signserver-ce
Best posts made by avatar1024
-
SignServer - online document signing
-
Per domain user subscription and admin role
I'm sure something similar has been asked already but I couldn't find it on the forum.
Would it be possible to add to following features of User & Groups in future version of Cloudron:
-
subscribe users to a specific domain (say with another drop down option for each users: default being "all" but with the possibility to select domains individually - as it is down for selecting group membership). Those users would then only be allowed to login on apps which are installed under that/those particular domain(s). Effectively this is no different that manually creating a group for each domain and then manually setting the correct access permission when installing apps, except that it would automate that process by creating those groups in the background for each domain and setting the correct rights automatically. Also it would be helpful for implementing the "3. per domain user management" aspect of the "domain admin" feature below
-
create a "domain admin" role to give some members admin rights but only on certain domains so that they can (and only can): 1. access all apps and email settings on a given domain(s); 2. an managed all of apps on that/those domain(s) 3. can see all users subscribed to that/those domain(s) and can invite new users to that/those domain(s). So as role we'd have: Owner, Admin (would automatically be administrates all domains), Domain Admin (which when selected would open the drop down menu to select domains without the "All" option), Users (which when selected would open the drop down menu to select domains, with default choice on the "All" option).
It feels these two features would greatly enhance cloudron management for cases where you don't necessarily want to have admins able to administrate all domains (either for security reasons and for reducing admin time) but still want someone able to configure email accounts / lists, manage apps and invite people.
Here is just some concepts and some ideas on how it could work on the UI side. Hope this proves useful.
-
-
Mailman
Hello,
Is it possible to integrate mailman to cloudron to be able to manage email lists?
It would be a great feature to have.
-
RE: What's coming in 7.0 (was 6.4)
@nebulon Apologies, I meant that on mouse hover an app, there is now a grey square button (with white gear) always visible, which then turns white (with blue gear) when actually hovering over it. Before it used to be that you see only the gear (without a square) when hovering over an app and you'd see the square when hovering over the gear.
Haha I've realised this is only a dark theme issue. I've just tried in another browser with a light theme and the issue is not here. So yes, probably a slight regression on the dark theme.
Cloudron 7
Cloudron 6
-
RE: Per domain user subscription and admin role
@girish Yes you are right that the post started with different domains but this is because I had in mind the case of an organisation that uses separate domains for different activities, with different people being in charge of those different activities. While you are right that Cloudron does a fantastic job as isolating access to apps with the Group feature, as soon as if you give Admin right to someone, then they get full access to everything irrespectively of group / user access rules (which is of course kinda of the point of an admin!).
The issue is that in the case I mentioned, it would still be useful to give some people the ability to at least managed emails, users and apps for their particular domain / area of the organisation.
While this may not be a "common" case, I reckon it is not super rare either.That said, the thread though as kinda of evolved into looking at ways to fine tune the rights of the Admin role rights rather than a split per domain as it started original. Lots of ideas in there. Maybe another intermediate Admin role could be step in that direction to delegate some rights (like email management) to people which would be useful in large organisations (see my second post) without granting full admin rights ?
-
RE: Kopano, Jitsi, BigBlueButton - why Kopano?
@scooke I too would very much like to use Kopano Meet with external users (without them to login into my Cloudron), so like you I think it would be a great feature to have but still, I think we should be grateful on the fact some developer bothered making a Cloudron package even if there are limitations for now and not be too harsh or focused on criticisms and enjoy that we got a videoconference app running on Cloudron. And maybe kindly ask for support if you're trying to do something which you cannot do on your own (I believe the Kopano Meet Cloudron app has an open source code which you could be modify to add the functions you want, if you know how to do it).
As @fbartels explained, Kopano does have this functionality, it "just" needs to be configured. Now the "just" doesn't seem very straightforward and yes it'd be great if someone could package the app with that function turned on. Maybe @fbartels can help? Personally I'm not a developer so I can't help with this but appreciate any work anyone can put into this or into anything else that makes Cloudron better.
-
RE: Subsonic/Libresonic/Airsonic - a music streaming server
Is there any update on this app? It would be awesome to have it!
-
RE: What's coming in Cloudron 7.1
@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).
-
Sympa - mailing list
Would be great to manage mailing on cloudron.
There is a topic on mailman so here is another one for Sympa which looks like a pretty good option too.
-
RE: What's coming in 7.3
Is there a plan for more backup backends like restic / borg for 7.3?
I recall it being listed for 7.2 at some point but looks like it got dropped off the list due to the need for a speedy release.
Latest posts made by avatar1024
-
RE: Disabling the dashboard
@girish disabling the dashboard is entirely fine. You can even do it through the Web UI apps settings. In fact I've disabled the dashboard on most of my NC instances ever since it was put as the default landing page as i don't find it particularly useful.
Thanks for the tip though. Useful to land to directly Files, while keeping the dashboard enabled.
-
RE: Nextcloud 24 has been released and seems to improve speed!
@necrevistonnezr Since the upgrade I find the overall experience in the WebUI snappier than before
-
RE: What's coming in 7.3
Is there a plan for more backup backends like restic / borg for 7.3?
I recall it being listed for 7.2 at some point but looks like it got dropped off the list due to the need for a speedy release.
-
RE: Mailing feature: add users and groups as members
@girish said in Mailing feature: add users and groups as members:
When added to a list, are you expecting the primary email of the user to be used ?
Indeed
-
Mailing list feature: basic moderation
Sorry for reviving one part of an old thread but since the whole thread was marked as solved but only one of the two features got implemented (it was my bad probably to request two features in one post
).
This feature request is about adding a basic moderation feature to Cloudron list without requiring require much code changes compared to the existing set-up.
So the idea is that for private list we could set one of the list member (an email address) as "the moderator" who would automatically receive emails coming from non-members of a private list (external senders) and who could then manually forward those emails (or not) to the list (since they are a member of the list).
I'm thinking about an implementation that looks like this:- If no moderator is set, then behaviour remains as is
- If a moderator is set, then the auto reply message receive by external senders explains that they've emailed a private list and their message will be moderated. The email gets forwarded to the moderator, who can then manually forward (or not) to the list. So it would effectively "only" require setting up an auto forward from external senders to a specific list member (the moderator) and that's it. I'm not a coder so the "only" may be mislead but it feels like all of this is already within the existing email capabilities of Cloudron which would need to be applied to the email list feature.
I know Cloudron email lists are just forwarding lists and not real email lists and I don't intend to ask for it to become a fully fledged email list but wondered if we could add this function in a quite simple way since it is a probably the on of the key feature missing for most common uses of mailing lists (even if not as fine tuned as actual mailing lists software). Especially as it seems there having been much progress or interest to add actual mailing list apps to Cloudron (mailman or sympa).
-
Mailing feature: add users and groups as members
Hello,
Was wondering if it'd be possible to add Cloudron users, and even more so groups as member of a mailing list instead of having to add their email addresses manually?
It's just that if you want to have an email list for a Cloudron group it would reduce steps and improve consistency to be able to add a group directly to a list so each time a new user gets added to a group it gets added to that list manually.
-
RE: High Performance Back-end for Nextcloud Files
systemctl status notify_push gives me:
notify_push.service - Push daemon for Nextcloud clients Loaded: loaded (/etc/systemd/system/notify_push.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-04-01 09:58:44 UTC; 14h ago Process: 180019 ExecStart=/home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/apps/notify_push/bin/x86_64/notify_push /home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/config/config.php (code=exited, status=1/FAILURE) Main PID: 180019 (code=exited, status=1/FAILURE) Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 0: Failed to connect to Nextcloud database Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 1: error communicating with the server: failed to lookup address information: Name does not resolve Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 2: failed to lookup address information: Name does not resolve Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Location: Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58 Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Backtrace omitted. Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
And journalctl -u notify_push
-- Logs begin at Mon 2022-03-28 21:45:49 UTC, end at Sat 2022-04-02 00:34:23 UTC. -- Apr 01 09:33:43 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients. Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Error: Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 0: Failed to parse config Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 1: Failed to parse nextcloud config Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: 2: Failed to read config file Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Location: Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: src/config/nc.rs:8 Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Backtrace omitted. Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:33:43 v2202201132182176931 notify_push[176600]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:33:43 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:33:43 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'. Apr 01 09:34:44 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients. Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Error: Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 0: Failed to parse config Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 1: Failed to parse nextcloud config Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: 2: Failed to read config file Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Location: Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: src/config/nc.rs:8 Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Backtrace omitted. Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:34:44 v2202201132182176931 notify_push[176680]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:34:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:34:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'. Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Location: Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: src/config/nc.rs:8 Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Backtrace omitted. Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:35:05 v2202201132182176931 notify_push[176786]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:35:05 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:35:05 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'. Apr 01 09:54:28 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients. Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Error: Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 0: Failed to connect to Nextcloud database Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 1: error communicating with the server: failed to lookup address information: Name does not resolve Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: 2: failed to lookup address information: Name does not resolve Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Location: Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58 Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Backtrace omitted. Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:54:28 v2202201132182176931 notify_push[179480]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:54:28 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:54:28 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'. Apr 01 09:58:44 v2202201132182176931 systemd[1]: Started Push daemon for Nextcloud clients. Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Error: Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 0: Failed to connect to Nextcloud database Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 1: error communicating with the server: failed to lookup address information: Name does not resolve Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: 2: failed to lookup address information: Name does not resolve Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Location: Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58 Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Backtrace omitted. Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=1 environment variable to display it. Apr 01 09:58:44 v2202201132182176931 notify_push[180019]: Run with RUST_BACKTRACE=full to include source snippets. Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE Apr 01 09:58:44 v2202201132182176931 systemd[1]: notify_push.service: Failed with result 'exit-code'.
-
RE: High Performance Back-end for Nextcloud Files
@jdaviescoates I have now tried to just follow the basic instruction instruction on the notify push github.
What I have done:
- Installed the app inside NC
- run occ notify_push:setup inside the app terminal
- The abovce generated a systemd service like
[Unit] Description = Push daemon for Nextcloud clients [Service] Environment=PORT=7867 Environment=NEXTCLOUD_URL=https://files.xxxxx.net/ ExecStart=/app/data/apps/notify_push/bin/x86_64/notify_push /app/code/config/config.php User=www-data [Install] WantedBy = multi-user.target
I have replaced the path to the actual path to the binary and the config file like so
[Unit] Description = Push daemon for Nextcloud clients [Service] Environment=PORT=7867 Environment=NEXTCLOUD_URL=https://files.xxxxx.net/ ExecStart=/home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/apps/notify_push/bin/x86_64/notify_push /home/yellowtent/appsdata/1445e2c5-fa60-4ce9-894e-3e2a8b8dd0a0/data/config/config.php User=www-data [Install] WantedBy = multi-user.target
ran sudo systemctl enable --now notify_push as indicated.
But then it says the binary is not running.... so for now it's a fail. Anyone got any idea?
-
RE: Jitsi - High CPU Usage in client's PC
Do you have dedicated GPU? Otherwise high cpu usage is pretty normal, since the client is decoding video streams.
-
RE: What's coming in Cloudron 8.0
@girish true that it's pretty hard for this post to keep up with your coding speed
Maybe we should start a new clean one and you can let us know what you think on some of the newer ideas that were proposed (e.g. this one on my side)
Well done for you amazing work! (and the friendly support I have to say!)