Cloudron Forum

About Claper:

Claper turns your presentations into an interactive, engaging and exciting experience.

Claper has a two-sided mission:

• The first one is to help these people presenting an idea or a message by giving them the opportunity to make their presentation unique and to have real-time feedback from their audience.
• The second one is to help each participant to take their place, to be an actor in the presentation, in the meeting and to feel important and useful.

---

Additional links:

Website: https://claper.co/
source: https://github.com/ClaperCo/Claper
docs: https://docs.claper.co/
License: Distributed under the GPLv3 License

About ClassQuiz:

ClassQuiz is a quiz-application like KAHOOT!, but open-source which is very important if it is a product for educational purposes. You can create quizzes and play them remotely with other people. It is mainly made for teachers, who create a quiz, so students can compete with their knowledge against each other.

---

Additional links:

Website: https://classquiz.de/
source: https://github.com/mawoka-myblock/ClassQuiz
docs: https://classquiz.de/docs
self-hosting: https://classquiz.de/docs/self-host
License: This repository is licensed under the Mozilla Public License 2.0

After having quickly searched for something similar, I don't think the below as been proposed yet.
Apologies if it has.

The idea:

• being able to leave quick (internal) notes / information / instruction for a given app.

This is specially useful if the app in managed by multiple admins/operators, to keep track of some changes or remind of a given set of parameters/circumstances etc...

Mostly useful also to offer the possibility to give the end user more information about the app: what is the app about, remind the user how to log in (which login to use) etc....

Here is how I imagine this could work:

For Admins:
For an admin, you access the notes via the cog wheel of the app via the dashboard

Then you access them via the new "Notes" section as per below:

Where you can create / leaves notes for other admins or operators or users.

/// /// ///

For Operators:
Identical to admins, you access the notes via the cog wheel

Then you access them via the new "Notes" section as per below:

/// /// ///

For Users:
You access the notes via the "notes" icon of the app via the dashboard

The user is then presented with the "notes" view - Similar to a settings view for admin, but presenting notes in read only format.

The added bonus would be to be able to keep track/version of the various notes and notes modification thanks to a basic version history (being able to revert / look at previous notes)

Nothing revolutionary but I believe this could add value for the actors of a Cloudron instance.
Of course this could take many other forms, but hopefully the general idea makes sense.

@girish said in Outline stopped working after upgrade to 1.2:

@eddowding @uwcrbc Can you add export FILE_STORAGE_LOCAL_ROOT_DIR=/app/data/storage to /app/data/env.sh?

Tried this. Stopped and started the app. It initially said not responding straight after the start (presumable running some migration - have not check the log further). but within couple of minutes, the app worked again - Status is running.
Seems like this did the trick. Thanks @girish. Is it something we overlooked?

@girish said in Outline stopped working after upgrade to 1.2:

@eddowding @uwcrbc Did you guys add export FILE_STORAGE=local manually in /app/data/env.sh by any chance?

Yes I did add the env. variable manually a while ago.

I have seen few posts here and there getting close to the request/idea below (sorting apps and such), but I have not found one with identical purpose.
Apologies in advance if this ends up being a duplicate.

This is, as far as I can tell, a pure UX request:

I regularly find the need to get "my apps" categorized (sub-categorize), for myself or my users. Here as an example:

it could be done with the introduction of an admin defined single "category" (for example below the tag field for each app):

Or alternatively, admin could set single tags to be "displayed as dashboard category" or something along these lines.

Should a given user not have access to any app for a given category / tag, then the dashboard category would simply not show

I guess that this also suppose a way to manage categories (creation / deletion) or tags, outside of each app, as a general setting as well as a default category for each app.

Hopefully this makes sense.

This is possibly a feature request, or simply me being oblivious. If the former, please feel free to move my post.

Please see screenshot below:

For some users/in some instance, the name "Cloudron" is not familiar and create more confusion than help.
While this is a minor cosmetic change, I wonder if this is alterable somewhere. I have looked in the "Branding" section, but nothing relevant pops up.
So maybe I am not looking in the right place?

I am not talking about changing the categorization made by Cloudron (login with credential, login with dedicated account, login with email), but simply provide more information / avoid end user's confusion.

Ideally, we'd be looking at the possibility to customize this string, to be able to mention the name of the company/related entity, and precise if user should use their username or email (depending on the app itself) to log in.
something like: "Log in with MyCompanyX username" or "Log in with MyInstitutionY's email address

Where "MyCompanyX" would be taken from somewhere on the Branding page, or the Cloudron application settings itself

Does it make sense?

Maybe someone also has a better idea about how to go about this?

Many thanks

For the record, I had the exact same issue this morning on a new cloudron install attempt with a SSDNode VPS running a fresh Ubuntu 22.

The change offered by @benborges worked effectively and allowed me to complete the cloudron installation.

While 2 different hosts having the same issue might still be coincidental, I think it is worth mentioning since the probability of it being a network glitch are consequently going down.

Hopefully this makes sense - I am not planing on re-deploying things just yet and so would not be in a position to test for re-occurence. With this in mind, I am happy to help in any ways you see relevant.

Is the OIDC integration (and the necessary time to integrate it) the only "blocking" factor here or is there any other element of the package/source preventing a release in Cloudron?
This app would be a great addition indeed.

Thanks @girish - i though indeed that OIDC will alleviate, at least partly this situation. Yet, on the other hand, not all apps will support/are supporting OIDC.

Many thanks for looking into this.

Just to confirm that this is not an isolated case, since the same happened to some (not all) of my box.
Solution was indeed to remount the backup storage manually.

Should this help, I have had it happen with v8 and v8.0.2 so far, on multiple servers, but only with Hetzner storage box.

@timconsidine Ah! I am in the exact same situation.
I run both on webcatalog and privacy locked browser. and in both situation Cloudron does not/cannot pick up the system preferences thus does not turn on the dark mode.

I suppose having an explicit toggle for "light mode, dark mode, use system preference" on the user profile would not hurt anyone, but I also agree, unless a quick feature to implement, there are bigger fishes to fry...

Apologies for the revival if irrelevant.
I am just wondering if this is still on the map and if so, if there is any hint of time until release?

Many thanks,

@jdaviescoates Indeed I am too, already using the groups to set visibility access to given set of apps for given users.

However, this only impact the "visibility" of an app on the dashboard, as far as I know. Not the segmentation of already visible/accessible apps.

The above feature request would have noting to do with access right to an app and everything to do with dashboard customization.

So this is not quite the same as what we are trying to do. That is to say, bring more readability/meaning on the dashboard app organization for all users (less tech savvy ones) - A way of grouping apps together according to one's own need/meaning.

Unless I am misunderstanding you, in which case apologies in advance!

Hi all,

It seems as Cloudron v8.1 is being pre-release with the following release notes:

Because this list seems to differ somewhat from the "What's coming in 8.1" forum post, I wanted to take a closer look to the release notes and note the differences, see what made the cut off and what has not.
However I seem to struggle to locate release notes for it.
Are these publicly available (I mean other then the popup when triggering the release)? If so, where to find them?

Furthermore, in the process of looking for these release notes, and while I know Cloudron is "source available", I could not find the actual source anywhere.
The following page makes mention of Cloudron Gitlab instance where one can find the app package sources, but I wasn't able to find the "Cloudron code" as mentioned here:

Am I looking in the right place ?

Any help is much appreciated.

In all case, many thanks for this further release.

@nebulon Sure - let's say for example that you have different apps for different department/teams in your company and a user can be part of multiple teams/departments.

So for example:
One group/category of apps is common to all users.
One group/category of apps cater to teachers only
One group/category of apps cater to students and teachers.

A applicable scenario in our organization would be for example:
One group/category of apps (NodeBB; WikiJS etc..) common to all users
One group/category of apps (Invoice Ninja, Kimai etc..) for users in the Accounting department
One group/category of apps (tools such as Vaultwarden, Cal.com, LanguageTool etc..) for users with specific related needs.

Does this make sense?
It is simply an arbitrary personalisation, not at the individual level, but at the company/provider level.

Let me know if it doesn't or does not seem intelligible.

Many thanks,

@girish said in Cloudron Source & Release Notes:

@uwcrbc the repos have moved a bit in last few weeks. We are moving all the app packages into the CI for automated and reproducible builds. I will make a separate post later this week explaining what we have done (it's mostly only technical and probably interesting to a fellow developers but not for cloudron users themselves). In the past, we were quite careless with how people registered and were given permissions. But anyway, to answer your question until that post pops up: we have made a few groups.

Cloudron code base - https://git.cloudron.io/platform
App packages - https://git.cloudron.io/cloudron
For doc repos - https://git.cloudron.io/docs
Unpublished apps, tools, testing stuff etc - https://git.cloudron.io/playground

The repos will most likely not get re-orged further but I will put the final org in my post.

@girish Great - This makes sense. Indeed I got the feeling that a few things were changing recently (Website, pricing tiers, repo - for the better I find!). It is like Cloudron is gearing up for the next stage and it feels good to see.

Possibly I think it would also make sense to update the open source website page to reflect these repo changes.

@nebulon Excellent - This looks great!

I think for us, the notes for users would also be most relevant.
To cater to a diverse range of users with various skills and IT literacy levels, one cannot provide enough easily accessible info and so having a place where one can keep a short reminder of what a given app is all about and how to access it more in details would be very valuable.

I'd like to revive this a bit if possible.

Without pushing this to a full blown white-label solution (this thread is probably more suited for this), there is still this small gap open for enterprises trying to deploy this to users who have no clue about what Cloudron is, and ultimately should not be concerned with this.

so I will limit the scope of my suggestion below to the end-user aka simple "user" in Cloudron (leaving aside all admin related branding).

To this extent I would like to propose the notion of "Brand name" with sole purpose to act as brand placeholder such as this:

This "Brand name" can be used in multiple places, starting with the few mentioned above such as:
+User profile:

+User Dashboard App Tile:

+App Login Page:

You get the idea - It is probably applicable in a few other places.

I see the above as a pragmatic step that I imagine fairly simple to implement (placeholder/env variable), as opposed to things like DKIM (as relevant/important as it is) would possibly require a more complex implementation.

It would be great if this could be of consideration.

@girish This is very nice of you. Here are some packages that we would love to test:

• Rallly
• Sterling PDF
• Vikunja
  To start with...

Many thanks,

Hi @JLX89,

This is something that has been discussed / requested a few times already.
Please see here:
https://forum.cloudron.io/post/91579
https://forum.cloudron.io/post/93245

and here for the latest:
https://forum.cloudron.io/post/96688

In short, my understanding is that it is coming in 8.2. Or could it be sooner @girish ? This seems in relative high demand.
If I get this right the Cloudron part is done, it just needs the related app package to be updated to make use of the Cloudron env variable.