INSTALL

changeset 254
55ca6cafc3dd
parent 221
33d7833ca54c
child 262
c357c4e69b9e
     1.1 --- a/INSTALL	Tue Nov 01 21:31:15 2022 +0100
     1.2 +++ b/INSTALL	Wed Dec 28 13:21:30 2022 +0100
     1.3 @@ -19,29 +19,19 @@
     1.4  3. Configure a data source in your application servlet or servlet container
     1.5  
     1.6  You may use absolutely anything: Tomcat, TomEE, Glassfish, Payara, you name it.
     1.7 +If it supports Servlet 6.0, JSP 3.1, and EL 5.0, you are good to go.
     1.8  Just make sure to configure a data source with the name jdbc/lightpit/app.
     1.9  If you want another name, you can configure the JNDI resource in the
    1.10  WEB-INF/web.xml and META-INF/context.xml files. It is highly recommended to use
    1.11  the lightpit_app user which has less privileges to create the data source and
    1.12  leave the lightpit_dbo user for the database operator.
    1.13  
    1.14 -4. Make sure JDBC driver and JSTL libraries are available
    1.15 -
    1.16 -This step may be optional depending on the container you are using. Most
    1.17 -application servers already have JSTL libraries installed. More basic servlet
    1.18 -containers like Tomcat don't. In that case you have to put the libraries of the
    1.19 -javax.servlet:jstl:1.2 artifact manually into the library dir of your servlet
    1.20 -container (jstl-1.2.jar and jstl-impl-1.2.jar).
    1.21 -
    1.22 -In most cases you also have to put the postgresql JDBC driver into the library
    1.23 -directory of your server (e.g. postgres-42.x.x.jar).
    1.24 -
    1.25 -5. Deploy the WAR file of lightpit
    1.26 +4. Deploy the WAR file of lightpit
    1.27  
    1.28  This is the most straight forward step. Just deploy the WAR file as you usually
    1.29  do in your application server.
    1.30  
    1.31 -6. Configuring a web server and authentication
    1.32 +5. Configuring a web server and authentication
    1.33  
    1.34  LightPIT can optionally detect the authenticated user. You may freely decide
    1.35  whether to enable authentication in your application server or put a web server

mercurial