Rapache

Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2008-05-29 23:30:42
Size: 2688
Editor: 213-156-52-112
Comment:
Revision 11 as of 2010-05-21 13:35:05
Size: 1238
Editor: 151
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Rapache =
Rapache
is a simple tool for remotely managing and configuring an apache2 (bla bla bla)
http
s://edge.launchpad.net/rapache/
 
Links:
[http://launchpad.net/rapache]
'''[[http://launchpad.net/rapache|Rapache]]''' is a simple tool for remotely managing and configuring an apache2 server.
Line 8: Line 3:
{{{ _________________________________________
/ This Rapache has super cow powers \
\ In fact is an eagle-cow /
 -----------------------------------------
        \ ^__^
         \ (oo)\_______
            (__)\ )\/\
                ||----w |
                || ||}}}
If you need a simpler software just to start/stop apache2 and mysql, check [[https://launchpad.net/localhost-indicator|localhost-indicator]]
Line 18: Line 5:
== Links ==
Currently we don't have a dedicated website.
 * Project page, code and bugs on launchpad: http://launchpad.net/rapache
 * Developer website: http://www.stefanoforenza.com/category/rapache/
Line 20: Line 11:
What do we miss ?
 * Wiki page
 * A first bzr push. This will happen just after code refactory-
 * There are many different branch developments.
Line 25: Line 14:
Version 0.7:
 * Fix the freeze bug and make rapache work on Ubuntu 10.04
Line 26: Line 17:
=== Stage 0 ===
We will ship a little working demo as proof of concept and base of future work.

We will (in order):
 * Implement existing Vhosts editing. This will likely parse only rapache-created vhosts at first (refactoring. mini-parser implementation)
 * Code refactoring and QA: Class and Python Packages Naming.
 * First BZR push (Yay !)
 * We should backup /etc/apache2 and /etc/hosts in ~/.rapache since this is still alphish software and we don't like people curses :)
 * Not everyone follows the right procedure for vhost creation and just create a *.conf in sites-enabled. We should note that and offer the user to normalize the situation
 * Define complete software interface (comprising future features), leaving invisible not yet implemented parts.
 * First bugs to be dealt with
   * Cancelling an operation when asked for root password should stop the entire procedure.
 * Code QA.
Notes:
 * Demo will work only on localhost (so only useful for test/dev websites)


=== stage 1 ===
 * Apache (mostly) complete config
 * Sniff installed package and offer user to install what it's needed to perform the requested action.
 * Simple configuration wizards for common apps
 * QA number 2

* Stage 2 *
Version 0.8:
Line 53: Line 21:
 * PackageKit ?  * Policykit ?
Line 58: Line 26:
Line 62: Line 29:


== Packages ==

- rapache (meta-package)
  -depends: rapache-core, rapache-gtk
  
- rapache-core (python classes, bash python scripts)
  -depends: nothing :).
  
- rapache-gtk (GUI)
  -depends: rapache-core

Rapache is a simple tool for remotely managing and configuring an apache2 server.

If you need a simpler software just to start/stop apache2 and mysql, check localhost-indicator

Currently we don't have a dedicated website.

Development environment

  • There are many different branch developments.

ROAD MAP

Version 0.7:

  • Fix the freeze bug and make rapache work on Ubuntu 10.04

Version 0.8:

  • Connect SSH servers to configure remote apaches
  • bookmark SSH servers
  • Avahi ? Smile :)

  • Policykit ?
    • maybe not, we can't use that on ssh servers.
    • how to get root privileges via ssh ? Not every server allow remote root login (ubuntu's for example ;-))
  • QA 3

Use cases

  • Tony is a webdesigner. He don't want to mess with apache, he wants to get started customizing wordpress themes on localhost.
  • Ralph is a small company's webmaster. Since he has lot of stuff to get done, he don't want to loose time configuring apache via commandline

Rapache (last edited 2010-06-01 13:30:11 by alfred-maghi)