Changes between Version 11 and Version 12 of ModuleInstall

Show
Ignore:
Author:
mickecarlsson (IP: 81.227.49.131)
Timestamp:
04/22/11 15:35:02 (2 years ago)
Comment:

Removed sourceforge obsolete links

Legend:

Unmodified
Added
Removed
Modified

  • ModuleInstall

    v11 v12  
    44 
    55 * Module releases (.tgz files) 
    6    * https://svn.sourceforge.net/svnroot/amportal/modules/release/2.x/filename.tgz 
     6   * http://svn.freepbx.org/modules/release/ 
    77 * Module ''stable'' code 
    8    * https://svn.sourceforge.net/svnroot/amportal/modules/branches/2.x/ 
    9  * Module ''development'' code 
    10    * https://svn.sourceforge.net/svnroot/amportal/modules/trunk/ 
     8   * http://svn.freepbx.org/modules/branches/ 
    119 
    1210== How does the Online Module admin know about available modules? == 
    1311 
    14 Good question!  A modules-X.X.xml file is generated for each released (stable) version of FreePBX.  This is done by collecting all the module.xml info from the ''stable'' module code branches @  https://svn.sourceforge.net/svnroot/amportal/modules/branches/2.x/.  The resulting modules-X.X files are available at http://amportal.sourceforge.net/ 
     12Good question!  A modules-X.X.xml file is generated for each released (stable) version of FreePBX.  This is done by collecting all the module.xml info from the ''stable'' module code branches. 
    1513 
    1614The Online Module admin, reads these files and compares what's available with what is installed locally.  From this it can determine if a module is installed, not installed, or needs an upgrade. 
    3230   * Module.xml files define whether official or unofficial, where unofficial modules have only seen limited testing .. no support from the core freepbx team. 
    3331   * php xml stuff http://au3.php.net/manual/en/ref.xml.php 
    34    * [http://svn.sourceforge.net/viewcvs.cgi/amportal/modules/trunk/modules.xml?view=markup&rev=1278|Master modules.xml sample] 
    35  * HTTP access to SVN is used for downloading modules 
     32   * HTTP access to SVN is used for downloading modules 
    3633   * modules/release/2.x/modulename-rev.tar​.gz 
    3734   * modules/devel/modulename/page.modu​lename.php 
    4441 
    4542I've got a svn checkout of the modules as /usr/src/freepbx-modules 
    46  * svn co https://svn.sourceforge.net/svnroot/amportal/modules /usr/src/freepbx-modules 
     43 * svn co http://svn.freepbx.org/modules/branches /usr/src/freepbx-modules 
    4744In the 2.1 and 2.2 directories there's a publish.pl script that creates the tar.gz file, updates the md5 and location in the xml, and publishes them both. So lets say you've made a change to module foo.  
    4845 * save and commit your changes 
    5148   * ./publish.pl foo 
    5249This generates foo-versionname.tar.gz, sticks it in ../../release (this is why you need a complete checkout of the entire modules tree) updates the xml file with the new location and md5sum, and publishes both 
    53 You also need to run ./mod.php on shell.sourceforge.net (in /home/groups/a/am/amportal) to update the online xml file, but this should be run automatically - something for ryan to fix. 
     50You also need to run ~~./mod.php on shell.sourceforge.net~~ (in /home/groups/a/am/amportal) to update the online xml file, but this should be run automatically - something for ryan to fix. 
    5451  ''RC: Runs once an hour via cron'' 
    5552