Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • core core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 241
    • Issues 241
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hubzillahubzilla
  • corecore
  • Issues
  • #1628
Closed
Open
Issue created Sep 26, 2021 by Happy Pony@HappyPony

Space needed for channel XY during channel import

Helpful for the Hubzilla users, who are not Hubzilla admins, if they had the possibility to determine before the import, how much storage space the channel XY needs on the target hub. And perfect would be, if before the import the Hubzilla engine would warn the user "There is not enough space available for channel XY on the target hub".

I believe making the value "Space needed for channel XY" available to a channel owner, who is not a Hubzilla admin is critical in determining whether potential Hubzilla users can take advantage of Hubzilla benefits. And it is crucial whether potential Hubzilla users can use Hubzilla productively.

Details s. Channel cloning

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking