airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (Jira)" <>
Subject [jira] [Commented] (AIRAVATA-3354) Wagtail: better handling exporting/importing of images and documents
Date Tue, 11 Aug 2020 21:26:00 GMT


Marcus Christie commented on AIRAVATA-3354:

Another idea would be to store the media files in S3 or some other object storage backend.
This way there wouldn't be as much need to export/import, just use the same object storage
backend for that gateway.

> Wagtail: better handling exporting/importing of images and documents
> --------------------------------------------------------------------
>                 Key: AIRAVATA-3354
>                 URL:
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
> 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

View raw message