Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give ability to configure provision from occ command #10356

Open
lebuzzer opened this issue Nov 13, 2024 · 0 comments
Open

Give ability to configure provision from occ command #10356

lebuzzer opened this issue Nov 13, 2024 · 0 comments

Comments

@lebuzzer
Copy link

lebuzzer commented Nov 13, 2024

Is your feature request related to a problem? Please describe.

I try to setup a docker-compose instance of nextcloud based on official image using post-installation scripts.
for the moment everything (core / ldap / contact / calendar) is done except mail provisioning.
there is no easy way to setup provisioning from occ command.

Describe the solution you'd like

like ldap, permit to populate provision table with following commands :

  • occ ldap:create-empty-config
  • occ ldap:set-config <created config id> <param> <value>

which could become for mail :

  • occ mail:provisioning:empty-create (output is created id of oc_mail_provisionings)
  • occ mail:provisioning:set <id> <param> <value>
  • example :
    • occ mail:provisioning:empty-create
      (example return "2" on stdout)
    • occ mail:provisioning:set 2 provisioning_domain domain.tld
    • occ mail:provisioning:set 2 email_template %EMAIL%
    • occ mail:provisioning:set 2 imap_user %EMAIL%
    • occ mail:provisioning:set 2 imap_host imap.domain.tld

Describe alternatives you've considered

I build an instance with cron and add mariadb client to insert configuration I need.
But this is a bad solution to add tools in instance just for initial setup.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant