Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 376
    • Issues 376
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #1319
Closed
Open
Issue created Dec 30, 2020 by pullopen@pullopen

S3 storage via Scaleway is forced to set private

Steps to reproduce

Trying to use Scaleway as S3 storage.

What happens?

Every file uploaded to Scaleway is automatically set private as Scaleway do not allow policy setting. In documentary of Scaleway it says I'll need to add --acl public-read when uploading.

What is expected?

So is there a way to add this term?

Context

Funkwhale version(s) affected: 1.0.1

Docker, nginx.

Edited Dec 30, 2020 by pullopen
Assignee
Assign to
Time tracking