Thanks for the response, but this assumes that we always upgrade to the
latest version of XWiki. I am not planning on upgrading regularly, so I
don't want to see documentation advance ahead of my current installation
version of XWiki. I therefore am hoping to 'freeze' the documentation by
taking a
Hi,
** Not sure if i'm posting this in correct place, as this is my 1st post. **
I have installed GlassFish v 3.1.2.2 + MySQL 5.6 +
Xwiki-enterprise-web-5.0.war
Not sure if I’m using the correct Java container and DB...
I will be using Xwiki with large DB.
Have i choose the correct Container and
Recommendations about DB Container depend on Your scenario of XWiki using
... For example, if you will have many and large attachments - need to
switch XWiki to file-system attachments storage or to use another database
(not MySQL) - this is my opinion.
My experience with big attachments - from
Thanks for the reply Jeremie, but my question still stands. Regardless of
continuous improvements to documentation, it would be useful to have a
frozen in time version of the documentation to compliment my current
deployed version. I can then be confident that my documentation is correct
for my
Hirji,
Running MySQL is good enough I feel.
Using Jetty makes it very easy to start just xwiki because of the packaging.
Otherwise, using other servlet containers should work.
Many have been using tomcat.
We, at curriki, employ the Sun Java Application Server, which is a version
earlier than
Thanks,
Which Servlet Container should I be using?
My DB will have large attachments and images.
Regards,
H
-Original Message-
From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On Behalf
Of Eugen Colesnicov
Sent: 20 March 2013 13:46
To: users@xwiki.org
Subject: Re:
You didn't tell us if this wiki will be in production (ie, available to
many users, requiring to be up most of the time, with proper backup of
data, etc...) or if it's only a test wiki for you, for example.
If it's only for tests, the standalone wiki with jetty + hsqldb is good
enough, for
Hi,
At the moment the safest way to go is Tomcat + MySQL. If you go with
Tomcat, make sure you set it to use UTF8 encoding, since the default
configuration of Tomcat is not UTF8.
The standalone jetty+hsqldb is not good in production/large wikis because
it uses an in memory hsqldb database,
Thank you for helping me out here.
Xwiki will be in production with large files.
15000 Pages... that's a lot of pages... ours will be much less then
that.
So Tomcat sounds good, but dot sure what you mean by filesystem
attachments? How does that work or can that be done at later stage with
Hi,
Just installed Tomcat + Xwiki using link below, but it does not tell me
to install MySQL? Its telling me to install Nginx, should I be doing
this?
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationTomcat#H
InstallationSteps
This is what I have done so far...
Windows 2008
You should follow
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationWAR
http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationTomcat
is just one step
On Wed, Mar 20, 2013 at 6:16 PM, Hirji Patel hirji.pa...@akt-uk.com wrote:
Hi,
Just installed Tomcat + Xwiki using link
Hi Jeremie,
We have started moving functional tests from xwiki-enterprise to
xwiki-platform so that they are grouped by functional domain. Thus
xwiki-enterprise-test-ui is not the best example. You should take a
look at the platform modules that have functional tests:
it worked! Great! Thank indeed! Please, read below...
From: users-boun...@xwiki.org [users-boun...@xwiki.org] On Behalf Of Marius
Dumitru Florea [mariusdumitru.flo...@xwiki.com]
Sent: 19 March 2013 08:23
To: XWiki Users
Subject: Re: [xwiki-users]
13 matches
Mail list logo
