antville/helma
antville/helma
1
1
Fork 0
Code Issues 5 Pull requests 7 Projects Releases 5 Activity Actions
Antville’s Fork of Helma Object Publisher https://helma.js.org
46 commits 10 branches 49 tags 53 MiB
Java 38.9%
HTML 35.3%
JavaScript 23%
Perl 2.4%
XSLT 0.1%
Other 0.1%
Find a file
stefanp 7bd5803a33 simplified editing of server authentication. 
as changes to server.properties are now immediately read and accessible
from the manage-application we just have a md5-encoding utility and leave
it to the admin to add the values to the server.properties file. this makes
sure that nothing can be changed via the web.

changes to allowadmin are effective immediately too.
2002-11-22 11:58:37 +00:00
Application lots of formatting fixes, 2002-11-22 11:39:11 +00:00
DocApplication re-added access check to actions 2002-11-22 11:55:42 +00:00
DocFunction re-added access check to actions 2002-11-22 11:55:42 +00:00
DocPrototype re-added access check to actions 2002-11-22 11:55:42 +00:00
DocTag major overhaul of the manage app's api-documentation functions. 2002-11-21 18:36:03 +00:00
Global simplified editing of server authentication. 2002-11-22 11:58:37 +00:00
Root simplified editing of server authentication. 2002-11-22 11:58:37 +00:00
app.properties made some decent rearrangements 2002-10-04 15:43:37 +00:00
class.properties make app work again with new way of retrieving a custom root object (helma.main.Server, that is) 2002-04-08 08:49:41 +00:00
readme.txt updated to fit the last changes 2002-04-24 16:04:29 +00:00

readme.txt 

To get the manage-application to work you must:

 - add it to the apps.properties file with the following line:

     manage

 - use snapshot 20020326 or later.

 - add the following properties to server.properties:
 
   allowAdmin=[comma-separated list of hosts or ip-addresses that
               are allowed to access this application, wildcards
               are only allowed in addresses, not in hostnames]
   adminUsername=<md5-encoded username>
   adminPassword=<md5-encoded password>
   
   MD5-encoding can be done - once you've got the application
   up and running - on the web:

     http://<your-server-name>/manage/makekey
     http://<your-server-name>/base/makekey

   or you can use a shell-tool integrated in helma:
     java -classpath helma.jar helma.util.MD5Encoder <username> <password>