ADVANCED Hubzilla Install

Tue, 07 Aug 2018 15:50:20 +0000

Is anyone doing any weird ADVANCED Hubzilla installations?  I'm thinking of things like:

(1) Some sort of network-backed file space (eg., Amazon SES, NFS, or something else)
(2) Tighter integration with things like NGINX's secure_links to allow for larger files to be served directly by the web server while maintaining security but not needing to pass large files through PHP.  This would be necessary, for instance, for large video files/audio files/etc. to be served securely (and/or for secured streaming) allowing for access control but not served over webdav.

I'm thinking/working in these directions - looking for others doing the same - but also thinking that the !Hubzilla Development forum and the !Hubzilla Support Forum would likely not be the right places to discuss stuff like this.  At least not at this stage where we're still trying to figure it out.

So, I guess, if there's a place you all are gathering, let me in on the secret.  If not, let me know and I'll get one set up.

Tue, 07 Aug 2018 15:58:57 +0000

Notice the idea here is to layer Hubzilla in a stack with other existing technologies - and not only look at the potential of Hubzilla native. These are things where configuration of other system level software may be necessary or other advanced concepts need to be implemented beyond just setting up a base Web Server with PHP capability or installing Hubzilla in shared hosting space.

Tue, 07 Aug 2018 16:52:23 +0000

That's fine with me - I was just concerned that since it strays from Hubzilla "proper" into things like NGINX configurations and cross configuration issues it may be confusing as people are trying to onboard and just get the basics down.  I'd hate to have people think you need to know the nuts and bolts of LUA programming using OpenResty's NGINX suite in order to install Hubzilla.

Now, in order to get Hubzilla to do some really cool stuff (for example, custom domains for web or wiki content), such things may be the best route rather than trying to change up the code.

Another example would be, I'd hate for people to think you need to implement either some complicated procmail scripts or a full implementation of the qmail MTA in order to install Hubzilla.  But to fully integrate email with the activity stream or ZotMail, that would probably be the way to do it rather than trying to create an email MTA within Hubzilla.

These are the type of things I'm talking about - Hubzilla as part of the ecosystem/toolchain within a server rather than a silo/stand-alone solution.  I guess call it "Full Stack Hubzilla".

I just didn't want to go over people's heads or intimidate especially beginners.  Hubzilla is very unique among the solutions I've reviewed in that it can take a place alongside these other things and be a prominent part of a much larger solution.  It doesn't HAVE to be, but it can - and in that context, it's possible to do some REALLY COOL STUFF - but it is definitely ADVANCED and not or the feint of heart.

Tue, 07 Aug 2018 19:08:48 +0000

Ah, ok, then, my mistake. I was thinking it was a narrower focus than that. If this is the right place, then there it is.

What do you think about setting up a wiki that could allow kind of a knowledge repository (config examples, implementation notes, etc)? Kind of a step between our own private work notes and more formal documentation.

Maybe make it invite only or watch the discussion and invite contributions based on posts and comments.