cover photo

h.ear.t | tobias

 somewhere between the lines 
Attention all Hubzilla-admins, your action is required. Due to the recent news regarding we have changed our git hosting provider to You need to update your git repositories to reflect this change, including your Hubzilla web document root, addon repository etc.

Mario VavtiMario Vavti wrote the following post Wed, 06 Jun 2018 21:51:39 +0200
Bye, bye GitHub!
You all probably already noticed that GitHub was recently bought by Microsoft. See here if you have not.

After a brief orientation period the Hubzilla community decided to move the sourcecode to an independent, freedom-loving GitLab instance at Framasofts

To get the latest and greatest Hubzilla code, you need to point your installation to the new sourcecode location. This is pretty simple:

cd into your Hubzilla root directory and execute this command:
git remote set-url origin

For the addons: cd into your Hubzilla addons directory (probably extend/addon/hzaddons) and execute this command:
git remote set-url origin

Please do the same for the widget and theme repos if you already added those from GitHub.

The GitHub repos will not receive any updates anymore but will stay intact for a short transition period.
Issues and bugreports should be reported and discussed at for core and for addon issues.

!Hubzilla Announcements !Hubzilla Support Forum

 somewhere between the lines last edited: Tue, 10 Apr 2018 22:32:32 +0200  
When you register at Hubzilla you are presented with a choice of channel roles. There are
  • social channels with varying privacy settings
  • forums with varying privacy settings
  • feed channels
  • a soap box function for announcement only channels
  • group repositories

The docs explain the basics about what is what, but I was always missing a tabled overview. So I created one.

This will be handy. I'd share it but somehow the Link to Source is buggered.
This will be refined over time, this graphic is just a first quick and dirty draft done in LibreOffice Calc and will be updated into a native table.

That is going to be one crazy block of BBcode! And if history is any guide, it will become outdated rapidly. This is something we could probably generate automatically in the code. It could be accessible when people are selecting a permission role and would naturally stay up-to-date.

@Zachary Dunn
  last edited: Wed, 11 Apr 2018 18:14:14 +0200  
@Mike Macgirvin
You are right, I made a mistake. Social does not have perms_auto, which I understand as autoconnect.

What I have not yet managed to find a meaning for is $ret['limits']. Any hint? :)

And "Default Collection" ... I believe that means connections are sorted into a default privacy group, the new name for collection? Yet that is - unfortunately - only configurable if I chose custom mode. Which for me is a huuuge reason to chose custom mode but ... ... ... maybe that should be moved to general access?
Or does that mean "Default permission group", which then is not reflected if I change the channel role.
(Note to self: Need to describe these default permission group roles as "follower, contributor, publisher", have never really looked into that before.)

    case 'forum_private':
                $ret['perms_auto'] = false;
                $ret['default_collection'] = true;
                $ret['directory_publish'] = false;
                $ret['online'] = false;
                $ret['perms_connect'] = [
                    'view_stream', 'view_profile', 'view_contacts', 'view_storage',
                    'view_pages', 'view_wiki', 'post_wall', 'post_comments',
                    'post_mail', 'post_like' , 'chat'
                $ret['limits'] = PermissionLimits::Std_Limits();
                $ret['limits']['view_profile']  = PERMS_SPECIFIC;
                $ret['limits']['view_contacts'] = PERMS_SPECIFIC;
                $ret['limits']['view_storage']  = PERMS_SPECIFIC;
                $ret['limits']['view_pages']    = PERMS_SPECIFIC;
                $ret['limits']['view_wiki']     = PERMS_SPECIFIC;


Corrected the image.

 somewhere between the lines last edited: Mon, 09 Apr 2018 19:17:15 +0200  
Edit: This howto was moved to

where it is being maintained and updated.

Installing my favorite web suite aka Hubzilla on the forthcoming Debian 9 "Stretch" is a joy. Quick, straightforward and easy. I will show you how to do it in about 10 minutes or less.
Currently I am preparing for the switch to Debian 9 "Stretch". So far I am quite happy with the update and I am pretty happy to finally welcome back to my favourite distro the pacemaker clustering suite. But that is another story and shall be told at another time. :)
(This is just a quick cheatsheet, I will later write a longer howto for later. Promised.)
I am starting with a basic Debian installation. The only additional feature chosen during installation is ssh-server.
  • The Basics: Install the required dependencies:
    apt-get install vim git apache2 mariadb-server php certbot python-certbot-apache php-curl php-gd php-mbstring php-xml php-mysql php-zip
  • Webserver apache: Create vhost file /etc/apache2/sites-available/hubzilla.conf and enable vhost, enable the required apache module rewrite
    <VirtualHost *:80> 
        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/hubzilla
        <Directory />
            Options FollowSymLinks
            AllowOverride All
        <Directory /var/www/>
            Options Indexes FollowSymLinks MultiViews
            AllowOverride All
            Order allow,deny
            allow from all
        ErrorLog ${APACHE_LOG_DIR}/hubzilla_error.log
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/hubzilla_access.log combined

    Enable the new vhost
    enable /etc/apache2/sites-available/hubzilla.conf
    Enable apache modules rewrite
    a2enmod rewrite
    Restart apache2 in order to activate all these changes
    systemctl restart apache2
  • Download Hubzilla: clone the Hubzilla Git repository and chown everything to be writable to the webserver account www-data
    cd /var/www/ ; git clone ; chown -R www-data. hubzilla;
  • create the database
    mysql -u root 
    create database hubzilla ; CREATE USER 'hubzilla'@'localhost' IDENTIFIED BY 'totally-secret-password'; GRANT ALL PRIVILEGES ON hubzilla.* to 'hubzilla'@'localhost';
  • SSL Encryption: create the letscencrypt certificates in order to use SSL and have certbot automatically configure your apache vhost to use SSL. Just follow the instructions. Let certbot configure your vhost to use SSL.
  • setup a cronjob
    echo "*/10 * * * *    cd /var/www/hubzilla; /usr/bin/php Zotlabs/Daemon/Master.php Cron"  >> /etc/crontab
  • Finally: open your browser and follow the instructions.
Erik hat hEARt | tobiass Beitrag mit ⋕Installation verschlagwortet
Erik hat hEARt | tobiass Beitrag mit ⋕Debian verschlagwortet
Erik hat hEARt | tobiass Beitrag mit ⋕Howto verschlagwortet