PLDWWW: Docs/Webapps

[grizz]

Author: grizz   Date: Mon Aug  4 14:44:03 2008 GMT
Module: PLDWWW   URL: http://pld-linux.org/Docs/Webapps?action=diff&rev2=8&rev1=7
---- Log message:
typo

---- Page affected: Docs/Webapps

---- Diffs:

================================================================
The comment on the change is:
typo

  ## page was renamed from Documentation/Webapps
- why webapps is better than apache_config_* macros
+ = Why webapps is better than apache_config_* macros =
  
- 1. unified structure. all configs are in /etc/webapps/$webapp
+ == 1. Unified structure. All configs are in /etc/webapps/$webapp ==
- admin is not confused, where's the config for app foo
+ Admin is not confused, where's the config for app foo.
  
- 2. simplier
+ == 2. Simplier ==
- no fancy rpm macro options, due layout being unified in front
+ No fancy rpm macro options, due layout being unified in front.
  
- 3. can have multiple webapps configuration per .spec
+ == 3. Can have multiple webapps configuration per .spec ==
- the limitation is because symlink used is %{name} which you can't override in
+ The limitation is because symlink used is %{name} which you can't override in
- spec. this is not hard to overcome, but it still exists.
+ spec. This is not hard to overcome, but it still exists.
  
- in other words You can easily manage multiple instances of a given webapp,
+ In other words You can easily manage multiple instances of a given webapp,
  by simply adding another link to.
  
- 4. no confusing numbers
+ == 4. No confusing numbers ==
  Using config load order is not needed anymore. Order in
  which webapps are loaded does not matter.
  
- 5. there's cli
+ == 5. there's cli ==
- There's a cli program called 'webapp' which you can use to view add and remove webapp links
+ There's a cli program called 'webapp' which you can use to view add and remove webapp links.
  
- 6. separate apache configs
+ == 6. Separate apache configs ==
- apache 1.3 and apache 2.x can have different configs, so you can create
+ Apache 1.3 and apache 2.x can have different configs, so you can create
- different setup for different vhosts. this is not actually a limitation.
+ different setup for different vhosts. This is not actually a limitation.
  
- 7. free for other webservers
+ == 7. Free for other webservers ==
- it is open to add any webserver. lighttpd has hooks but nobody has made any
+ It is open to add any webserver. lighttpd has hooks but nobody has made any
  config.
  
- 8. you can have "modules"
+ == 8. You can have "modules" ==
- you can have a webapp to have subwebapp. say horde is the main package, and
+ You can have a webapp to have subwebapp. Say horde is the main package, and
- horde/imp is horde module. then the webapp name for horde-imp is "horde/imp".
+ horde/imp is horde module. Then the webapp name for horde-imp is "horde/imp".
- the way the config symlinks are created module webapp configs are loaded before
+ The way the config symlinks are created module webapp configs are loaded before
- master. this allows you define /horde alias in main application and /horde/imp
+ master. This allows you define /horde alias in main application and /horde/imp
- in sub application. it's transparent, you don't even have to think about that.
+ in sub application. It's transparent, you don't even have to think about that.
  
  {{{
  # ls -log /etc/httpd/webapps.d/drupal*.conf
@@ -44, +44 @@

  lrwxrwxrwx  /etc/httpd/webapps.d/drupal.conf -> ../../../etc/webapps/drupal/httpd.conf
  }}}
  
- 9. webapps do not have to be rpm packages
+ == 9. Webapps do not have to be rpm packages ==
- in case you have application that's not rpm package, you can achieve similiar
+ In case you have application that's not rpm package, you can achieve similiar
- effect. as the program to register is available outside rpm macros.
+ effect. As the program to register is available outside rpm macros.
- ----
- CategoryUpdateNeeded