[
https://issues.jboss.org/browse/WFLY-695?page=com.atlassian.jira.plugin.s...
]
Scott McLaughlin commented on WFLY-695:
---------------------------------------
Just cleaning out the deployments and the content repo does not seem like it would be
going far enough. I am having trouble understanding the use case here. This is the use
case that made me think about another way so that i did not have to worry about this
problem. what I did was to separate the JBoss distribution from the server and domain
configurations.
for example
/usr/local/jboss/jboss-<version> for the distribution directory (unzip , untar,
...)
/usr/local/jbconfig/<app-name> This is the folder that contains the server config ,
domain config
This design has allowed me to support more than 50 separate applications using one JBoss
Dist (with no changes)
I am happy to share this setup but I am not sure if this is the correct place seems better
as a wiki article
make-pristine.sh to reset an AS installation to factory settings
----------------------------------------------------------------
Key: WFLY-695
URL:
https://issues.jboss.org/browse/WFLY-695
Project: WildFly
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Scripts
Reporter: Bob McWhirter
Fix For: Awaiting Volunteers
Not sure how this is better than unzip -q jboss-as-bin.zip, but being able to
"reset" the domain and such (and bootstrap logging props) to out-of-the-box
settings might be nice.
Perhaps a separate script to clean the deployments and content repo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira