New publication workflow at W3C — main component
HTML JavaScript Other
tripu Merge pull request #594 from w3c/greenkeeper/file-type-9.0.0
Update file-type to the latest version 🚀
Latest commit 4e2014b Aug 10, 2018
Permalink
Failed to load latest commit information.
assets
doc Presentation: tweaks and corrections Jun 4, 2015
lib transition request: point to requirements if issue not found Aug 8, 2018
test nsp → npm audit; jscs → eslint Jul 23, 2018
views Update link to live version of Specberus Apr 9, 2018
.eslintrc.json nsp → npm audit; jscs → eslint Jul 23, 2018
.gitignore Exclude "package-lock.json" from version control Jun 21, 2017
.istanbul.yml Remove all traces of Bower and Grunt. May 18, 2015
.jshintignore
.jshintrc Simple Web interface Jul 14, 2017
.travis.yml nsp → npm audit; jscs → eslint Jul 23, 2018
CONTRIBUTING.md Node.js >=4.1.2, npm >=3.3.6; also in Travis; update docs Oct 9, 2015
LICENSE Add MIT license to the project Jan 16, 2015
README.md Simple Web interface Jul 14, 2017
app.js nsp → npm audit; jscs → eslint Jul 23, 2018
config.js.example check if the document was already published before looking for the ap… Jun 21, 2018
jsdoc.json nsp → npm audit; jscs → eslint Jul 23, 2018
known-vulns.txt Update known vulnerabilities: one just got fixed Aug 8, 2018
package.json fix(package): update file-type to version 9.0.0 Aug 10, 2018
sendmail.sh include decision and request id in the notification email Dec 21, 2016
whitelist.json Adapt config and whitelist to changes in third-party-resources-checker. May 25, 2015

README.md

Build Status Coverage Status Dependency Status devDependency Status Inline docs

Echidna

Greenkeeper badge

Echidna is the central piece of software taking care of the new publication workflow at W3C. The plan is for Echidna and related sub-projects (see below) to automate the publication of new specs under http://www.w3.org/TR/.

Using Echidna as an editor

If you are a spec editor, you do not need to install Echidna, nor to run it locally.

Please see the wiki for how to use Echidna as a spec editor.

Hacking Echidna as a developer

Installation

To run Echidna, you need to install Node.js first. This will install npm at the same time, which is required as well.

Then run the following commands with your favorite terminal:

git clone https://github.com/w3c/echidna.git
cd echidna
cp config.js.example config.js
npm install

Running it locally

Note: local setup of the full system is not supported currently due to dependency on W3C's DB and IPP system, but having mock services that emulate these pieces is our short-term goal.

In your terminal, run the following:

npm start [-- STAGING_PATH [HTTP_LOCATION [PORT [RESULT_PATH]]]]

You may use the optional defined below:

  1. STAGING_PATH: path in the local filesystem where documents will be downloaded; staged. (Default /var/www/html/trstaging/.)
  2. HTTP_LOCATION: HTTP endpoint for Specberus and the Third Party Resources Checker. (Default http://localhost/trstaging/.)
  3. PORT: where Echidna will be listening for publication requests. (Default 3000.)
  4. RESULT_PATH: local path where Echidna will dump the results of publication requests in JSON format.

Alternatively, you can use the configuration file config.js.

Once the server is started, you can throw publication requests at it through a curl/POST request to its enpoint, http://localhost:3000/api, or using the web-based testbed (described below).

You can also use a simple web client to send and monitor those requests, at http://localhost:3000/ui.

Testing Echidna

This section describes how to run Echidna's test suite to make sure that the project itself is working properly over time. Note that the test suite is not intended to test actual documents.

Running the unit test suite

You can run the test suite with the following command line:

npm test

Using test documents

For testing purposes, we are using a local web server. The test server simulates some of the W3C services, such as the CSS and HTML validators, or the token authorization checker. It also serves a set of sample drafts.

You can launch this test server separately by using:

npm run testserver

When the test server is running, the testbed with all drafts will be available in http://localhost:3001.

Feedback and contributions

Please refer to our contribution reference to learn how to contact us, give feedback, or actively contribute to this project.