You are browsing a read-only backup copy of Wikitech. The live site can be found at

Nova Resource Talk:Webtools

From Wikitech-static
Revision as of 04:18, 21 May 2013 by imported>Tim Landscheidt (Add deprecation note here as well.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

URLs of MMPs

One thing I always loathed about MMPs and think may be addressed by Webtools is the neglect of what Berners-Lee so nicely put as: "Cool URIs don't change." If the MMPification of a tool means that all URLs need to be updated, there is significant pressure not to do that. What I'd propose for Webtools, thus, is to have a way to easily call dibs on some URL.

Say, I want to create a tool superdupertool, I execute $CMD superdupertool as user scfc, and – if it didn't exist already – a rewrite from to is automatically added. As the developer doesn't have to contact a (human) administrator, I think this could foster more permanent URLs and thus more potential for collaboration. --Tim Landscheidt (talk) 18:23, 26 September 2012 (UTC)

My plan is to make tools trivial to make (ie. you run maketool superdupertool and you automatically get a MMP at User urls would be supported but deprecated, their usage should be limited to tests, kind of User:Foo/sandbox.
As we are going to change urls from toolserver to wmflabs, we can skip the step of creating ~scfc/superdupertool/ urls. The focus should be on the tools, not on the MMP or the user which created them.
platonides (talk) 20:47, 29 September 2012 (UTC)
Starting with a clean slate, your approach is probably better. Even more, if maketool was a tool that was intended to be used generously (and had accompanying add-maintainer, etc. executable by user and not by JIRA ticket :-)), it might be reasonable to disable user URLs altogether.
If you need help or a tester, you can add me to the project. --Tim Landscheidt (talk) 22:32, 29 September 2012 (UTC)

Request for membership

Hello, I would like to become a member of this project as I am testing the possibilities to port some Toolserver tools as tools:~dewpmp and tools:~wppb to Labs. Best regards, --ireas (talk) 21:15, 23 December 2012 (UTC)

Added Platonides (talk) 18:40, 4 January 2013 (UTC)

Kindly add user 'tb' to this project

Howdy. User 'tb' from the toolserver here, requesting access to evaluate what may be feasible to migrate here. - tb (talk) 12:25, 24 December 2012 (UTC)

Added Platonides (talk) 18:40, 4 January 2013 (UTC)

Another request to join

Hello, I'd like to join this project. I am a Toolserver user (russell) and want to explore migrating tools from there to here. Thanks. --russblau (talk) 20:51, 3 January 2013 (UTC)

Added Platonides (talk) 18:40, 4 January 2013 (UTC)

path names and URLs

I think a better location for tools would be /data/project/<name>. Why add a /web? And the URL shouldn't be<name> but<name> (or Maybe we can use<name> later as well, when the toolserver will be decommissioned (if it will be at all). – gifti (talk) 18:30, 9 January 2013 (UTC)

Request to join

Hi! I'd also like to join the Webtools project. I intend to provide a simple tool for making/handling lists for sv-wikt, currently on Toolserver. I'd also explore more tools for sv-wikt. skalman (talk) 04:34, 22 January 2013 (UTC)

Engineering design goals

Hi guys. Feeling like a bit of a dinosaur here, computerwise; specifically I've little understanding of practical design goals in a virtual environment.

Currently I maintain a suite of a dozen or so tools on the toolserver. They're all traditional LAMP applications - a server process that generates some useful data, a SQL database to store the data, a front end that reads the data and presents it in response to user requests.

Should I be planning to:

  1. Implement these within a single server instance shared between myself and other similar projects
  2. Implement them all in a server instance scaled to the entire tool suite.
  3. Raise a cluster of small servers, sized to each individual tool.

I have fairly good metrics to hand for each tool (disk, CPU, TPMs) and a fairly long list of packages needed to build and run them (gcc, bison, php, flex, lisp etc). - tb (talk) 13:50, 31 January 2013 (UTC)


I think it would be a good idea to make it easy for people to deploy rails apps (I my self really want to stop using php as much as possible). azatoth (talk) 19:48, 13 February 2013 (UTC)

Oh yea, wanna join as well. azatoth (talk) 19:49, 13 February 2013 (UTC)
Double personality? I have never used rails, but it should be possible to do. You are of course encouraged to provide a server configuration for that. ;) platonides (talk) 22:36, 16 February 2013 (UTC)

Request to join

I am a Toolserver user and want to develop some tools here. Thanks.

DGideas (talk) 11:52, 29 March 2013 (UTC)

You are probably looking for the Tools project. --Tim Landscheidt (talk) 03:31, 1 April 2013 (UTC)

Request to join

I am a b'crat in ko.wikipedia and a toolserver user. I want to develop a web tools for the ko.wikipedia. Thanks. -- ChongDae (talk) 02:02, 10 April 2013 (UTC)