ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

I'm am thinking of making a codeigniter interface is this practical or impractical before I commit to building it

March 03, 2008 2:23pm

Subscribe [2]
  • #1 / Mar 03, 2008 2:23pm

    Sally D

    129 posts

    I’m thinking of making a script that will unpack all the files and set any configuration files all at once

    like a php script that will install and configure codeigniter at once. The programm will also have web interface that will alow you to edit the core codeigniter files from a web interface. Like I can click a link then it will open that file all from a web inter face with tool tips to help my remember the codes all most like a cheat cheat built into the web interface to make it easier for me to remember the codes while your programming something.

    I would like php to extract all the files and then write any configuration files at the moment of inception so I don’t have to open any files to edit anything.

    just click install and configure that’s it.  So I can up load only one file to my server then it will unpack the rest configure any files I need configured it will set there permissions to. It will then create a web interface using ajax and php to edit these files with tool tips to help me remember the codes as I am editing them.

    Is this worth while would it make it easier to work with CI

  • #2 / Mar 03, 2008 2:55pm

    Leggy

    25 posts

    Hmm, it is a nice idea but there are two things, what type of extracting (zip)? and CodeIgniter is extremely simple on it’s own to install, this would just add something else to do on it.

    On the other hand, you could do this for a piece of software you made in CI, where you upload a the systems folder, index.php. The installer could be a controller so it is able to use all of CI’s features. In the default controller you could check if installer has been run if not redirect them. Then in the installer edit all the files, etc; then it could remove itself and remove the bit in the default controller which checks for the installer (optional).

    Either way a universal installer system would be nice, then developers could build on if for their app’s.

  • #3 / Mar 03, 2008 3:09pm

    Michael Wales

    2070 posts

    I use SVN for this. I keep a folder constantly up-to-date with the current CI rev, I then export/merge this with another repository I use for all of my personal libraries/helpers I use on virtually every install.

    When I want to start a new application - I just export that final repository to the root and whip through the config really quick (it takes no more than 20 seconds, once you get really good at it, lol).

  • #4 / Mar 03, 2008 4:47pm

    adamp1

    772 posts

    Personally it seems a bit OTT, I mean CI is very simple to setup and for the basic install all you need to change is some lines in config.php and database.php and your done.

    As Michael said use SVN then you can just merge copies with your default files and export it.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases