Release 0.3.0 Patrick Vergain

Total Page:16

File Type:pdf, Size:1020Kb

Release 0.3.0 Patrick Vergain Documentation tutorial Documentation Release 0.3.0 Patrick Vergain 2018-5-3 Contents 1 Documentation 3 1.1 Documentation news...........................................3 1.1.1 Documentation news 2018...................................3 1.1.2 Documentation news 2017...................................3 1.1.3 Documentation news 2016...................................4 1.2 Documentation Advices.........................................4 1.2.1 You are what you document (Monday, May 5, 2014).....................5 1.2.2 Rédaction technique......................................5 1.2.3 13 Things People Hate about Your Open Source Docs.....................7 1.2.4 Beautiful docs..........................................7 1.2.5 Designing Great API Docs (11 Jan 2012)...........................7 1.2.6 Docness.............................................7 1.2.7 Hacking distributed (february 2013)..............................7 1.2.8 Jacob Kaplan-Moss (November 10, 2009)...........................8 1.2.9 Agile documentation best practices...............................8 1.2.10 Best Practices for Documenting Technical Procedures Melanie Seibert............8 1.2.11 Plone..............................................8 1.2.12 Twilio..............................................9 1.2.13 Other advices..........................................9 1.3 Documentation generators........................................ 11 1.3.1 Sphinx.............................................. 12 1.3.2 Authorea............................................ 147 1.3.3 Doxygen............................................ 147 1.3.4 Javadoc............................................. 162 1.3.5 Jekyll.............................................. 162 1.3.6 JSDoc.............................................. 163 1.3.7 Mkdocs............................................. 164 1.3.8 Pandoc............................................. 165 1.4 Good documentation........................................... 167 1.4.1 CakePHP............................................ 167 1.4.2 Passlib.............................................. 167 1.4.3 Sfepy.............................................. 167 1.4.4 Shark.............................................. 168 1.5 Formats Documentation......................................... 168 1.5.1 Input formats.......................................... 168 1.5.2 Input/output formats...................................... 178 i 1.5.3 Output formats......................................... 178 1.6 Documentation projects......................................... 182 1.6.1 C Documentation projects................................... 182 1.6.2 Mozilla documentation..................................... 182 1.6.3 Documenting python projects.................................. 182 1.7 Documentation tools........................................... 184 1.7.1 Dash............................................... 184 1.7.2 Graphviz............................................ 185 1.7.3 Zeal documentation browser.................................. 186 1.8 Documentation videos.......................................... 186 1.8.1 Write the docs.......................................... 186 1.8.2 RTFM - wRite The Friendly Manual.............................. 187 1.9 Wiki documentation........................................... 187 1.9.1 Mediawiki............................................ 187 1.9.2 Wiki tools............................................ 198 2 Command Line Interface (CLI) 203 2.1 Introduction............................................... 203 2.2 Usage................................................... 204 2.2.1 CLI and python......................................... 204 2.2.2 CLI with Perl.......................................... 204 2.2.3 Command Line Interface (CLI) on GNU/linux......................... 209 2.2.4 Command Line Interface (CLI) on Windows.......................... 221 2.2.5 Google cli............................................ 233 ii Documentation tutorial Documentation, Release 0.3.0 Documentation tutorial Release 0.3.0 Date 2018-5-3 Authors Patrick Vergain Target Tutorial about documentation See also: • https://gdevops.gitlab.io/tuto_devops/ • genindex • reStructuredText Sphinx documentation • https://gitlab.com/gdevops/tuto_documentation • https://gdevops.gitlab.io/tuto_documentation/index.html • https://devopstutodoc.readthedocs.io/en/latest/index.html • https://readthedocs.org/projects/devopstutodoc/ Contents 1 Documentation tutorial Documentation, Release 0.3.0 2 Contents CHAPTER 1 Documentation See also: • http://blog.smartbear.com/software-quality/bid/256072/13-reasons-your-open-source-docs-make-people-want-to-scream • http://brikis98.blogspot.de/2014/05/you-are-what-you-document.html • http://redaction-technique.org/index.html 1.1 Documentation news 1.1.1 Documentation news 2018 Contents • Documentation news 2018 – Bringing interactive examples to MDN Bringing interactive examples to MDN See also: • https://hacks.mozilla.org/2018/03/bringing-interactive-examples-to-mdn/ 1.1.2 Documentation news 2017 3 Documentation tutorial Documentation, Release 0.3.0 Contents • Documentation news 2017 – Autodoc-style extraction into Sphinx for your JS project Autodoc-style extraction into Sphinx for your JS project See also: • sphinx-js : autodoc-style extraction into Sphinx for your JS project 1.1.3 Documentation news 2016 Contents • Documentation news 2016 – La documentation linux utilise sphinx La documentation linux utilise sphinx See also: • https://github.com/return42/linuxdoc • https://return42.github.io/linuxdoc/ • https://lwn.net/Articles/692704/ L’annonce sur https://lwn.net/Articles/692704/ 1.2 Documentation Advices See also: • parse_API_doc • http://producingoss.com/en/getting-started.html • http://justwriteclick.com/book/ • http://brikis98.blogspot.de/2014/05/you-are-what-you-document.html • http://redaction-technique.org/index.html Contents • Documentation Advices – You are what you document (Monday, May 5, 2014) – Rédaction technique 4 Chapter 1. Documentation Documentation tutorial Documentation, Release 0.3.0 * Libérez vos informations de leurs silos * Intégrer la documentation aux processus de développement – 13 Things People Hate about Your Open Source Docs – Beautiful docs – Designing Great API Docs (11 Jan 2012) – Docness * Docness Source code – Hacking distributed (february 2013) – Jacob Kaplan-Moss (November 10, 2009) – Agile documentation best practices – Best Practices for Documenting Technical Procedures Melanie Seibert – Plone – Twilio – Other advices 1.2.1 You are what you document (Monday, May 5, 2014) See also: • http://brikis98.blogspot.de/2014/05/you-are-what-you-document.html • http://jacobian.org/writing/great-documentation/ • http://zachholman.com/posts/documentation/ • http://blog.parse.com/2012/01/11/designing-great-api-docs/ • http://www.mikepope.com/blog/DisplayBlog.aspx?permalink=1680 • https://github.com/PharkMillups/beautiful-docs • http://blog.codinghorror.com/if-it-isnt-documented-it-doesnt-exist/ • http://docs.writethedocs.org/writing/beginners-guide-to-docs/ The number one cause of startup failure is not the product, but the distribution: it doesn’t matter how good the product is if no one uses it. With software, the documentation is the distribution: it doesn’t matter how good the code is if no one uses it. If it isn’t documented, it doesn’t exist. 1.2.2 Rédaction technique See also: • http://redaction-technique.org/index.html 1.2. Documentation Advices 5 Documentation tutorial Documentation, Release 0.3.0 Libérez vos informations de leurs silos Des solutions souples et fiables libèrent vos informations des silos d’information cloisonnés où elles sont emprisonnées et sous-exploitées. Oubliez MS Word ou FrameMaker pour passer de la maintenance de la documentation à la gestion du cycle de vie des projets documentaires modulaires ! Intégrer la documentation aux processus de développement La documentation fait partie du logiciel. Fournie avec le produit, elle doit : • sortir en même temps, • suivre les mêmes cycles de vie, et • faire l’objet des mêmes processus de production et de contrôle qualité. Elle doit répondre idéalement aux critères suivants : • pas de vendor lock-in (indépendance du format et de l’éditeur de contenu), • chaînes de publication libres et gratuites, • mise en page totalement automatisée. Il y a quelques années encore, les seuls outils permettant de fournir des livrables de qualité au format PDF ou HTML reposaient sur des formats binaires et propriétaires qui s’intégraient mal aux systèmes de gestion de versions des équipes de développement. Résultat : réalisée à part, la documentation technique répondait difficilement aux mêmes exigences de qualité et de délai de mise sur le marché que les produits. 6 Chapter 1. Documentation Documentation tutorial Documentation, Release 0.3.0 DocBook, puis DITA XML et reStructuredText ont changé la donne : ces formats texte peuvent être modifiés avec tout type de programme, du simple éditeur de texte à l’‘IDE graphique, et s’intègrent parfaitement sous Subversion, Git ou tout autre système de gestion de versions. 1.2.3 13 Things People Hate about Your Open Source Docs See also: • http://blog.smartbear.com/careers/13-things-people-hate-about-your-open-source-docs/ • http://www.framablog.org/index.php/post/2013/06/28/documentation-defauts-open-source 1.2.4 Beautiful docs See also: • https://github.com/PharkMillups/beautiful-docs 1.2.5 Designing Great API Docs (11 Jan 2012) See also: • http://blog.parse.com/2012/01/11/designing-great-api-docs/ 1.2.6
Recommended publications
  • Tinn-R Team Has a New Member Working on the Source Code: Wel- Come Huashan Chen
    Editus eBook Series Editus eBooks is a series of electronic books aimed at students and re- searchers of arts and sciences in general. Tinn-R Editor (2010 1. ed. Rmetrics) Tinn-R Editor - GUI forR Language and Environment (2014 2. ed. Editus) José Cláudio Faria Philippe Grosjean Enio Galinkin Jelihovschi Ricardo Pietrobon Philipe Silva Farias Universidade Estadual de Santa Cruz GOVERNO DO ESTADO DA BAHIA JAQUES WAGNER - GOVERNADOR SECRETARIA DE EDUCAÇÃO OSVALDO BARRETO FILHO - SECRETÁRIO UNIVERSIDADE ESTADUAL DE SANTA CRUZ ADÉLIA MARIA CARVALHO DE MELO PINHEIRO - REITORA EVANDRO SENA FREIRE - VICE-REITOR DIRETORA DA EDITUS RITA VIRGINIA ALVES SANTOS ARGOLLO Conselho Editorial: Rita Virginia Alves Santos Argollo – Presidente Andréa de Azevedo Morégula André Luiz Rosa Ribeiro Adriana dos Santos Reis Lemos Dorival de Freitas Evandro Sena Freire Francisco Mendes Costa José Montival Alencar Junior Lurdes Bertol Rocha Maria Laura de Oliveira Gomes Marileide dos Santos de Oliveira Raimunda Alves Moreira de Assis Roseanne Montargil Rocha Silvia Maria Santos Carvalho Copyright©2015 by JOSÉ CLÁUDIO FARIA PHILIPPE GROSJEAN ENIO GALINKIN JELIHOVSCHI RICARDO PIETROBON PHILIPE SILVA FARIAS Direitos desta edição reservados à EDITUS - EDITORA DA UESC A reprodução não autorizada desta publicação, por qualquer meio, seja total ou parcial, constitui violação da Lei nº 9.610/98. Depósito legal na Biblioteca Nacional, conforme Lei nº 10.994, de 14 de dezembro de 2004. CAPA Carolina Sartório Faria REVISÃO Amek Traduções Dados Internacionais de Catalogação na Publicação (CIP) T591 Tinn-R Editor – GUI for R Language and Environment / José Cláudio Faria [et al.]. – 2. ed. – Ilhéus, BA : Editus, 2015. xvii, 279 p. ; pdf Texto em inglês.
    [Show full text]
  • Tuto Documentation Release 0.1.0
    Tuto Documentation Release 0.1.0 DevOps people 2020-05-09 09H16 CONTENTS 1 Documentation news 3 1.1 Documentation news 2020........................................3 1.1.1 New features of sphinx.ext.autodoc (typing) in sphinx 2.4.0 (2020-02-09)..........3 1.1.2 Hypermodern Python Chapter 5: Documentation (2020-01-29) by https://twitter.com/cjolowicz/..................................3 1.2 Documentation news 2018........................................4 1.2.1 Pratical sphinx (2018-05-12, pycon2018)...........................4 1.2.2 Markdown Descriptions on PyPI (2018-03-16)........................4 1.2.3 Bringing interactive examples to MDN.............................5 1.3 Documentation news 2017........................................5 1.3.1 Autodoc-style extraction into Sphinx for your JS project...................5 1.4 Documentation news 2016........................................5 1.4.1 La documentation linux utilise sphinx.............................5 2 Documentation Advices 7 2.1 You are what you document (Monday, May 5, 2014)..........................8 2.2 Rédaction technique...........................................8 2.2.1 Libérez vos informations de leurs silos.............................8 2.2.2 Intégrer la documentation aux processus de développement..................8 2.3 13 Things People Hate about Your Open Source Docs.........................9 2.4 Beautiful docs.............................................. 10 2.5 Designing Great API Docs (11 Jan 2012)................................ 10 2.6 Docness.................................................
    [Show full text]
  • C-C++ Beautifier HOW-TO
    C-C++ Beautifier HOW-TO Al Dev (Alavoor Vasudevan) < alavoor[AT]yahoo.com > v16.7, 2 Nov 2003 Abstract This document will help you to format (beautify) the C/C++ programs so that it is more readable and confirms to your site C/C++ coding standards. The information in this document applies to all the operating sytems that is - Lin- ux, MS DOS, Apple Macintosh, Windows 95/NT/2000, BeOS, OS/2, IBM OSes, all flavors of Unix like Solaris, HPUX, AIX, SCO, Sinix, BSD, UnixWare, etc.. and to all other operating systems which support "C" compiler (it means almost all the operating systems on this planet!). Table of Contents Introduction ...................................................................................................................... 1 Installing BCPP ................................................................................................................. 2 How can I trust Beautifier programs??!! ................................................................................ 3 Method 1: Verfication Program for C++/C ..................................................................... 3 Method 2: Verfication Program for C++/C ..................................................................... 3 Method 3: Verfication Program for Java/C++/Others ........................................................ 4 Method 4: Shell script: Verfication Program for C++/C .................................................... 5 HTML Beautifier ..............................................................................................................
    [Show full text]
  • The Types, Roles, and Practices of Documentation in Data Analytics Open Source Software Libraries
    Computer Supported Cooperative Work (CSCW) https://doi.org/10.1007/s10606-018-9333-1 © The Author(s) 2018 The Types, Roles, and Practices of Documentation in Data Analytics Open Source Software Libraries A Collaborative Ethnography of Documentation Work R. Stuart Geiger1 , Nelle Varoquaux1,2 , Charlotte Mazel-Cabasse1 & Chris Holdgraf1,3 1Berkeley Institute for Data Science, University of California, Berkeley, 190 Doe Library, Berkeley, CA, 94730, USA (E-mail: [email protected]); 2Department of Statistics, Berkeley Institute for Data Science, University of California, Berkeley, Berkeley, CA, USA; 3Berkeley Institute for Data Science, Helen Wills Neuroscience Institute, University of California, Berkeley, Berkeley, CA, USA Abstract. Computational research and data analytics increasingly relies on complex ecosystems of open source software (OSS) “libraries” – curated collections of reusable code that programmers import to perform a specific task. Software documentation for these libraries is crucial in helping programmers/analysts know what libraries are available and how to use them. Yet documentation for open source software libraries is widely considered low-quality. This article is a collaboration between CSCW researchers and contributors to data analytics OSS libraries, based on ethnographic fieldwork and qualitative interviews. We examine several issues around the formats, practices, and challenges around documentation in these largely volunteer-based projects. There are many dif- ferent kinds and formats of documentation that exist around such libraries, which play a variety of educational, promotional, and organizational roles. The work behind documentation is similarly multifaceted, including writing, reviewing, maintaining, and organizing documentation. Different aspects of documentation work require contributors to have different sets of skills and overcome various social and technical barriers.
    [Show full text]
  • Automation to Save Your Bacon Elliot Jordan End-User Platform Security Nordstrom “I’M Not Really a Software Developer
    Linters Hooks Pipelines Automation to Save Your Bacon Elliot Jordan End-User Platform Security Nordstrom “I’m not really a software developer. I just think I’m a software developer because I develop software.” — Arjen van Bochoven ‣ Package sources ‣ Scripts and extension plist, yaml, json, shell, python attributes ‣ AutoPkg recipes/ shell, python overrides ‣ MDM profiles plist, shell, python plist ‣ Munki repos ‣ Documentation plist, python, shell text, markdown, reStructuredText Mac Software "Dev Ops" Admin Developer Reducing errors Streamlining development Automating tedious tasks Ground Rules Protected "master" branch Peer review Remote Git hosting Production code in Git Code standards Linters Linters Linters Linters Linters Linters Linters Atom + Shellcheck Linters Atom + Shellcheck Terminal $ brew install shellcheck ==> Downloading https://homebrew.bintray.com/bottles/ shellcheck-0.6.0_1.mojave.bottle.tar.gz ==> Pouring shellcheck-0.6.0_1.mojave.bottle.tar.gz ! /usr/local/Cellar/shellcheck/0.6.0_1: 8 files, 7.2MB $ which shellcheck /usr/local/bin/shellcheck ⌘C $ Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck ⌘V Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Linters Atom + Shellcheck Click to learn more! Linters Atom + Shellcheck Linters Atom + Shellcheck Typo caught Linters Atom + Shellcheck Suggestions for improving resiliency Linters Atom + Shellcheck Deprecated syntax
    [Show full text]
  • Howtos with Linuxdoc
    HOWTOs with LinuxDoc David S. Lawyer v0.09, November 2007 Questo testo tratta di come scrivere gli HOWTO usando il semplice linguaggio a marcatori (markup) LinuxDoc. È rivolto principalmente agli autori del Linux Documentation Project (e ad autori futuri alle prime armi che vogliono iniziare rapidamente). Se si vuole usare DocBook, il linguaggio a marcatori più completo e dicile, (incluso XML), vedere la LDP Authoring Guide (Guida per gli autori di LDP). Traduzione ed adattamenti in italiano a cura di Beatrice Torracca, beatricet (at) libero (dot) it, e Hugh Hartmann, hhartmann (at) libero (dot) it, revisione a cura di Vieri Giugni, v.giugni (at) gmail (dot) com). Per versioni aggiornate di questo documento, e per trovare altra documentazione in italiano sul software libero, visitare il sito dell' ILDP <http://it.ildp.org> Indice 1 Introduzione 2 1.1 Per partire immediatamente.....................................2 1.2 Copyright e licenza..........................................3 1.3 Perché si dovrebbe scrivere un HOWTO?.............................3 1.4 Perché ho scritto questo documento................................3 2 Informazioni sulla scrittura di un HOWTO3 2.1 Copyright...............................................3 2.2 Scegliere un argomento........................................3 3 Il formato degli HOWTO4 3.1 Introduzione..............................................4 4 LinuxDoc e DocBook a confronto4 5 Imparare LinuxDoc 6 5.1 Introduzione..............................................6 5.2 Esempio 1 (nome le: esempio1.sgml)...............................6 5.3 Esempio 2 (nome le: esempio2.sgml)...............................7 5.4 Esempio 3 (nome le: esempio3.sgml)...............................9 5.5 Guida di consultazione rapida di LinuxDoc............................ 11 5.5.1 Intestazione.......................................... 11 5.5.2 Impaginazione del corpo................................... 12 5.5.3 Tipi di carattere....................................... 12 1.
    [Show full text]
  • Open-Source Documentation
    Open-Source Documentation: In Search of User-Driven, Just-in-Time Writing Erik Berglund Michael Priestley Linköping University IBM Toronto Lab S-581 83, Linköping, Canada Sweden [email protected] + 46 13 28 24 93 [email protected] ABSTRACT Keywords Iterative development models allow developers to respond quickly Open source documentation, just-in-time, user-driven. to changing user requirements, but place increasing demands on writers who must handle increasing amounts of change with ever- 1. THE PROBLEM decreasing resources. In the software development world, one Over the years, the software industry has accepted that changing solution to this problem is open-source development: allowing the requirements are simply part of the software development process. users to set requirements and priorities by actually contributing to An allowance for client requirements change, even an expectation the development of the software. This results in just-in-time of change, is at the foundation of most software development software improvements that are explicitly user-driven, since they methodologies. The Rational Unified Process (RUP) illustrates are actually developed by users. this, and Extreme Programming (XP) exemplifies it. Taken to the In this article we will discuss how the open source model can be extreme, as it often is in open-source development, the extended to the development of documentation. In many open- functionality of the product may not be determined until the day it source projects, the role of writer has remained unchanged: is completed. documentation development remains a specialized activity, owned Continuous requirements change makes traditional methods of by a single writer or group of writers, who work as best they can software documentation difficult.
    [Show full text]
  • Manticore Search Documentation Release 3.0.2
    Manticore Search Documentation Release 3.0.2 The Manticore Search team Apr 01, 2021 Manticore Documentation 1 Introduction 1 2 Gettting Started 5 2.1 Getting started using Docker container.................................5 2.2 Getting Started using official packages................................. 10 2.3 Migrating from Manticore or Sphinx Search 2.x............................ 15 2.4 A guide on configuration file....................................... 17 2.5 A guide on connectivity......................................... 19 2.6 A guide on indexes............................................ 21 2.7 A guide on searching........................................... 24 3 Installation 31 3.1 Installing Manticore packages on Debian and Ubuntu.......................... 31 3.2 Installing Manticore packages on RedHat and CentOS......................... 32 3.3 Installing Manticore on Windows.................................... 33 3.4 Upgrading from Sphinx Search..................................... 34 3.5 Running Manticore Search in a Docker Container............................ 34 3.6 Compiling Manticore from source.................................... 35 3.7 Quick Manticore usage tour....................................... 38 4 Indexing 43 4.1 Indexes.................................................. 43 4.2 Data Types................................................ 47 4.3 Full-text fields.............................................. 49 4.4 Attributes................................................. 49 4.5 MVA (multi-valued attributes).....................................
    [Show full text]
  • Advanced Search Capabilities with Mysql and Sphinx
    Advanced search capabilities with MySQL and Sphinx Vladimir Fedorkov, Blackbird Andrew Aksyonoff, Sphinx Percona Live MySQL UC, 2014 Knock knock who’s there • Vladimir – Used Sphinx in production since 2006 – Performance geek – Blog http://astellar.com, twitter @vfedorkov – Works for Blackbird • Andrew – Created Sphinx, http://sphinxsearch.com – Just some random guy Search is important • This is 2014, Google spoiled everyone! • Search needs to exist • Search needs to be fast • Search needs to be relevant • Today, we aim to show you how to start – With Sphinx, obviously Available solutions • Most databases have integrated FT engines – MySQL (My and Inno), Postgres, MS SQL, Oracle… • Standalone solutions – Sphinx – Lucene / Solr – Lucene / ElasticSearch • Hosted services – IndexDen, SearchBox, Flying Sphinx, WebSolr, … Why Sphinx? • Built-in DB search sucks • Sphinx works great with DBs and MySQL • Sphinx talks SQL => zero learning curive • Fast, scalable, relevant, and other buzzwords :P • You probably heard about Lucene anyway • NEED MOAR DIVERSITY What Sphinx is not • Not a plugin to MySQL • Does not require MySQL • Not SQL-based (but we talk SQL) – Non-SQL APIs are available • Not a complete database replacement – Yet? – Ever! OLAP vs OLTP vs Column vs FTS vs Webscale Quick overview • Sphinx = standalone, open-source search server • Supports Real-time indexes • Fast – 10+ MB/sec/core indexing, 700+ qps/core searching – And counting! • Scalable – Can do a lot even on 1 box – Lets you aggregate search results from N boxes – Auto-sharding,
    [Show full text]
  • Sphinxql Query Builder Release 1.0.0
    SphinxQL Query Builder Release 1.0.0 Oct 12, 2018 Contents 1 Introduction 1 1.1 Compatiblity...............................................1 2 CHANGELOG 3 2.1 What’s New in 1.0.0...........................................3 3 Configuration 5 3.1 Obtaining a Connection.........................................5 3.2 Connection Parameters..........................................5 4 SphinxQL Query Builder 7 4.1 Creating a Query Builder Instance....................................7 4.2 Building a Query.............................................7 4.3 COMPILE................................................ 10 4.4 EXECUTE................................................ 10 5 Multi-Query Builder 13 6 Facets 15 7 Contribute 17 7.1 Pull Requests............................................... 17 7.2 Coding Style............................................... 17 7.3 Testing.................................................. 17 7.4 Issue Tracker............................................... 17 i ii CHAPTER 1 Introduction The SphinxQL Query Builder provides a simple abstraction and access layer which allows developers to generate SphinxQL statements which can be used to query an instance of the Sphinx search engine for results. 1.1 Compatiblity SphinxQL Query Builder is tested against the following environments: • PHP 5.6 and later • Sphinx (Stable) • Sphinx (Development) Note: It is recommended that you always use the latest stable version of Sphinx with the query builder. 1 SphinxQL Query Builder, Release 1.0.0 2 Chapter 1. Introduction CHAPTER 2 CHANGELOG 2.1 What’s New in 1.0.0 3 SphinxQL Query Builder, Release 1.0.0 4 Chapter 2. CHANGELOG CHAPTER 3 Configuration 3.1 Obtaining a Connection You can obtain a SphinxQL Connection with the Foolz\SphinxQL\Drivers\Mysqli\Connection class. <?php use Foolz\SphinxQL\Drivers\Mysqli\Connection; $conn= new Connection(); $conn->setparams(array('host' => '127.0.0.1', 'port' => 9306)); Warning: The existing PDO driver written is considered experimental as the behaviour changes between certain PHP releases.
    [Show full text]
  • { Type = Xmlpipe Xmlpipe Command = Perl /Path/To/Bin/Sphinxpipe2.Pl } Index Xmlpipe Source
    Setting up Sphinx ­ By Brett Estrade <[email protected]> http://www.justanswer.com/computer/expert­bestrade/ sphinx.conf: source example_xmlpipe_source { type = xmlpipe xmlpipe_command = perl /path/to/bin/sphinxpipe2.pl } index xmlpipe_source { src = example_xmlpipe_source path = /path/to/index_file_prefix docinfo = extern } command (assuming sphinxpipe2.pl outputs valid xmlpipe2 XML): indexer ­­config /path/to/sphinx.conf ­­all # creates indexes The above should just create the indexes. To set up the search server (searchd), the following needs to be added to the sphinx.conf: searchd { compat_sphinxql_magics = 0 listen = 192.168.0.2:9312 listen = 192.168.0.2:9306:mysql41 log = /path/to/searchd.log query_log = /path/to/query.log read_timeout = 30 max_children = 30 pid_file = /path/to/searchd.pid max_matches = 1000000 seamless_rotate = 1 preopen_indexes = 1 unlink_old = 1 workers = threads # for RT to work binlog_path = /path/to/sphinx_binlog } Assuming that searchd is running, the index command would require a “­­rotate” flag to read in the updated indexes whenever updated. indexer ­­rotate ­­config /path/to/sphinx.conf ­­all Searching Note that there is a MySQL compatible listening interface that is defined above using the “listen = 192.168.0.2:9306:mysql41” line. This means you can point a mysql client to “192.168.0.2:9306” and issue SELECT statements as described here: http://sphinxsearch.com/docs/archives/1.10/sphinxql.html Using the PHP Sphinx Client is covered starting at listing 12 of this article ­ http://www.ibm.com/developerworks/library/os­php­sphinxsearch/#list12 Note the difference between fields and attributes. Fields provide the text that is subject to the full text searching and indexing.
    [Show full text]
  • Using Css to Style the Pdf Output
    Oxygen Markdown Support Alex Jitianu, Syncro Soft [email protected] @AlexJitianu © 2020 Syncro Soft SRL. All rights reserved. Oxygen Markdown Support Agenda • Markdown – the markup language • Markdown editing experience in Oxygen • Markdown and DITA working together • Validation and check for completeness (Quality Assurance) Oxygen Markdown Support What is Markdown? • Easy to learn Create a Google account ============ • Minimalistic How to create or set up your **Google Account** on • your mobile phone. Many authoring tools available * From a Home screen, swipe up to access Apps. • Publishing tools * Tap **Settings** > **Accounts** * Tap **Add account** > **Google**. Oxygen Markdown Support Working with Markdown • Templates • Editing and toolbar actions (GitHub Flavored Markdown) • HTML/DITA/XDITA Preview • Export actions • Oxygen XML Web Author Oxygen Markdown Support DITA-Markdown hybrid projects • Main documentation project written in DITA • SME(s) (developers) contribute content in Markdown Oxygen Markdown Support What is DITA? • DITA is an XML-based open standard • Semantic markup • Strong reuse concepts • Restrictions and specializations • Huge ecosystem of publishing choices Oxygen Markdown Support Using specific DITA concepts in Markdown • Metadata • Specialization types • Titles and document structure • Image and key references • https://github.com/jelovirt/dita-ot-markdown/wiki/Syntax- reference Oxygen Markdown Support What is Lightweight DITA? • Lightweight DITA is a proposed standard for expressing simplified DITA
    [Show full text]