Friendica Administration

Most of the administrative work–basic settings, user management etc.–of a Friendica node is done in the Admin Panel (example.com/admin) of the node. Some of the administrative features, mostly new ones, have not made it into the panel yet, but they are available with the command line interface of Friendica, which is provided by bin/console.

See the Admin Tools page for a list of tools that are shipped with Friendica and some useful 3rd party tools.

Bad things will happen to your server. Sooner or later.

Therefore you should have a backup strategy. To easy the planing of such a strategy, here is a list of files you need to restore your Friendica node.

  • Configuration files: config/local.config.php and the .htaccess file if it was edited beyond the .htaccess-dist one.
  • A dump of the used database.
  • If the file storage backend is set to Filesystem, a copy of the root filesystem folder.

The Friendica Project aims to release a new stable version of the platform once every quarter. Sometimes it might take a bit longer, and in cases of critical fixes there might be a release sooner. Releases will be announced at the Friendica homepage and the announcements will be automatically distributed by the @news@forum.friendi.ca account.

The development cycle of a new release starts with the stable release of the last release. This code will enter the development branch of the git repositories. After about two month, a release candidate (RC) branch will be branched off from the develop branch and the team will concentrate their work to stabilize the code and enhance the translation + documentation in the rc branch. In this time, which usually lasts two weeks, the develop branch wont see (much) action. Once the beta testers of the rc branch are happy the rc branch will be merged into the stable branch and thus becomes the new release.

The Friendica team does not advise you to use the develop or rc branches on your server. But is happy about every alpha or beta testing person who is willing to take the risk and report problems during the development phases of a new release.

  • Last modified: 2022-05-21 07:28