Friendica Communications Platform (please note that this is a clone of the repository at github, issues are handled there)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

71 lines
3.0 KiB

  1. Updating Friendica
  2. ===============
  3. * [Home](help)
  4. ## Using a Friendica archive
  5. If you installed Friendica in the ``path/to/friendica`` folder:
  6. 1. Unpack the new Friendica archive in ``path/to/friendica_new``.
  7. 2. Copy ``config/local.config.php``, ``photo/`` and ``proxy/`` from ``path/to/friendica`` to ``path/to/friendica_new``.
  8. 3. Rename the ``path/to/friendica`` folder to ``path/to/friendica_old``.
  9. 4. Rename the ``path/to/friendica_new`` folder to ``path/to/friendica``.
  10. 5. Check your site. Note: it may go into maintenance mode to update the database schema.
  11. 6. If everything works, just delete the ``path/to/friendica_old`` folder.
  12. To update Addons from an archive, simply delete the ``path/to/friendica/addon`` and replace it with the provided archive.
  13. ## Using Git
  14. You can get the latest changes at any time with
  15. cd path/to/friendica
  16. git pull
  17. bin/composer.phar install
  18. The addon tree has to be updated separately like so:
  19. cd path/to/friendica/addon
  20. git pull
  21. For both repositories:
  22. The default branch to use is the ``master`` branch, which is the stable version of Friendica.
  23. It is updated about four times a year on a fixed schedule.
  24. If you want to use and test bleeding edge code please checkout the ``develop`` branch.
  25. The new features and fixes will be merged from ``develop`` into ``master`` after a release candidate period before each release.
  26. Warning: The ``develop`` branch is unstable, and breaks on average once a month for at most 24 hours until a patch is submitted and merged.
  27. Be sure to pull frequently if you choose the ``develop`` branch.
  28. ### Considerations before upgrading Friendica
  29. #### MySQL >= 5.7.4
  30. Starting from MySQL version 5.7.4, the IGNORE keyword in ALTER TABLE statements is ignored.
  31. This prevents automatic table deduplication if a UNIQUE index is added to a Friendica table's structure.
  32. If a DB update fails for you while creating a UNIQUE index, make sure to manually deduplicate the table before trying the update again.
  33. #### Manual deduplication
  34. There are two main ways of doing it, either by manually removing the duplicates or by recreating the table.
  35. Manually removing the duplicates is usually faster if they're not too numerous.
  36. To manually remove the duplicates, you need to know the UNIQUE index columns available in `database.sql`.
  37. ```SQL
  38. SELECT GROUP_CONCAT(id), <index columns>, count(*) as count FROM users
  39. GROUP BY <index columns> HAVING count >= 2;
  40. /* delete or merge duplicate from above query */;
  41. ```
  42. If there are too many rows to handle manually, you can create a new table with the same structure as the table with duplicates and insert the existing content with INSERT IGNORE.
  43. To recreate the table you need to know the table structure available in `database.sql`.
  44. ```SQL
  45. CREATE TABLE <table_name>_new <rest of the CREATE TABLE>;
  46. INSERT IGNORE INTO <table_name>_new SELECT * FROM <table_name>;
  47. DROP TABLE <table_name>;
  48. RENAME TABLE <table_name>_new TO <table_name>;
  49. ```
  50. This method is slower overall, but it is better suited for large numbers of duplicates.