Hyphe: web corpus curation tool & links crawler
Hyphe aims at providing a tool to build web corpus by crawling data from the web and generating networks between what we call "web entities", which can be single pages as well as a website, subdomains or parts of it, or even a combination of those.
You can try a limited version of Hyphe at the following url: http://hyphe.medialab.sciences-po.fr/demo/
How to install?
Before running Hyphe, you may want to adjust the settings first. The default config will work but you may want to tune it for your own needs. There is a procedure to change the configuration after the installation. However we recommend to take a look at the Configuration documentation for detailed explanation of each available option.
Warning: Hyphe can be quite disk-consuming, a big corpus with a few hundred crawls with a depth 2 can easily take up to 50GB, so if you plan on allowing multiple users, you should ensure at least a few hundreds gigabytes are available on your machine. You can reduce disk-space by setting to false the option
store_crawled_html_content and limiting the
Migrating older versions
Hyphe has changed a lot in the past few years. Migrating from an older version by pulling the code from git is not guaranteed anymore, it is highly recommended to reinstall from scratch. Older corpora can be rebuilt by exporting the list of web entities from the old version and recrawl from that list of urls in the new Hyphe.
Easy install: using Docker
For an easy install either on Linux, Mac OS X or Windows, the best solution is to rely on Docker.
Docker enables isolated install and execution of software stacks, which helps installing easily a whole set of dependencies.
Docker's containers are sizeable: you should ensure at least 4GB of empty space is available before installing. In any case, as expressed above, for a regular and complete use of Hyphe, you should better ensure at least 100GB are available.
1. Install Docker
First, you should deploy Docker on your machine following its official installation instructions.
Once you've got Docker installed and running, you will need Docker Compose to set up and orchestrate Hyphe services in a single line. Docker Compose is already installed along with Docker on Windows and Mac OS X, but you may need to install it for Linux.
2. Download Hyphe
Collect Hyphe's sourcecode from this git repository (recommended way to benefit from future updates) or download and uncompress a zipped release, then enter the resulting directory:
git clone https://github.com/medialab/hyphe.git hyphe cd hyphe
Then, copy the default configuration files and edit them to adjust the settings to your needs:
# use "copy" instead of "cp" under Windows powershell cp .env.example .env cp config-backend.env.example config-backend.env cp config-frontend.env.example config-frontend.env
.env file lets you configure:
TAG: the reference Docker image you want to work with among
prod: for the latest stable release
preprod: for intermediate unstable developments
PUBLIC_PORT: the web port on which Hyphe will be served (usually 80 for a single service server, or for a shared host any other port you like which will need to be redirected)
DATA_PATH: using Hyphe can quickly consume several gigabytes of hard drive. By default, volumes will be stored within Docker's default directories but you can define your own path here.
DATA_PATHMUST be either empty, or a full absolute path including leading and trailing slashes (for instance
It is not currently supported under Windows, and should always remain empty in this case (so you should install Hyphe from a drive with enough available space).
RESTART_POLICY: the choice of autorestart policy you want Hyphe containers to apply
no: (default) containers will not be restarted automatically under any circumstance
always: containers will always restart when stopped
on-failure: containers will restart only if the exit code indicates an on-failure error
unless-stopped: containers will always restart unless when explicitly stopped
If you want Hyphe to start automatically at boot, you should use the
alwayspolicy and make sure the Docker daemon is started at boot time with your service manager.
Hyphe's internal settings are adjustable within
config-frontend.env. Adjust the settings values to your needs following recommendations from the config documentation.
If you want to restrict Hyphe's access to a selected few, you should leave
HYPHE_OPEN_CORS_API false in
config-backend.env, and setup
openssl passwd -apr1 to generate your password's encrypted value).
4. Prepare the Docker containers
You have two options: either collect, or build Hyphe's Docker containers.
Recommended: Pull our official preassembled images from the Docker Store
Alternative: Build your own images from the source code (mostly for development or if you intend to edit the code, and for some very specific configuration settings):
Pulling should be faster, but it will still take a few minutes to download or build everything either way.
5. Start Hyphe
Finally, start Hyphe containers with the following command, which will run Hyphe and display all of its logs in the console until stopped by pressing
Or run the containers as a background daemon (for instance for production on a server):
docker-compose up -d
6. Stop and monitor Hyphe
To stop containers running in background, use
docker-compose stop (or
docker-compose down to also clean relying data).
You can inspect the logs of the various Docker containers using
docker-compose logs, or with option
-f to track latest entries like with
Whenever you change any configuration file, restart the Docker container to take the changes into account:
docker-compose stop docker-compose up -d
docker-compose help to get more explanations on any extra advanced use of Docker.
If you encounter issues with the Docker builds, please report an issue including the "Image ID" of the Docker images you used from the output of
docker images or, if you installed from source, the last commit ID (read from
7. Update to future versions
If you installed from git by pulling our builds from DockerHub, you should be able to update Hyphe to future minor releases by simply doing the following:
docker-compose down git pull docker-compose pull # eventually edit your configuration files to use new options docker-compose up -d
Manual install (complex and only for Linux)
If your computer or server relies on an old Linux distribution unable to run Docker, if you want to contribute to Hyphe's backend development, or for any other personal reason, you might want to rather install Hyphe manually by following the manual install instructions.
Please note there are many dependencies which are not always trivial to install and that you might run in quite a bit of issues. You can ask for some help by opening an issue and describing your problem, hopefully someone will find some time to try and help you.
Hyphe relies on a web interface with a server daemon which must be running at all times. When manually installed, one must start, stop or restart the daemon using the following command (without
bin/hyphe <start|restart|stop> [--nologs]
By default the starter will display Hyphe's log in the console using
tail. You can use
Ctrl+C whenever you like to stop displaying logs without shutting Hyphe down. Use the
--nologs option to disable logs display on start. Logs are always accessible from the
All settings can be configured directly from the global configuration file
config/config.json. Restart Hyphe afterwards to take changes into account:
Serve Hyphe on the web
As soon as the Docker containers or the manual daemon start, you can use Hyphe's web interface on your local machine at the following url:
For personal uses, you can already work with Hyphe as such. Although, if you want to let others use it as well (typically if you installed on a distant server), you need to serve it on a webserver and make a few adjustments.
Read the dedicated documentation to do so.
Advanced developers features & contributing
See our roadmap!
Papers & references
- Explanatory video (french) Explorer les internets avec Hyphe (September 2017). Mathieu Jacomy presents Hyphe at Sciences Po CEVIPOF during METSEM, a seminar on digital methods in social sciences.
Publications about Hyphe
JACOMY, Mathieu, GIRARD, Paul, OOGHE, Benjamin, et al, "Hyphe, a curation-oriented approach to web crawling for the social sciences.", in International AAAI Conference on Web and Social Media. Association for the Advancement of Artificial Intelligence, 2016.
PLIQUE, Guillaume, JACOMY, Mathieu, OOGHE-TABANOU Benjamin & GIRARD, Paul, "It's a Tree... It's a Graph... It's a Traph!!!! Designing an on-file multi-level graph index for the Hyphe web crawler". (Video / Slides) Presentation at the FOSDEM, Brussels, BELGIUM, February 3rd, 2018.
Publications using Hyphe
VENTURINI, Tommaso, JACOMY, Mathieu, BOUNEGRU, Liliana & GRAY, Jonathan, (2018, forthcoming), "Visual Network Exploration for Data Journalists", in S. E. I. and B. Franklin (Ed.). Abingdon: Routledge.
FROIO, Caterina, "Nous et les autres. L’altérité sur les sites web des extrêmes droites en France", in Réseaux, 2017/2 (n° 202-203), p. 39-78. DOI : 10.3917/res.202.0039.
ARZHEIMER, Kai, "The AfD’s Facebook Wall: A new Hub for Right-Wing Mobilisation in Germany?", in American Political Science Association Conference, 2015.
PEDROJA, Cynthia, et al. "Dépasser la liste : quand la bibliothèque entre dans la danse des corpus web." Digital Humanities 2016 (DH2016). Jagiellonian University & Pedagogical University, 2016.
DE CARVALHO PEREIRA, Débora "Produits laitiers : les réseaux d'influence sur le web".
OJALA, Mace "Mining with Hyphe", 2018 (a blog post on Ethos Lab's blog)
CREPEL, Maxime, BOULLIER, Dominique, JACOMY, Mathieu, OOGHE-TABANOU, Benjamin, ANTOLINOS-BASSO, Diego, MONSALLIER, Paul "Privacy web corpus", 2017.
CAYLA, Nathalie, PEYRACHE-GADEAU, Véronique, La singularité territoriale générée par le déploiement de la marque Parc naturel régional, 2017
ROGERS, Richard. Digital Methods for Cross-platform Analysis. J. Burgess, A. Marwick e T. Poell (a cura di) The Sage Handbook of Social Media. London: Sage, 2017.
SERRES, Alexandre et STALDER, Angèle. L'EMI sur le web: cartographie d'un domaine en émergence. In : Journée d'étude GRCDI-ESPE de Caen et Rouen,«L’EMI en questions: enjeux, prescriptions, contenus, apprentissages». 2016.
BERTHELOT, Marie-Aimée, SEVERO, Marta, et KERGOSIEN, Eric. Cartographier les acteurs d'un territoire: une approche appliquée au patrimoine industriel textile du Nord-Pas-de-Calais. In : CIST2016-En quête de territoire (s)?. 2016. p. 66-72.
SCHNEIDER, Élisabeth, SERRES, Alexandre, et STALDER, Angèle. L’EMI en partage: essai de cartographie des acteurs. In : 10e Congrès des Enseignants Documentalistes de l'Education Nationale" Enseigner-apprendre l'information-documentation". 2015.
KERGOSIEN, Eric, JACQUEMIN, Bernard, SEVERO, Marta, et al. Vers l'interopérabilité des données hétérogènes liées au patrimoine industriel textile. In : CiDE. 18. 18e Colloque international sur le Document Électronique. Europia, 2015. p. 145-158.
MUNK, Anders Kristian. Mapping Wind Energy Controversies Online: Introduction to Methods and Datasets. 2014.
Credits & License
Discover more of our projects at médialab tools.
Hyphe is a free open source software released under AGPL 3.0 license.
[...] I hear _kainos_ [(greek: "now")] in the sense of thick, ongoing presence, with __hyphae__ infusing all sorts of temporalities and materialities."
Donna J. Haraway, Staying with the Trouble, Making kin with the Chthlucene p.2