savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] submission of stac - deployment/provision framework


From: toni
Subject: [Savannah-hackers] submission of stac - deployment/provision framework - savannah.nongnu.org
Date: Tue, 22 Apr 2003 04:19:45 -0400
User-agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U; ) Gecko/20020623 Debian/1.2.5-0.woody.1

A package was submitted to savannah.nongnu.org
This mail was sent to address@hidden, address@hidden


Toni Prug <address@hidden> described the package as follows:
License: gpl
Other License: 
Package: stac - deployment/provision framework
System name: stac
Type: non-GNU

Description:
On Gnu/Linux and Unix platforms, we have a set of established
packaging systems (apt, rpm, bsd ports etc). However they all address
the issue of automated application provision (install -> configure)
specificaly for Operating Systems. What\'s missing is a tool that
performs simillar functionality, but aimed at web applications. Which
is precisely the intention behind the development of Stac. It is an
application deployment framework, built to automate provision of
applications, specificaly web applications.  It is designed to deploy
and manage multiple instances of a web application. It also keeps the
record of end users of the applications that it deploys. See more at
http://www.openmute.org/view/Open/StAc. Alpha tarball is at 
http://openmute.org/twiki/pub/Open/StAcMakefile/stac-0.3.2.tar.gz

By provision i mean: to INSTALL, CONFIGURE, ACTIVATE and TEST an instance of 
software web tool/application. For example, here\'s the paragraph from stac man 
page that explains provision of a tool, well, part of it for now: installation 
and configuration.

task: provide twiki

   % stac -g install -t twiki -p \"Bow Arts\" -U bowarts
          --admin address@hidden -d bowarts.openmute.org

    1. creates new project (-p), unless project already exists
    2. creates new authentication user (-U) for that project
    3. gets tool (-t) code from cvs server, twiki in this case
    4. configures tool files with end_user data
    5. creates virtual_host file, for inclusion in main apache one

    To make tool live, we need the supplied domain to resolve.
    Include link to the virtual_host file in apache configuration and
    restart apache (check the apache config syntax first).  That\'s it,
    tool install is live. This will be automated further later, with
    no manual step left to perform, apart from issuing a single
    command line.

Stac stores its data about projects and end users (users using provided web 
applications, working on projects stac deploys) in XML. It gets the source for 
applications from CVS, although there will be other method added as well, 
probably the ablility to use a tarball.

Other Software Required:


Other Comments:






reply via email to

[Prev in Thread] Current Thread [Next in Thread]