Visvanath Ratnaweera hozzászólásai

Kép Kép
William

Thanks (and that was very fast typing! ;)

1) Create a new Moodle site:
If "but it may carry with the legacy files" materializes, my the whole exercise would be useless.

2) Manually delete all of the legacy files:
That is what I thought. Simply make the moodledata/courseno/ directories unreadable to the web-server (for later removal). Wanted opinions before I send the teachers looking for missing files!

3) Rebuild your courses manually in the 3.1 installation:
Out of the question. (It is not _me_, you know. ;tojás
Kép Kép
I am planning to migrate a Moodle 2.7 installation to 3.1. This site has a long history, starting from Moodle 1.5. As a result it has those "legacy files", visible as moodledata/1/ to moodledata/290 - obviously from courses during the 1.x days. Not that they interfere in any way today, but I don't want ghosts in the server who may show up exactly at the wrong moment.
;-(

Any formula of getting rid of then now? I don't mind a cleaning action with all the testing involved.
Értékelések átlaga: -
Kép Kép
Hallo Marvin

Technisch: HTTP war nicht gedacht Monsterdateien hochzuladen. Dafuer gibt es viele Protokolle, du hast FTP erwaehnt. Also ein https://docs.moodle.org/32/en/File_system_repository einrichten und den Film via FTP oder vergleichbares dorthin hochladen.

Praktisch: Ob 4 GB grosse Datein, obendrauf Filme, direkt via Moodle anbieten eine gute Idee ist, das bezweifele ich. Sonst gaebe es keine Streaming-Server (YouTube wenn dir der Datenkrake Google nichts ausmacht, sonst Vimeo, usw.)