• Status Planned
  • Percent Complete
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity High
  • Priority Low
  • Reported Version
  • Due in Version 1.1 devel
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by magicfinger - 15.03.2013
Last edited by peterdd - 15.07.2016

FS#1849 - Installer Overhaul

The application installer needs an overhaul, all strict notices fixed and the associated dependant tasks resolved.

The task depends upon
ID Project Summary Priority Severity Assigned To Progress
1673 Flyspray FS#1673 - Only white screen after upgrade to 1.0 - reasons Low High
1744 Flyspray  FS#1744 - Error "Connection could not be established" after upgrading from  Very Low Very Low
1835 Flyspray  FS#1835 - Upgrade to 1.0 requires dokuwiki syntax vs. free text/html handl  Low High
1848 Flyspray  FS#1848 - password field  Very Low Very Low
1850 Flyspray  FS#1850 - Installer not Creating first user  Low High
1851 Flyspray  FS#1851 - GD Library Setup Checks  Very Low Low
1852 Flyspray  FS#1852 - Blank DB Password  Very Low Low magicfinger
This task has the following sub-task
ID Project Summary Priority Severity Assigned To Progress
2108 Flyspray FS#2108 - Support local language when install Flyspray Very Low Medium
Project Manager

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
      V                                                                                                                           ----------------
<PHP safe_mode ON ?> ---yes---> <perl ./ executable?> --yes--> <run ok?> --yes--> <run 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
 | 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.

Project Manager

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.

Project Manager

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?

Project Manager

Note to myself

Web based install:

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

Adapted the setup thema a bit to the CleanFS theme.


Available keyboard shortcuts


Task Details

Task Editing