Conversation
Notices
-
Setting up a !GNUsocial instance isn't bad; I've done it live in front of an audience twice now, and takes me less than 20 minutes. Don't know about !Diaspora; you can ask @stigatle about his adventures: https://quitter.no/notice/2292084
-
To get !GNUsocial for HTTPS only first set up your Web server for HTTPS only (including redirects from HTTP to HTTPS), then install GNUsocial normally. You'll only have problems if you install GNUsocial with HTTP then switch the server to HTTPS later (or vice versa), or arbitrarily allow HTTP and HTTPS connections for the same URLs.
-
@bobjonkman with Diaspora, my experience is you have to get a lot of software versions right. It installs under a very specific environment. It's also much more complicated than !gnusocial with your web server functioning as a proxy. This is the kind of thing that's a step too far for me.
As to switching from http to https, I think it *can* be done, but since !gnusocial now installs under https, I haven't had to try in quite a long time. !diaspora@oracle.skilledtests.com @stigatle @indi
-
"install GNUsocial with HTTP then switch the server to HTTPS later" ASA fragdeving your instance.
-
And by ASA I mean "also known as".
-
With #LetsEncrypt, there is no reason to install anything other than https!
-
From absolutely zilch, I just registered with a VPS provider https://datamantle.com/ (use the promotion code LAUNCH for some gratis credit), installed Debian, configured Apache, MariaDB, phpmyadmin; installed !GNUsocial, and created @bobjonkman2@gs.sobac.com all in about four hours. Ain't so tough.