3,789
edits
Changes
From Amahi Wiki
no edit summary
Packaging applications is through a simple web form in the contributor's area of amahi.org.
Here is a ''really old'' 10-page Powerpoint presentation [[:File:Packaging-Applications-for-OneClick-Installation.ppt|HOWTO package an application]] (PPT) <!--([["File:Packaging-Applications-for-OneClick-Installation.pdf|PDF]])-->.
The fields in the application's form are listed below with their descriptions:
Official name for the application. This is the name the user sees for the application. It must be unique (no repeats). Make sure the capitalization is the official capitalization of the original application. Examples: WordPress, Zina, Gallery, MediaWiki...
=App Home Page == The URL to the app's home page, if it has one. Otherwise you can leave it blank. =Version/Release====
Version number for this app. Please specify like this: 7.5, 2.3.4, 0.1, etc. and align the version numbering with the source application being packaged.
It should have transparent background (for best integration in all themes).
Valid formats are png (much recommended), jpg, png and gif. The best logos are well centered with the logo covering most of the image and transparent background. They must be uploaded in the Amahi wiki and referenced in the app. Please do not reference images from other sites. If you need a quick image editor, you can use the free online image editor [http://aviary.com/apps/flash/aviary/index.aspx?tid=1&Phoenix Phoenix], by Aviary.
Best resolution for the screenshot is 320x240px or multiples thereof.
Valid formats are png, jpg and gif. It should have transparent background (for must not be blurry. '''Most times it's best integration to zoom in all themes)as much as possible to a representative area of the screen, not the whole screen of the app.''' They must be uploaded in the Amahi wiki and referenced in the app. Please do not reference images from other sites. Valid formats are jpgIf you need a quick image editor, you can use the free online image editor [http://aviary.com/apps/flash/aviary/index.aspx?tid=1&Phoenix Phoenix], png and gifby Aviary.
URL for a tar.gz/tgz or zip file containing the source of the app.
The source tar.gz/tgz or zip file must expand into a single directory to be supported.
You can leave this and the SHA1 fields blank if the app is RPM based.
Users will also be able to type blog in the address bar of browsers to reach the app. If this name is not available, a subsequent name will be picked, e.g. blog1.
====RPM(s)===Package =This field is a list, the name of the RPM package for the application, *preceded* by any other required RPMs (space-separated or comma-separated). These will be installed via yum in one install command. Note, however, If this name is different per distro that for reliability reasonsAmahi is supported on, only it may be discerned per the main (last) RPM will be removed upon un-install[[Package naming conventions]].
=Package Dependencies ==This field is a space-separated list, the name of any other required packages (space-separated). If this list of names is different per distro that Amahi is supported on, it may be discerned per the [[Package naming conventions]]. These will be installed via yum/apt-get in one install command. Note, however, that for reliability reasons, these will not be removed upon un-install. =Custom Webapp Options ====
This field, if filled, allows you to add custom options to this application,
'''if this app has an associated webapp.''' The values you enter here will be but in a .htaccess file.
=App Database ===Kind of application====Kind of application (underlying technology): PHP, Python, RoR, Perl, Plain HTML, ...
This field should contain the name of the database for this app, if any. MySQL is used by default. A corresponding user by the same name is created. The password for the user is also the database name. IMPORTANT: BOTH user and database are created at app install time and ARE DROPPED when the app is uninstalled =Kind of application ==Kind of application. Must be one of: php, theme, ror, ... or leave blank (this selects form a pattern of virtual host templates and needs to be more documented) =App home page URL====
Type the URL for the home page or the main site for this application, e.g. http://wordpress.org
Any tags you want for this app. Useful for search and categories for this application. Better to have more tags at this stage.
This field should contain a description of the application in a single paragraph with a sentence or more in it. Ideally, the first sentence should contain an good description within the first 70 characters of this field. You can include some very limited HTML. Links should include a target="_" in it.
This field should contain a full description of the app in several paragraphs. It will be positioned after the short description and should be a follow-through of it. You can include some limite HTML. Links should include a target="_" in it.
= App Dependencies =
= Troubleshooting =
NOTE: The application installer logs install process information in your HDA at:
So please check that log file for exceptions or other errors if your application fails to install!
= Releasing =
As soon as you are happy with how the app is installed please contact the core team support at team at amahi.org or in the IRC channel to review . At this stage the basic packaging is complete. You can add other users to the app as contributors to help with the app and release! Return to the details on how to be an [[Application Contributor]]
