LDAP is in roadmap! Although no ETA Also most feature requests are done by GitHub issue tickets not discord otherwise it's hard to track over time

@jan-reinhardt that's all I can think of. But maybe you can ask about the dangers of a public instance at https://github.com/Frooodle/Stirling-PDF/discussions

@DrewHasQuestions The new package now uses Stirling's built-in auth

Posted an issue for this in upstream repo. https://github.com/Frooodle/Stirling-PDF/issues/461

Latest package version should fix this.

This can probably be closed since Text conversion has been removed from Stirling-PDF for now due to bug in LibreOffice Only RTF remains

Thanks! It's working correctly now.

This is fixed with latest package.

@froodle said in Stirling PDF on Cloudron: @Neiluj reached out to them "We don't accept projects hosted under personal profiles. Our mission is to support groups rather than individuals. Have you considered moving it to a separate GitHub org? This helps to signal that this project is a collaboration instead of a personal undertaking." I'll have to think about how best to do this and pros and cons I'd guess that is just the policy of their default Open Source Collective fiscal host https://opencollective.com/opensource Note there are many other fiscal hosts on Open Collective who likely have less arduous policies (saying that, I'd guess it probably does make sense for you to be hosted by the Open Source Collective)

@aflorea I guess you are trying to call the API straight from your website's frontend ? If so, yes, this will trigger a CORS error. We don't provide a way to adjust CORS headers. Usually apps have a way to adjust this but Stirling-PDF does not have a mechanism for this. A workaround is to make your frontend call your website's backend and the backend proxies the call to Stirling-PDF.

Thanks for the heads up. Update published.

@girish Great, thank you for the information.

Yes, sorry, I just added this in the recent package.

@girish working now, thank you very much