Skip to content

Commit

Permalink
Update page.md
Browse files Browse the repository at this point in the history
Remove non-sense link
  • Loading branch information
robmarzialetti authored Apr 19, 2024
1 parent 7fb390e commit e3df7b4
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Example Usage (RedHat/CentOS):

If you change the Lucee to something other then the ROOT user, you need to configure your sites to allow write access from whatever the Lucee user is. This will allow Lucee/Tomcat to write the WEB-INF files to that directory. If you don't want the Lucee/Tomcat user to have write access to your site directory, you'll need to create the WEB-INF directory yourself and at least provide write access to that WEB-INF directory.

To show how this is done, let's use the "apache" user again, like we did above. If our site directory is /home/admin/[www.sitename.com](http://www.sitename.com/)/, we'll need to create the directory and assign permissions to it so that the "apache" user can write to it. We can do that with this command:
To show how this is done, let's use the "apache" user again, like we did above. If our site directory is /home/admin/www.sitename.com/, we'll need to create the directory and assign permissions to it so that the "apache" user can write to it. We can do that with this command:

Example Usage (Debian/Ubuntu/Mint):

Expand All @@ -44,4 +44,4 @@ Example Usage (Debian/Ubuntu/Mint):

Do that for each site you've configured in your tomcat server.xml file. After you've got a WEB-INF directory in every site with permissions adjusted on each of them, don't forget to restart Lucee/Tomcat!

$ sudo /opt/lucee/lucee_ctl restart
$ sudo /opt/lucee/lucee_ctl restart

0 comments on commit e3df7b4

Please sign in to comment.