I have not used MP4 files on my own server (bandwidth issues) but I have found the EmbedVideo Extension to work well. Implementation details are mostly left to the video service (YouTube, Vimeo, etc). May be worth a look.
Hello!
Does anybody have information about sizing of MediaWiki, i.e. if I have 1000 users per day how much RAM/CPU do I need to run MediaWiki?
Moreover, when I have 10000 users per day, how much RAM/CPU is needed in this case?
And when I have 20000 users per day how much RAM/CPU is needed in this case?
Does anybody knows where to get such information? Any ideas about how to calculate this?
Best regards,
Vasli Slavik
It recently came to my attention that users of my wiki cannot edit/create
their user and talk pages and it's probably been this way for some time and
I didn't realize it til now.
It's using v1.24.4
They have the following permissions.
$wgGroupPermissions['autoconfirmed']['read'] = true;
$wgGroupPermissions['autoconfirmed']['edit'] = true;
$wgGroupPermissions['autoconfirmed']['createpage'] = true;
$wgGroupPermissions['autoconfirmed']['createtalk'] = true;
$wgGroupPermissions['autoconfirmed']['upload'] = true;
$wgGroupPermissions['autoconfirmed']['reupload'] = true;
$wgGroupPermissions['autoconfirmed']['reupload-shared'] = true;
$wgGroupPermissions['autoconfirmed']['move'] = false;
$wgGroupPermissions['autoconfirmed']['minoredit'] = false;
$wgGroupPermissions['autoconfirmed']['createaccount'] = false;
$wgGroupPermissions['autoconfirmed']['editprotected'] = false;
$wgGroupPermissions['autoconfirmed']['editsemiprotected'] = false;
Any thoughts on how to fix this?
Thanks
Adrian
Hi all,
I'm using Cargo with Semantic Forms. The cargo table is defined in one
template and attached in others. Each has it own form as they represent
subtypes. How can I hardcode the subtype so that when I query the cargo
table holding all the subtypes the info is available?
In one of the forms, I tried with
{{{field|SubType|mandatory|default="TypeA"}}}
and it works. However, when I hide it
{{{field|SubType|mandatory|default="TypeA"|hidden}}}
it does not.
Thoughts? Thanks!
Requirements: a simple installer and a one click maintainer for all!
===
Every legacy software reaches a dead end without its adherents noticing.
In the case of Drupal and WordPress, both decided they had to make an
architectural break with the past, with Drupal 8 and WordPress Calypso
respectively.
WordPress has leaped Drupal by implementing a full node.js REST model, but
it had the advantage of the Ghost fork that did this several years ago.
Drupal is a step behind, they decided structured content was more important
and were late to the JSON game. Their Rest is a bit of an add-on layer.
For MW, one possibility is to add a MEAN stack in front for content
delivery. Use angular to develop a fully responsive/adaptive Web
Application.
Use the legacy code for authoring and content management. Add a REST layer
to dump content into Mongo at the front end.
Over time, convert the back end to Javascript.
David
I am trying to install ContentTranslation on our MediaWiki site. I am having trouble getting past the installation where I run the command "npm start" for the cxserver that is needed in partnership with the extension. The process takes hours and never seems to complete, consistently showing variations of the following:
{"name":"mediawiki-contenttranslation.heap.rss","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.rss:62722048","method":"timing","value":62722048,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.rss:62722048","time":"2015-12-17T21:33:38.678Z","v":0}
{"name":"mediawiki-contenttranslation.heap.total","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.total:52044288","method":"timing","value":52044288,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.total:52044288","time":"2015-12-17T21:33:38.679Z","v":0}
{"name":"mediawiki-contenttranslation.heap.used","hostname":"hoplahoma","pid":11219,"level":10,"message":"timing:mediawiki-contenttranslation.heap.used:19116472","method":"timing","value":19116472,"levelPath":"trace/metrics","msg":"timing:mediawiki-contenttranslation.heap.used:19116472","time":"2015-12-17T21:33:38.680Z","v":0}
Do I need to give the process more time? Is there something else I can do to fix the issue? I have yet to get past this step in the installation process setting up the cxserver. We run Mediawiki 1.26, PHP 5.5.9, MySQL 5.5.46. Thank you in advance.
Best,
Andrew
Andrew Geary
SEG Wiki editor
Society of Exploration Geophysicists (SEG)
8801 South Yale, Suite 500 / Tulsa, OK 74137 USA
504-407-1303
ageary(a)seg.org
www.seg.org
As part of T113210 [1], which is a broader discussion on track for the
developer summit, I am hosting two IRC office hours back to back [2] on
December 21st from 20:00 UTC to 22:00 UTC.
The previous office hour [3] focused on ways to reconnect to the shared
hosting community. This time two very different topics will be discussed.
*The open questions in the descriptions below are by no means meant to be
exhaustive, nor are they expected to be fully answered by the end of those
office hours. They are just examples to clarify the context of the titles.*
*Shared hosting technical alternatives*
During the last office hour on the topic of non-technical mediawiki
installs, people seemed very eager to discuss new technical solutions that
could offer a viable alternative to shared hosting.
Could new technologies like containers allow for performance/cost ratios
comparable to shared hosting? If not, how big would the penalty be? How
much maintenance would we have to do to keep deployment on such platforms
up to date?
Shared hosting has always suffered from the fact that it's not used at the
WMF and therefore only maintained on a volunteer basis. How would things be
different with new tech?
*Shared hosting support definition*
Shared hosting usage is already a reality and we should do a better job
accounting for it. Currently mediawiki contributors have no visibility in
what should be supported and to what degree. Our browser support is graded
and very clear, meanwhile our server-side support is not:
https://www.mediawiki.org/wiki/Compatibility
Should we model our server-side compatibility guidelines on the graded
system we have for browsers? If so, what would that look like? How could we
break down "shared hosting support" into more discreet server-side
capabilities?
[1] https://phabricator.wikimedia.org/T113210
[2] https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
[3]
https://tools.wmflabs.org/meetbot/wikimedia-office/2015/wikimedia-office.20…
--
[fwding message from wikitech-l and other lists]
I want to modify the term "Search" in the standard search bar that would apply across all skins. Any suggestions? Thanks.
Best,
Andrew
Andrew Geary
SEG Wiki editor
Society of Exploration Geophysicists (SEG)
8801 South Yale, Suite 500 / Tulsa, OK 74137 USA
504-407-1303
ageary(a)seg.org
www.seg.org