You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, any user-uploaded file to our S3 bucket has their username (which is their email address) in the path, e.g. \thumbnails\[email protected]\filename.file_id.jpg Rather than exposing email addresses this way, we should update our S3 uploader to use a unique identifier of some type which is not a plaintext username and we should make sure to update all our existing uploads without losing or breaking existing uploads. These include project files, project logo images, user profile images -- basically any file uploaded to dlab by a user.
In sum, this issue requires:
a unique ID system which is not personal information
changing our uploader to use that unique ID
migrating all our old files to new links without breaking
Right now, any user-uploaded file to our S3 bucket has their username (which is their email address) in the path, e.g.
\thumbnails\[email protected]\filename.file_id.jpg
Rather than exposing email addresses this way, we should update our S3 uploader to use a unique identifier of some type which is not a plaintext username and we should make sure to update all our existing uploads without losing or breaking existing uploads. These include project files, project logo images, user profile images -- basically any file uploaded to dlab by a user.In sum, this issue requires:
Relevant code:
CivicTechExchange/civictechprojects/views.py
Line 731 in ff5cff7
The text was updated successfully, but these errors were encountered: