Details

    • Type: Task
    • Status: Closed
    • Priority: TBD
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Complexity:
      Undetermined

      Description

      Instead of using URLs to external images, we should allow users to upload images. The images could be stored in a networked storage (e.g., an S3 bucket) or within the database.

      Design ideas

      While people often recommend storing images in a file system instead of a database for an application, that's common advice when storing lots of images of arbitrary sizes and images that are accessed frequently. Limiting the marker image size to 200x200 pixels would yield a max PNG size of ~150K. Even with 1000 images, it would be in the range of ~150 MB of disk space or less. It's likely we'll have 20-50 sites with images... or fewer. So, we could consider using the database for storing marker images, making it simpler to deploy and manage the images. Storing the images as separate resource (a blob in MySQL) at their own path (e.g., /image/:id) would allow us to use nginx caching if ever needed to reduce unnecessary database reads.

        Attachments

          Activity

            People

            • Assignee:
              heliostrike Sai Sandeep Mutyala
              Reporter:
              cintiadr Cintia Del Rio
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: