YunoHost/doc
1
0
Fork 0
mirror of https://github.com/YunoHost/doc.git synced 2024-09-03 20:06:26 +02:00
Code Issues Projects Releases Packages Wiki Activity
doc/pages/04.applications/10.docs/osada/app_osada.md
pp-r e0c147b099
Create app_osada.md
2022-10-05 12:05:57 +02:00

2.7 KiB
Raw Blame History

title template taxonomy routes
Osada docs
category
docs, apps
default
/app_osada

Installer Osada with YunoHost Integration level

Index

Osada uses Zot6 protocol which is next version of zot5 protocol. Osada has native support for the ActivityPub protocol (W3C standard) as well as the more advanced features. It can inter-operate with other social networking applications and projects in either of these spaces, including Mastodon, Pleroma, Pixelfed, PeerTube, Funkwhale, Zap, Friendica, Hubzilla, and many more.

Screenshots

Screenshot of Osada

Disclaimers / important information

This app claims following features:

  • LDAP integration
  • Multi-instance
  • Adeed php.log in the root folder for debugging PHP, with logrotate applied on it (can be accesssed by admin->logs and entering the php.log).
  • Fail2Ban
  • Option to choose between Mysql and PostgreSQL for the Osada

Ldap Admin user rights, logs and failed database updates

  • For admin rights: When installation is complete, you will need to visit your new hub's page and login with the admin account username which was entered at the time of installation process. You should then be able to create your first channel and have the admin rights for the hub.

  • For normal YunoHost users: Normal LDAP users can login through LDAP authentication and create there channels.

  • Failing to get admin rights: If the admin cannot access the admin settings at https://osada.example.com/admin then you have to manually add 4096 to the account_roles under accounts for that user in the database through phpMyAdmin.

  • For logs: Go to admin->logs and enter the file name php.log.

  • Failed Database after Upgrade: Some times databse upgrade fails after version upgrade. You can go to hub eg. https://osada.example.com/admin/dbsync/ and check the numbers of failled update. These updates will have to be ran manually by phpMyAdmin.

Useful links