👍 Internally, there is already a way to set custom env vars (you can do this only in the CLI currently, cloudron env). So, we have to update the manifest and the UI to use those fields and set env vars.
For future reference, systemd was acting all strange. We got all sorts of errors.
# systemctl restart box
Failed to restart box.service: Connection timed out
See system logs and 'systemctl status box.service' for details.
# systemctl status box
Failed to get properties: Connection timed out
# systemctl status box
Failed to get properties: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
16/07/2021 17:58:24 :: [console] Error writing to collectd.localhost.df-sdc1.df_complex-used: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-used.wsp)
16/07/2021 17:58:24 :: [console] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 266, in <lambda>
inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext
File "/usr/lib/python3/dist-packages/carbon/writer.py", line 189, in writeForever
--- <exception caught here> ---
File "/usr/lib/python3/dist-packages/carbon/writer.py", line 165, in writeCachedDataPoints
File "/usr/lib/python3/dist-packages/carbon/database.py", line 124, in write
File "/usr/lib/python3/dist-packages/whisper.py", line 740, in update_many
return file_update_many(fh, points, now)
File "/usr/lib/python3/dist-packages/whisper.py", line 747, in file_update_many
header = __readHeader(fh)
File "/usr/lib/python3/dist-packages/whisper.py", line 294, in __readHeader
raise CorruptWhisperFile("Unable to read header", fh.name)
whisper.CorruptWhisperFile: Unable to read header (/var/lib/graphite/whisper/collectd/localhost/df-sdc1/df_complex-free.wsp)
The last line gives a hint that the graphite file is corrupt. So, I removed all the whisper files in /home/yellowtent/platformdata/graphite/whisper/collectd/localhost/df-sdc1 and graphs seems to work after that.
@atridad Maybe a good idea to check the health of the hard disk ? Also, since we hit the systemd issue on the same server.
@atrilahiji I definitely like this idea! I know I've had to delete an app the odd time that I'm not sure if I will need later or not. My workarounds so far are to change the URL of the app to something like "app-old" or to make sure I download the backup info file first before deleting the app. Your idea is much cleaner and would be an awesome addition! It will allow for extra redundancy if for example we delete an app so it can be replaced by a new app at the same URL and something goes wrong, we can quickly revert back in such a case.
Below is the "hardware requirements" section from their github page.
Dendrite in Monolith + SQLite works in a range of environments including iOS and in-browser via WASM.
For small homeserver installations joined on ~10s rooms on matrix.org with ~100s of users in those rooms, including some encrypted rooms:
Memory: uses around 100MB of RAM, with peaks at around 200MB.
Disk space: After a few months of usage, the database grew to around 2GB (in Monolith mode).
CPU: Brief spikes when processing events, typically idles at 1% CPU.
This means Dendrite should comfortably work on things like Raspberry Pis.
@thetomester13 Nothing special in mine. I have a little node server that serves the static content and a separate endpoint for healthchecks. Otherwise it is exactly the same as hosting with surfer, with the only advantage here being it would show up as a one-click install for Hoppscotch specifically vs surfer.
And yeah I only just deleted my Gmail account I'm not about to make another to use Firebase. 😛
The main benefits on having 1 server type + 1 image combination insted of 1 for everything is the support for easy backup, update and rollback, Webui can be simple to the end user because it have just the function that he needs.
You can offer back compatibility to Minecraft Beta with no afford, and maintain there java version updated.
Development if the automation is good, will be easy because when you push a change a server type all his version will be updated automatically and rebuild.
If you update the basic java image all the server type will be updated, and all the version will be updated too.
Never mind it seems their login form has a shorter text limit than LimeSurveys maximum character limit. For some reason they decided to have a character limit on the form and not the password requirements. 10/10 good software 😄👌
Right.. It seems there are many candidates zabbix, netdata, some SNMP thing I forget etc. I prefer simply making sure Cloudron "works" with these existing software. It's why we added a way to open up the firewall as well. Happy to make any more fixes required to make these things work more easily.
Just an FYI - I recently found (thanks to @girish for setting the wheels in motion for me to dig into this) that there is some form of whitelisting/allowlisting in SpamAssassin via Cloudron's UI. It's not perfectly matching what we are looking for in this feature request, but should help buy some time for those who need this capability right away. Here's the goods on it:
The pros: you can use this right away!
The cons: It's not a true "whitelist" since spam processing still proceeds (a true whitelist/allowlist in my mind means it completely skips spam processing completely), but setting the score to be incredibly low should effectively force all messages that may have otherwise been "spam" into the inbox for the user (and onwards for mailing lists too), it basically achieves the same result as we're wanting for the most part. I don't think it can be done by IP, but will work for domain. The values also accept wildcard characters to help "whitelist" an entire domain.
From the other post I made (pasting it here for convenience):
I can confirm through testing that if I add a section to the SpamAssassin rules such as the following, this works! 🙂 So this is a great workaround to not having direct whitelisting capabilities, using the whitelist_to rule and score.
# whitelisting addresses
score USER_IN_WHITELIST_TO -100
Using the above (but of course substituting the actual email addresses) worked in my testing.
Similarly, the whitelist_from will work too on the opposite end of the equation... that will apply to who sent the message rather than who the message was directed to.