Looks like the patch that @jk referred to has been merged into Wallabag for 2.4, it would be nice to have this patched in the Cloudron version.
I've submitted a Merge Request for the wallabag-app here: https://git.cloudron.io/cloudron/wallabag-app/merge_requests/1
Is it possible to get this merged so that we can upgrade Cloudron?
In an effort to build better monitoring, it would be good to look at supporting existing tooling as well. For example, a Prometheus exporter would allow users to take advantage of the robust feature set offered by Prometheus and Grafana. Or, if Cloudron already stores persisted metrics in a graphite database or something, a way to connect to that from an external server running a monitoring suite would suffice.
Restic would be really great.
For my non-Cloudron services, I use this Docker image: https://github.com/ViViDboarder/docker-restic-cron.
It wouldn't make sense to take that as is, but it could be a good example of basic Restic functionality for something like Cloudron.
Hello. Since October 31st, my feeds have not been refreshing automatically. When I go into a terminal and execute the refresh command, it seems to work just fine, so it doesn't appear to be an issue with TT-RSS itself.
When I look at the container logs I don't see any logs from the refresh task at all, so it's as if it's not been scheduled.
Any ideas on fixing this? How can I view the logs for the cron jobs to debug further? How are these generally scheduled?
@girish for what I’m trying to do, it’s best to be a provider.
There are some applications that just aren’t suitable to host on my Cloudron due to memory limitations. I’d like to not manage my credentials separately. Public facing LDAP would be more convenient, but higher risk. A public OAuth provider would be enough for me to use for proxy auth from my other server.
Cloudron used to support acting as an OAuth provider for external applications, and it’s referenced in the documentation, however I can no longer find the setting. Is that still available?