Skip to content
This repository was archived by the owner on Aug 21, 2026. It is now read-only.
This repository was archived by the owner on Aug 21, 2026. It is now read-only.

Document occ incoming-shares:poll for update detection with federated shares #856

Closed

Description

@mmattel

What Needs to be Documented?

With core owncloud/core#34903 (Add a command to poll incoming federated shares for updates)
a new occ command needs to be documented: incoming-shares:poll

Where Does This Need To Be Documented?

admin_manual, occ command set

Why Should This Change Be Made? (Optional)

What Type Of Content Change Is This? (Optional)

  • New Content Addition
  • Old Content Deprecation
  • Existing Content Simplification
  • Bug Fix to Existing Content

Which Manual Does This Relate To? (Optional)

  • Admin Manual
  • Developer Manual
  • User Manual
  • Android
  • iOS
  • Branded Clients
  • Desktop Client
  • Other

@PVince81 Pls let us know if it is correct to have this for 10.2 + no backporting to older releases
@VicDeo @jvillafanez FYI
@settermjd

Activity

  1. changed the title [-]New core occ command (for teh upcoming release 10.2)[/-] [+]New core occ command (part of the upcoming owncloud release)[/+] on Mar 29, 2019
  2. PVince81 commented on Apr 1, 2019

    @PVince81
    Contributor

    @VicDeo can you provide a quick summary that could be incorporated into the documentation ?

    If there is a section about federated shares, it could be linked back to the section for this command for improving update detection and syncing.

  3. changed the title [-]New core occ command (part of the upcoming owncloud release)[/-] [+]Document occ incoming-shares:poll for update detection with federated shares[/+] on Apr 1, 2019
  4. VicDeo commented on Apr 3, 2019

    @VicDeo
    Contributor

    summary: due to performance reasons federated shares are not updated automatically.
    The particular directory of the federated share is updated only when user browse into it via web UI.

    CLI command occ incoming-shares:poll could be added into the system crontab in order to poll federated shares for updates automatically.

  5. mmattel commented on Apr 3, 2019

    @mmattel
    ContributorAuthor

    Just for the record, this command polls all fed shares recieved, there is no path necessary to provide.

  6. pmaier1 commented on Apr 8, 2019

    @pmaier1

    What is the recommended interval for running the background job? @VicDeo @micbar

  7. pmaier1 commented on Apr 8, 2019

    @pmaier1

    Does the command provide any options?

  8. micbar commented on Apr 8, 2019

    @micbar
    Contributor

    @pmaier1 The first question is currently discussed in our testing.

    This command does not provide any options.

  9. VicDeo commented on Apr 10, 2019

    @VicDeo
    Contributor

    What is the recommended interval for running the background job?

    The recommended is never. :)
    Since it iterates through all federated shares in one go the interval depends on the federated shares amount.
    Once per 12 hours should be safe enough for any instance. It could be reduced to once per 2 hrs for instances with low federated shares amount.

  10. added 5 commits that reference this issue on Apr 16, 2019
    646eab1
    d7ed798
    79fa468
    5959f46
    3c77e45
  11. added 2 commits that reference this issue on Apr 17, 2019
    d703e2a
    660ac93
  12. pmaier1 commented on May 6, 2019

    @pmaier1

    Can we add some more information like I tried in the release notes (starting here https://github.com/owncloud/docs/pull/967/files#diff-ba12788edde90b189cd9bb4d1b5492afR90)? I think that makes it more clear for admins how to handle the interval for the background job.

  13. reopened this on May 6, 2019
  14. added this to the Development milestone on May 21, 2019
  15. settermjd commented on May 21, 2019

    @settermjd
    Contributor

    Closing, as the implementing PR, #1134, has been merged.

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions