servala/servala-portal
3
0
Fork 0
Code Issues 21 Pull requests 5 Projects 2 Releases Packages 2 Activity Actions

Object Storage not properly configured #67

New issue
Closed
opened 2025-05-27 09:27:21 +00:00 by tobru · 3 comments
tobru commented 2025-05-27 09:27:21 +00:00
Owner
Copy link

Description

After configuring object storage in 5f38856dd9, the application didn't start up anymore:

SystemCheckError: System check identified some issues:

ERRORS:
?: (staticfiles.E005) The STORAGES setting must define a 'staticfiles' storage.

I reverted the configuration for now in 1dda974e11

## Description After configuring object storage in 5f38856dd962a1caa1597bfe6a23b9522327e855, the application didn't start up anymore: ``` SystemCheckError: System check identified some issues: ERRORS: ?: (staticfiles.E005) The STORAGES setting must define a 'staticfiles' storage. ``` I reverted the configuration for now in 1dda974e110083ad30745ec11e16b31027f2f908
tobru added the
bug
 label 2025-05-27 09:27:21 +00:00
tobru added this to the Development Planning project 2025-05-27 09:27:24 +00:00
tobru commented 2025-05-27 13:34:01 +00:00
Author
Owner
Copy link

Even after fixing settings in #69 file uploads don't land in object storage and are also not retrieved from there.

Even after fixing settings in #69 file uploads don't land in object storage and are also not retrieved from there.
rixx commented 2025-06-15 16:37:45 +00:00
Member
Copy link

I only added django-storages instead of django-storages[s3] to the package list, which may be the reason (though I would have expected django-storages to yell about that). Opened a MR in #102.

I only added `django-storages` instead of `django-storages[s3]` to the package list, which may be the reason (though I would have expected django-storages to yell about that). Opened a MR in #102.
tobru commented 2025-06-16 15:32:39 +00:00
Author
Owner
Copy link

Now that Mr. Deployment Specialist ™️ realized that object storage works best when it is configured, and now it is configured dc9a499e00 - it actually works. The usual "Kaum macht man(n) es richtig, funktionierts".

Now that Mr. Deployment Specialist ™️ realized that object storage works best when it is configured, and now it is configured https://servala.app.codey.ch/servala/servala-portal/commit/dc9a499e00cba6bd6e699cd7daa6d2870a2848d4 - it actually works. The usual "Kaum macht man(n) es richtig, funktionierts".
tobru closed this issue 2025-06-16 15:32:39 +00:00
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
132-frontend-improvements
renovate/sentry-sdk-2.x
renovate/coverage-7.x
renovate/lock-file-maintenance
renovate/jsonschema-4.x
instance-edit-permi-from-org
Clear current reference
2025.04.14-1
Labels
Clear labels   
dependencies

Dependencies Update

  
bug

Something is not working

  
change

Change an existing feature

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Development Planning
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: servala/servala-portal#67
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?