You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Marcus Christie (Jira)" <ji...@apache.org> on 2020/07/23 16:37:00 UTC

[jira] [Created] (AIRAVATA-3354) Wagtail: better handling of images and documents

Marcus Christie created AIRAVATA-3354:
-----------------------------------------

             Summary: Wagtail: better handling of images and documents
                 Key: AIRAVATA-3354
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3354
             Project: Airavata
          Issue Type: New Feature
          Components: Django Portal
            Reporter: Marcus Christie
            Assignee: Marcus Christie


When a new set of wagtail pages are created (a "theme"), we can export those pages into a json file that can then be loaded into a separate Django portal instance. This works pretty well for developing a library of themes or for exporting/importing a set of wagtail pages to a different Django portal instance. However, we don't have a good way to export wagtail images (and documents, although I don't think we use those in our themes). What we currently do is we commit those images into the media directory of the repository. However, this tends to bloat the repository over time and any Django portal instance will only use a fraction of the images there.

Ideally, we would be able to produce an export of the Wagtail pages that includes the page content plus any files like the images and documents.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)