Flyspray - The bug killer!

I was able to install flyspray dev version complete with composer and dependencies under some circumstances.

So maybe a release without included composer dependencies can be used also for users without ssh access to their webspace.

The decision graph (incomplete):

<vendor/autoload.php exists?> --yes--> run flyspray or flyspray setup
      |
      |no
      V                                                                                                                           ----------------
<PHP safe_mode ON ?> ---yes---> <perl ./ executable?> --yes--> <run composerit.pl ok?> --yes--> <run composerit2.pl ok?> --yes--> | setup screen |
      |                          ^       |                        ^                |                            |                 ----------------  
      |no                        |       |no          yes, upload to cgi-bin       |no                          |no
      V                          |       |                        |                V                            V
<composerit.php ok?> --no--> goto perl   ---> <perl cgi-bin/ executable?> --no--> install composer with ssh or download a flyspray release with all third party files included
      |
     yes
      |
      V
 ----------------
 | setup screen |
 ----------------

Fun fact: These experiments were detected probably by an IDS as probably suspicious activities and the whole flyspray install directory got a (temporary?) .htaccess "deny from all".
But as long as it runs through one time and the perl and setup files are removed after install all should be fine.

This is my current status of making the required install of composer of the web for lazy users or users without shell access to their webspace.

   setup1.png (97.3 KiB)
   setup2.png (82.4 KiB)
   setup3.png (72.2 KiB)
   setup4.png (69.8 KiB)

Reminder setting at install seems outdated.
The code for a notification daemon process seems to be dropped a while ago because it didn't worked.

There are only 2 options available for the reminder setup (option php dropped)

• 0 for off
• 1 for on (which means schedule.php accept to be called by a cronjob)

So are you ok when I drop the "reminder daemon" description and replace it by some information how to setup cronjob (or Task Scheduler on Windows) for Flyspray?

   reminder.png (10.1 KiB)

Note to myself

Web based install:
TODO:

• check if phar and openssl extensions exist before trying composer stuff
• catch the error messages if possible

Adapted the setup thema a bit to the CleanFS theme.