[05:50:18]
<lapineige> > You may be interested in editorconfig. In the example package, it is configured to make you insert the right style of newlines:
> https://github.com/YunoHost/example_ynh/blob/88e9fc2b194ccac48b76b4df990339298227c587/.editorconfig#L8
>
> It is widely integrated natively (Neo/vim, Emacs, IntelliJ, ...), though you need a plugin for some editors like VSCode:
> https://editorconfig.org/#editor-plugins
I was a simple mistake where I edited a windows file first and forgot to change the setting then 😅
[07:50:21]
<rimu (piefed.social)> Hi folks, I'm the lead developer of PieFed.
I have added LDAP support to PieFed but I do not know how to get the host, port, etc so that PieFed can connect to the Yunohost LDAP server. Is there a convention for environment variables hold this data? Any links to documentation would be great :)
[07:56:51]
<tituspijean[m]> Welcome, and thank you for developing PieFed :)
I'd say that's up to the YunoHost packager to set up these variables, and we adapt to whatever you chose to store them (config file, env file).
[07:57:21]
<rimu (piefed.social)> ok, easy :)
[07:59:40]
<tituspijean[m]> for example, here is what we have for nextcloud: https://github.com/YunoHost-Apps/nextcloud_ynh/blob/7604803e5f13bd1c2b38f1d81bd2043ff06e2cfd/conf/config.json#L40
[08:01:52]
<tituspijean[m]> ...which, from what I see in your implementation, is a bit too advanced, since it uses groups to filter access 😅
[08:02:26]
<tituspijean[m]> (that's not a requirement, our SSO is here to block access if a user does not have permission)
[08:08:07]
<rimu (piefed.social)> how does the contents of config.json get passed to nextcloud?
[08:11:25]
<tituspijean[m]> In the case of Nextcloud in YunoHost, that file is pushed in Nextcloud's directory upon installation or upgrades handled by YunoHost.
In your case, I guess we could have an `.env` file handled the same way, and referred to in the service that launches PieFed.
[08:12:26]
<mrflos> rimu (piefed.social): you can find the basic informations of yunohost's ldap here : https://doc.yunohost.org/packaging/advanced/sso_ldap_integration#ldap-integration
[08:12:48]
<rimu (piefed.social)> Yes, I read that one :)
[08:13:16]
<rimu (piefed.social)> Sounds good. I will need to buy more RAM so I can run VMs and then do some experiments :)
[08:13:35]
<rimu (piefed.social)> next week.
[08:13:50]
<rimu (piefed.social)> Thanks!
[08:22:03]
<tituspijean[m]> From what I gather in your issue tracker and here, are you willing to do the packaging of PieFed for YunoHost from scratch? If so, we can definitely support you. If not, no problem, I'm sure some packagers (myself included) can contribute.
[08:23:10]
<rimu (piefed.social)> I'm sure it would go 10 times faster if you guys could do it. I have too many things to do already!
[08:24:37]
<tituspijean[m]> That's what I was wondering. 😅 Let's do it the other way around: if that's fine for you, can we ping you here or on your issue tracker if we encounter any issue during the packaging?
[08:25:09]
<rimu (piefed.social)> For sure. I will update the INSTALL.md about the new LDAP environment variables, now.
[08:32:05]
<tituspijean[m]> Actually I'll start the packaging now 😇
[08:32:18]
<rimu (piefed.social)> exciting!
[08:50:18]
<tituspijean[m]> Is there a particular reason not to use the same Redis DB for the cache and the celery broker? (I am no Redis expert, I only see that our Redis helper only returns an other DB that 0 when it's "full")
[08:53:33]
<rimu (piefed.social)> Probably they could use the same one.
[08:53:41]
<rimu (piefed.social)> Try it :)
[08:54:32]
<rimu (piefed.social)> I have never had to do this but I want the option of deleting everything in the cache Redis DB without deleting everything in the celery redis DB.
[08:55:14]
<rimu (piefed.social)> In practice I have found that is is the celery one that gets too big when bad things happen, not the cache one. Losing the cache is no problem....
[08:59:31]
<miro5001> > <@tituspijean:matrix.org> Is there a particular reason not to use the same Redis DB for the cache and the celery broker? (I am no Redis expert, I only see that our Redis helper only returns an other DB that 0 when it's "full")
I've faced this situation while packaging indico. I don't remember the details, but it's recommended not to use the same db for redis cache and celery because it may lead to conflicts. I ended up creating a small function to lock the first redis_db to get a new one when asking for the second during install, upgrade
[09:08:42]
<tituspijean[m]> OK thanks! I'll keep an eye on it and check your function if needed
[09:34:42]
<Yunohost Git/Infra notifications> tituspijean created repository piefed_ynh: Federated forum and link aggregator, packaged for YunoHost https://github.com/YunoHost-Apps/piefed_ynh
[09:53:38]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 1 commit to testing: Update manifest.toml ([347990f5](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/347990f57b4b646c90cbefe0effe02587732c860))
[09:53:47]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar opened [pull request #824](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/824): Testing
[09:54:16]
<Yunohost Git/Infra notifications> [nextcloud_ynh/testing] Testing (#823) * Update ADMIN.md: update advice to open shell + add a note on how to promote a user to admin * Update ... - eric_G
[09:54:16]
<Yunohost Git/Infra notifications> [nextcloud_ynh/testing] Merge branch master into testing - eric_G
[09:54:16]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 2 commits to testing ([347990f57b4b...d2f2ca902bd6](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/347990f57b4b...d2f2ca902bd6))
[09:55:24]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 1 commit to v30: Update manifest.toml ([869c817b](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/869c817b03fea7aec8e70f4caa6e420e5a259746))
[09:55:42]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 1 commit to testing: Update manifest.toml ([d5f9917f](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/d5f9917f1dae7168983a03c54aeceb1d061a9051))
[09:56:16]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 5 commits to postgresql_reboot ([12505efc7449...9900bce6b2f5](https://github.com/YunoHost-Apps/nextcloud_ynh/compare/12505efc7449...9900bce6b2f5))
[09:56:17]
<Yunohost Git/Infra notifications> [nextcloud_ynh/postgresql_reboot] Merge branch master into testing - eric_G
[09:56:19]
<Yunohost Git/Infra notifications> [nextcloud_ynh/postgresql_reboot] Update manifest.toml - eric_G
[09:56:19]
<Yunohost Git/Infra notifications> [nextcloud_ynh/postgresql_reboot] Merge branch testing into postgresql_reboot - eric_G
[10:45:24]
<Yunohost Git/Infra notifications> [appgenerator] tituspijean opened [issue #19](https://github.com/YunoHost/appgenerator/issues/19): A few encountered bugs
[10:47:54]
<Yunohost Git/Infra notifications> [appgenerator] tituspijean edited [issue #19](https://github.com/YunoHost/appgenerator/issues/19): A few encountered bugs
[10:49:47]
<Yunohost Git/Infra notifications> tituspijean edited repository piefed_ynh: Federated forum and link aggregator, packaged for YunoHost https://github.com/YunoHost-Apps/piefed_ynh
[10:53:39]
<Yunohost Git/Infra notifications> tituspijean edited repository piefed_ynh: Federated forum and link aggregator, packaged for YunoHost https://github.com/YunoHost-Apps/piefed_ynh
[11:41:39]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar merged [pull request #824](https://github.com/YunoHost-Apps/nextcloud_ynh/pull/824): Testing
[11:41:39]
<Yunohost Git/Infra notifications> [nextcloud_ynh] ericgaspar pushed 1 commit to master: Testing (#824) * Update ADMIN.md: update advice to open shell + add a note on how to promote a user to admin * Update ... ([38f165a5](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/38f165a550622313fea05aaf1e05a072a62ffc7b))
[13:10:14]
<Yunohost Git/Infra notifications> [borg_ynh] eauchat [commented](https://github.com/YunoHost-Apps/borg_ynh/pull/193#issuecomment-3188401340) on [issue #193](https://github.com/YunoHost-Apps/borg_ynh/pull/193) Improved error and success emails formating, and included missing general borg logs in them: @fflorent Specifying the log files path seems like it could be convenient for admins to know where to go digging for mo...
[15:19:01]
<tituspijean[m]> The repository: https://github.com/YunoHost-Apps/piefed_ynh/pull/1
[15:19:02]
<tituspijean[m]> @rimuatkinson:matrix.orgI've a working-ish prototype now, though I see part of the `flask init-db` process is interactive (https://codeberg.org/rimu/pyfedi/src/commit/ecabd8360eb9dbe6aacaee40b5cc5ff4e208c39e/app/cli.py#L181)
Is it possible for you to allow parameters to `flash init-db` so that we have a fully non-interactive setup?