Difference between revisions of "Documentation Team/Obsolete/Services Binary-less Services HOWTO"

From Sugar Labs
Jump to navigation Jump to search
(work on English)
Line 4: Line 4:
 
</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 local initial service.info by invoking ''0sugar init'', tweak newly created ''service/service.info'' file
+
* Create a local, initial service.info file by invoking ''0sugar init'', then tweak the newly created ''service/service.info'' file.
* increase/change version field in ''service.info'' file
+
* Increase/change the version field in the ''service.info'' file.
* ''0sugar dist'' to change local feed in ''dist/'' and place there tarball
+
* 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>see [[#Release workflows]] for other release scenarios
+
* Run ''0sugar push stable'' to rsync changed files from ''dist/'' to the server.<br>See [[#Release workflows]] for other release scenarios.

Revision as of 23:38, 6 March 2010


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.
  • Execute 0sugar dist to change the local feed in dist/ and place the tarball there.
  • Run 0sugar push stable to rsync changed files from dist/ to the server.
    See #Release workflows for other release scenarios.