I think since this is now running our web installer totally useless and broken, let's please keep the third party files in their place, we must not rely on extra permissions granted during the web installation process to move the files around. aiki is totally broken now
On Mon, Oct 24, 2011 at 11:35 AM, Roger Martín <[email protected]> wrote: > Hi people: > > I add a first beta (IT DOESN'T WORK), to evaluate new installer. In brief: > - install process via web is similar to like wordpress, joomla, and drupal > installation, ideal for hosting installation where you have only ftp access. > - Installer is a aiki independent apps. It's must called as > aiki/assets/installer/installer.php. It's not required Aiki runing. > - installer first check if no previous config.php file exists (security > reason) and if necessary files exists (sql, config template, htaccess.ing) > - process have 4 step: > 1) ask for setting. In this step, user can test connection. > 2) create database, and insert sql. > 3) create config.php. If can't, aiki display the file-dump, and some > button for retry. > 4) create htaccess.php > > Step 3 and 4 are created because sometimes user must copy-paste the file. > > > WHY IT DOESN'T WORK > --------------------------------------- > 1) aiki bootstrap detect RUN-TIME installation. > (see line 64 bootstrap.php) > -> solution: Web and run-time installation must detect the same file: > config.php > > 2) run-time insert some variables that are not available in web > installation: > *VERSION. REVISION, AUTHORS* > * AIKI_LOG_DIR, AIKI_LOG_FILE,AIKI_LOG_PROFILE, AIKI_LOG_LEVEL; > > Solution: > for log: a installer must assumed there are not log configuration, or use > a default log configuration. > for version, revision and authors -> create a separated file (for example > /configs/aiki_data.txt) > > > 3) Aike needs a run-time installation to: > - move certain files ( third-party libraries) > - insert same values in files (configs/config.php) and i think some > javascript too. > > Solution: > - move all files to src directory. > - no runtime-insertions. > Gains? > - a complete web based installer: a webmaster only need copy src directory > to make a installation (similar to wordpress, joomla, drupal...etc) > - easy to maintain: we only need zipped all src files..and voila..a aiki > web package. > - easy to develop: > old installer? > - will do his work: Copy files in adequate directory ( /usr/share/aiki), > must create apache2/site-enables/aiki file, desktop links.. > - doesn't need create the database. So it can work automatically like 99% > of debian packages. > > > 4) TODO > are we agree with new installation? > > other: > - use ezSQL (i'm working on it) > > > > roger > > PD: > how must i generate Makefile.in > > > > > > > > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~aikiframework-devel > Post to : [email protected] > Unsubscribe : https://launchpad.net/~aikiframework-devel > More help : https://help.launchpad.net/ListHelp > > -- Bassel Safadi http://bassel.ws Global +1 323-545-3855 Skype i.know.sy
_______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
