Jump to content

Set location of "360Works Log" directory


This topic is 4359 days old. Please don't post here. Open a new topic instead.

Recommended Posts

This is not customizable with SuperContainer, but if you use one of the other deployment methods it will write logs to a different location.

When you run SuperContainer in stand-alone mode it is run as the logged-in user, and so logs are written to your Documents folder because it's the most likely place for you to have write permission and needs to be available immediately the first time you launch SuperContainer. If you deploy SuperContainer with FileMaker server using installer.jar rather than running supercontainerserver.jar (stand-alone deployment) or if you deploy supercontainer with a Tomcat deployment logs will be written to a different location.

Link to comment
Share on other sites

  • Newbies

This is not customizable with SuperContainer, but if you use one of the other deployment methods it will write logs to a different location.

Thanks, understood.

Feature request: I'd still like the location to be configurable please, after the first start-up if neccessary.

SuperContainer standalone is excellent, but it joins far too many of the poorer quality Windows software products in forcibly creating a top-level folder of it's own in My Documents, cluttering it up, rather than asking the user where. Sorry to be blunt, but that's the message that this type of software behaviour gives.

Link to comment
Share on other sites

This topic is 4359 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.