Akelos Framework v1 forum archive. This forum is no longer maintained. To report bugs please visit https://github.com/akelos/akelos/issues
    • CommentAuthoralake
     

    This is a hint for using batch files. I'm using Linux (Fedora 7), but I'm sure that this technique can be adapted for other operating systems. My home directory is /home/alan. I've created /home/alan/bin. ("bin" is a name that's used in various places as a name for directories that hold binary (executable) files. I've added /home/alan/bin to my path in my .bash_profile file, so that executable files in this directory can be found by keying in the file name from anywhere in /home/alan. I have two Akelos related files in here. If you use them, they must be customized to reflect where your stuff is.

    The first file is called "akelos_upgrade":

    svn co http://svn.akelos.org/trunk/ ~/develop/Software/akelos
    chmod -R g+w ~/develop/Software/akelos
    ln -s  ~/develop/Software/akelos/public ~/www/html/akelos
    

    /home/alan/develop/Software/akelos, in the first line, is where I store akelos.
    /home/alan/www/html, in the second line is the document root of a virtual server.

    Notes: "~/" is shorthand for one's home directory, in my case "/home/alan". The link statement refers to akelos/public. In another forum, I saw the instruction to leave the "public" off and just link to "akelos". It appears to make no difference. I got the "Welcome Aboard" with both links.

    The second file is php_project.php:

    #!/usr/bin/php
    <?php
    exec('develop/Software/akelos/script/setup -d ~/develop/php/'.$argv[1].' -p ~/www/html/'.$argv[1]);
    exec('chmod -R g+w ~/develop/php/'.$argv[1]);
    ?>
    

    This could have been written as a shell script, but I'm lazy. I already know how to pass arguments to a php script. Of course, it has the same directories as the first script.

    •  
      CommentAuthorbermi
     

    Alan,

    The link statement refers to akelos/public. In another forum, I saw the instruction to leave the "public" off 
    and just link to "akelos". It appears to make no difference. I got the "Welcome Aboard" with both links.
    

    I have to discourage the use of linking to "/akelos/" directly as this approach exposes your app/, script/, config/... to direct requests by malicious users pointing their browsers to those public paths.

    Whenever is possible you should only expose the "akelos/public/" directory. If you need to redistribute your app for running at an account without shell access you can redefine the include paths and put everything in a includes dir which you can latter protect using htaccess rules