Skip to content

installer: database section now visible if auto-setup is used #56160

Description

@scubamuc

Hey team,

the Nextcloud snap team are busy testing Nextcloud snap PR for vs. 32.0.1snap1 and have come across an (issue/change) during initial setup which we're confused about...

nextcloud-snap/nextcloud-snap#3305 (comment)

nextcloud (beta/pr-3305) 0+git.493ed6a from Nextcloud✓ installed

Initial setup

  • initial install page shows selector for storage and DB
grafik

do you know if there's any method to disable the initial install selector? since autoconfig is detected and in place, we should be able to skip that?

any ideas?

Activity

  1. szaimen commented on Nov 4, 2025

    @szaimen
    Contributor
  2. kesselb commented on Nov 4, 2025

    @kesselb
    Contributor

    The storage and database section button being shown is related to the migration of the setup page to vue: #51464.

    stable31 hides the button if datadirectory and database are given and errors beeing empty:

    <?php if (!$_['directoryIsSet'] or !$_['dbIsSet'] or count($_['errors']) > 0): ?>
    <fieldset id="advancedHeader">
    <legend><a id="showAdvanced" tabindex="0" href="#"><?php p($l->t('Storage & database')); ?><img src="<?php print_unescaped(image_path('core', 'actions/caret.svg')); ?>" /></a></legend>
    </fieldset>
    <?php endif; ?>

    stable32 always shows the button, the section is closed when the configuration is valid:

    <details :open="!isValidAutoconfig" data-cy-setup-form-advanced-config>
    <summary>{{ t('core', 'Storage & database') }}</summary>

    do you know if there's any method to disable the initial install selector?

    There's none.

    cc @skjnldsv @susnux

  3. kesselb commented on Nov 4, 2025

    @kesselb
    Contributor
    1. Needs triage (Pending check for reproducibility or if it fits our roadmap)

    Is reproduciable.

    Needs decision if it fits the roadmap or we are good with the button always beeing shown.

  4. scubamuc commented on Nov 4, 2025

    @scubamuc
    Author
    1. Needs triage (Pending check for reproducibility or if it fits our roadmap)

    Reproduciable.

    Needs decision if it fits the roadmap or we are good with the button always beeing shown.

    please don't hesitate to give me a shout if you need a testing instance, although its easy to install and remove using snap;

    • install
    sudo snap install nextcloud --channel=latest/beta/pr-3305
    
    • remove
    sudo snap remove --purge nextcloud
    
  5. susnux commented on Nov 5, 2025

    @susnux
    Contributor

    I think it behaves like I would expect it to behave:

    • if no auto config it expands the section to fill in data
    • if auto config is used it pre-fills the form but allows to manually change if needed (but collapses section by default)

    I think this is more a discussion for product design, cc @nextcloud/designers

  6. moved this from To triage to Triaged in 🧑‍🤝‍🧑 Community triageon Nov 5, 2025
  7. added theissue type on Nov 5, 2025
  8. changed the title [-]-- Nextcloud snap team assistance required --[/-] [+]installer: database section now visible if auto-setup is used[/+] on Nov 5, 2025
  9. skjnldsv commented on Nov 6, 2025

    @skjnldsv
    Member

    I'm ok adding a v-hide directly if the config is valid 👍

  10. skjnldsv commented on Nov 6, 2025

    @skjnldsv
    Member
  11. skjnldsv commented on Nov 6, 2025

    @skjnldsv
    Member

    I think this is more a discussion for product design, cc @nextcloud/designers

    Please confirm your choice on #56231

    @scubamuc imho, that should not be an issue to continue with your snap package, no ?
    Or is it bevause users should never change anything on this part of the config when using snap ?

  12. scubamuc commented on Nov 6, 2025

    @scubamuc
    Author

    @skjnldsv thanks for your response

    imho, that should not be an issue to continue with your snap package, no ?

    nextcloud-snap/nextcloud-snap#3305 (comment)

    i'm the only non-dev in the team, so that's not a decision i can make. @kyrofa @pachulo please confirm so that @skjnldsv can go ahead.

    Or is it bevause users should never change anything on this part of the config when using snap ?

    the snap was designed with IoT in mind and requires little to no user interaction. it is possible to change/move the data directory, but this is best done post install due to snap confinement and required snap actions.

    it is misleading letting users think they may be able to change the database or the data directory at install which would certainly fail.

  13. kyrofa commented on Nov 6, 2025

    @kyrofa
    Member

    i'm the only non-dev in the team, so that's not a decision i can make. @kyrofa @pachulo please confirm so that @skjnldsv can go ahead.

    I'm a smidge confused as to what I'm confirming here 😛 . +1 to the change though, thank you @skjnldsv. @scubamuc is correct, that dialog is really just a foot gun for snap users.

  14. skjnldsv commented on Nov 6, 2025

    @skjnldsv
    Member

    @kyrofa please confirm that the current state is not a blocker (showing the collapsed view) to release your 32 snap version.
    We can improve for 33 or 32.0.2, but if that is not a blocker, we can leave as is

  15. kyrofa commented on Nov 6, 2025

    @kyrofa
    Member

    Ah, okay I get it now, sorry for being dense 😄 . We would prefer not to release a foot gun if we can avoid it, would you mind backporting to v32? We can wait for 32.0.2.

  16. skjnldsv commented on Nov 7, 2025

    @skjnldsv
    Member

    We would prefer not to release a foot gun if we can avoid it

    But that's what I don't get, how is that a true blocker for you?

  17. pachulo commented on Nov 8, 2025

    @pachulo
    Contributor

    But that's what I don't get, how is that a true blocker for you?

    It's a blocker in the sense that we have the feeling that, in addition to being misleading, it will cause requests on the community forum and our GitHub.

    Besides, version 32.0.2 will be released on the 20th, and we already have version 31.0.10 in our stable channel, so it's harmless to wait for this fix.

    By the way, thanks for the fix!

  18. added a commit that references this issue on Sep 30, 2026
    93c72c6
  19. added a commit that references this issue on Sep 30, 2026
    39ba1b5
  20. added a commit that references this issue on Oct 1, 2026
    07013eb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions