Difference between revisions of "Documentation Team/Obsolete/Services Binary-less Services HOWTO"
Jump to navigation
Jump to search
(Created page with '<noinclude> {{TOCright}} Category:Activity Team </noinclude> Work flow for services that don't require compilation stage thus could be just packaged and used as is on server…') |
|||
(5 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
+ | {{Obsolete | Was only draft content.}} | ||
+ | |||
<noinclude> | <noinclude> | ||
{{TOCright}} | {{TOCright}} | ||
− | [[Category: | + | [[Category:Services/Documentation]] |
</noinclude> | </noinclude> | ||
− | Work flow for services that don't require compilation stage thus could be just packaged and used as is on server side: | + | Work flow for services that don't require a compilation stage, thus, they could be just packaged and used as is on server side: |
− | * | + | * Create a local, initial service.info file by invoking ''0sugar init'', then tweak the newly created ''service/service.info'' file. |
− | * | + | * Increase/change the version field in the ''service.info'' file. |
− | * ''0sugar dist'' to change local feed in ''dist/'' and place there | + | * Execute ''0sugar dist'' to change the local feed in ''dist/'' and place the tarball there. |
− | * ''0sugar push stable'' to rsync changed files from ''dist/'' to the server<br> | + | * Run ''0sugar push stable'' to rsync changed files from ''dist/'' to the server.<br>See [[#Release workflows]] for other release scenarios. |
Latest revision as of 13:39, 25 November 2010
|