upgrading_from_05.rst 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  1. =========================
  2. Upgrading from Misago 0.5
  3. =========================
  4. Misago 0.6 comes with special utility that allows those upgrading from Misago 0.5 to move their data to new site. This utility, named ``datamover``, provides set of management commands allowing you to move data over.
  5. Preparing for move
  6. ==================
  7. To move your data to new site, you'll need to first install Misago 0.6, and then tell mover how to access your old data.
  8. Database
  9. --------
  10. In your site's ``settings.py`` find ``DATABASES`` setting, and add connection named ``misago05``::
  11. DATABASES = {
  12. 'default': {
  13. # new database used by Misago
  14. },
  15. 'misago05': {
  16. 'ENGINE': 'django.db.backends.mysql',
  17. 'NAME': 'your_misago_05_database_name',
  18. 'USER': 'your_misago_05_database_user',
  19. 'PASSWORD': 'your_misago_05_database_password',
  20. 'HOST': 'localhost',
  21. 'PORT': '3306',
  22. }
  23. }
  24. User uploads
  25. ------------
  26. You'll actually won't need all of your old forum's files for move, only attachments and media directories. To tell data mover where it can find those directories, add ``MISAGO_OLD_FORUM`` setting somewhere in your ``settings.py``, just like in example below::
  27. MISAGO_OLD_FORUM = {
  28. 'ATTACHMENTS': '/home/somewhere/myoldmisago/attachments/',
  29. 'MEDIA': '/home/somewhere/myoldmisago/media/',
  30. }
  31. Creating superuser
  32. ------------------
  33. Its good idea to create superuser accounts for all site administrators. Don't worry about their e-mails being same as ones on old forum. If this happens Misago will simply reuse those accounts, instead of creating new ones.
  34. Moving forum configuration
  35. ==========================
  36. To move configuration over to new forum, run ``python manage.py movesettings`` command.
  37. .. note::
  38. Some settings have been moved from admin to configuration file or removed. Those will not be migrated. Please consult :doc:`configuration reference </developers/settings>` for available settings that you will need to add yourself.
  39. Moving users
  40. ============
  41. To move users over to new forum, run ``python manage.py moveusers`` command.
  42. Moved users will be assigned default rank and permissions as those aren't moved by the datamover. If user with such e-mail address already exists in database (because you've used this e-mail ealier to create superuser account), his or her permissions and rank will be left as they are in new database.
  43. If user avatar could not be moved (for .eg because uploaded picture is smaller than allowed by ``MISAGO_AVATARS_SIZES``), default avatar will be set for this user.
  44. In case of username collision, Misago will append digits to new user's username and print a warning in console to let you know about this.
  45. Moving threads
  46. ==============
  47. Todo
  48. Wrapping up migration
  49. =====================
  50. Not everything is moved over. Thread labels will be turned into subcategories of their categories. With exception of pre-made superuser accounts, all users will be assigned to "Members" rank and will have only default roles of forum members. Likewise no permissions will be moved over to users, categories or ranks, and you will have to reset those manually.
  51. Changed links
  52. -------------
  53. Todo