[jira] Created: (GEOS-484) document a 'production best practices'

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (GEOS-484) document a 'production best practices'

JIRA jira@codehaus.org
document a 'production best practices'
--------------------------------------

         Key: GEOS-484
         URL: http://jira.codehaus.org/browse/GEOS-484
     Project: GeoServer
        Type: Sub-task
  Components: Configuration  
    Versions: 1.3.0 RC6    
    Reporter: Chris Holmes
 Assigned to: Chris Holmes
    Priority: Minor
     Fix For: 1.3.0 RC7


Document at a minimum these four steps:
professor_daveed: hum - so someone setting up a real site would do this:
professor_daveed: 1. have the basic geoserver (ie. all the libs) in a .war
professor_daveed: 2. have a data_dir for all their stuff
professor_daveed: 3. probably delete the demos/ stuff
professor_daveed: 4. have a web-app (or whatever) for their actual site

I think we should make something a bit fuller, recommend using a real servlet container instead of our embedded Jetty, and make sure no one's serving shapefiles on production instances either.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel