https://github.com/openfun/dmcloud-migrate

Python scripts for migration from Dailymotion Cloud
https://github.com/openfun/dmcloud-migrate

Last synced: 8 months ago
JSON representation

Python scripts for migration from Dailymotion Cloud

• Host: GitHub
• URL: https://github.com/openfun/dmcloud-migrate
• Owner: openfun
• License: mit
• Created: 2015-01-15T09:29:15.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2015-09-11T15:37:32.000Z (over 10 years ago)
• Last Synced: 2025-01-13T12:48:43.425Z (over 1 year ago)
• Language: Python
• Size: 184 KB
• Stars: 2
• Watchers: 17
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.rst
  • License: LICENSE

Awesome Lists containing this project

README

          
Dailymotion Cloud migration scripts

===================================

The DmCloud service by Dailymotion is shutting down; this repository provides

python scripts for making a backup of all your DmCloud assets, and eventually

migrating your data to another service.

Install

-------

Always use a virtual environment when installing python dependencies::

    virtualenv venv

    source venv/bin/activate

    pip install git+https://github.com/openfun/dmcloud-migrate.git

Usage

-----

Set up your DmCloud credentials::

    export DMCLOUD_USER_ID="yourdmclouduserid"

    export DMCLOUD_API_KEY="yourdmcloudapikey"

Check how much space the download is going to take::

    dmsize ./path/to/download/

Download media files::

    # Check everything before actually downloading:

    dmdownload --fake ./path/to/download/

    # Perform a full backup:

    dmdownload ./path/to/download/ 

    # Perform a full backup for one of your organisation's users:

    dmdownload --user=username ./path/to/download/

File system hierarchy

---------------------

Whenever you perform a full backup for your organisation, the files will be

downloaded in the following filesystem hierarchy::

    rootpath/

        username1/

            media.json

            medianame1/

                mediaid/

                    assets.json

                    assetname1

                    assetname2

                    ...

            medianame2/

                ...

            ...

        username2/

            ...

        ...

For instance, if you have a single user named 'bob', here is a possible file

structure::

    $ dmdownload --user=bob ./dump/

    ./dump/

        bob/

            media.json

            My holiday video (2014)/

                531594c29473991c7f21e181/

                    assets.json

                    jpeg_thumbnail_medium.jpg

                    mp4_h264_aac_hd.mp4

                    source.mp4

            Test video 42/

                1264cde462416235548e5f69/

                    assets.json

                    jpeg_thumbnail_source.jpg

                    source.dat