Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
Tom's Obvious, Minimal Language. Contribute to toml-lang/toml development by creating an account on GitHub. 
No comment yet.
Sign up to comment
Scoop.it!
From
dzone
Covers 16 patterns that serve to increase team agility, enhanced by general guidelines for improved SCM, and a list of resources.
Scoop.it!
Dans cet environnement hétérogène, nous utilisions déjà Vagrant pour gérer plusieurs VM Linux : intégration continue, bases de données, conteneur Web. Vagrant
Scoop.it!
Suite aux deux excellents articles de Michael Pagès sur Docker (Docker présentation – Part1, et Docker – Tutoriel : Isolation d’application par Projet – Part 2), j’ai eu envie d’essayer d’utiliser cet outil. Cependant, j’ai rencontré quelques difficultés lors de la mise en oeuvre, avec des résultats pas toujours voulus, ou bien de longues minutes à essayer de comprendre comment faire telle ou telle chose. Cet article n’est donc pas destiné à vous expliquer comment fonctionne docker, mais plutôt : “Comment l’utiliser”.
Scoop.it!
Open Source Software Configuration Management Tools: Source Control, Build, Deployment, Continuous Integration, Continuous Delivery
Scoop.it!
Pour maintenir en toute sérénité ses milliers de serveurs, Facebook a choisi le gestionnaire de configuration Open Source Chef pour gérer l'énorme infrastructure sur laquelle repose le géant des réseaux sociaux, en l'adaptant très légèrement.
Mickael Ruau's insight:
Pour trouver le système de gestion de configuration Open source le plus adapté, l'équipe a réalisé un certain nombre de tests avec Chef, Puppet, et Spine
Scoop.it!
the practice and the history of Continuous Integration and CruiseControl
Scoop.it!
L’intégration continue permet de révéler les éventuelles erreurs et incompatibilités des différentes parties réalisées par chaque développeur de l’équipe. Cruise Control, étant un serveur d’intégration continue, permet d’automatiser cette phase...
Mickael Ruau's insight:
L'intégration continue est une technique de développement/management de projet qui implique d'intégrer très fréquemment le travail de tous les membres d'une équipe. Ensuite, une compilation automatique doit être lancée pour vérifier les éventuelles erreurs de compilation du projet puis si possible les tests unitaires doivent aussi être lancés.
La plupart des outils d'intégration continue sont capable de faire les actions suivantes : lancement d'une intégration périodique (toutes les heures par exemple)mise à jour du code depuis un gestionnaire de code sourcecompilation du code sourcelancement des tests unitairesenvoi de mails automatique aux personnes concernés (celui qui a fait l'erreur recevra le mail d'erreur)envoi d'un mail de rapportdéploiement sur un serveur de testcréation de statistiques
Scoop.it!
A comparison of Opscode's Chef and Puppet Lab's Puppet for Enterprise applications.
Mickael Ruau's insight:
Conclusion
If you’re a large shop with a diverse range of skills in operations and development you may lean towards Puppet.
If you’re a Rails shop you’d probably go straight to Chef. There really is no definitive answer though. As mentioned above, doing one is light years better than doing neither so if you’re agonizing over the decision just stop, toss a coin and get going today.
Scoop.it!
Have you gotten frustrated with Puppet? Corey Quinn offers an impassioned argument for his favorite open source alternative.
Mickael Ruau's insight:
If you’re responsible for the care and feeding of multiple servers, and you haven’t heard about configuration management yet, you have not been paying attention. CFengine was one of the first configuration management systems that was deployed in anything approaching widespread use, and was followed later by Puppet and Chef. A bit over two years ago, Salt Stack‘s ”Salt” entered the market, and took a radically different approach to the problem of “configure all of my servers to do X.”
Scoop.it!
Ce sont les outils classiques de l'analyste-développeur. Ils simplifient les tâches redondantes et systématiques et lui permettent de se concentrer sur les points importants de la réalisation du logiciel.
Mickael Ruau's insight:
Outils de gestion de configuration
Ils évitent au développeur de passer des heures à configurer son poste de travail en gérant l'environnement du projet (présence de bibliothèques, intégration au système). "L'ancêtre" autotool (automake/autoconf) créé en 1992 pour les systèmes Linux a inspiré de nouveaux systèmes comme Ant et Maven principalement utilisés en Java.
Scoop.it!
Besides dependency management, with a little creativity Composer can also be used as a basic build automation tool for your PHP projects.
Mickael Ruau's insight:
Following Alexander Cogneau’s introduction to dependency management with Composer, you now know that Composer is a resolver for managing external project dependencies and versioning constraints. But is that all it does? In this article I’ll show you how Composer can also be used as a basic build automation tool.
Scoop.it!
Packagist is the main Composer repository. It aggregates all sorts of PHP packages that are installable with Composer.
Mickael Ruau's insight:
download composer.phar into your project root
|
Scoop.it!
Si les CMDB sont encore appréciées, elles ne dominent plus la gestion IT. Découvrez les options d’intégration de la CMDB qui subsistent et pourquoi les administrateurs doivent envisager d’autres solutions que ces logiciels.
Mickael Ruau's insight:
Les CMDB, ou bases de données de gestion des configurations, sont apparues comme la source unique de vérité concernant...
Scoop.it!
Most articles on the web tell you to use dotenv to manage environment variables. Now, it has over 6 million weekly downloads. It is not a bad library but it can be confusing, especially for beginners.
Mickael Ruau's insight:
Most cloud services like AWS or Heroku, you will manage all environment variables in their respective consoles. This is good because you don’t store any important credentials locally. More importantly, you will not accidentally start a development server which uses your production data.
(...) If you insist on using dotenv, the correct way is to use preloading."scripts": {"dev": "node -r dotenv/config index.js dotenv_config_path=.env.dev" } Final words: I’m not against using dotenv but I don’t recommend to use require(‘dotenv’) in your code because by default it loads .env and fails silently. Moreover, it becomes more confusing when you have different env files to load.
Scoop.it!
Learn to leverage the tools that will enhance your existing Configuration Management solution.
Mickael Ruau's insight:
To quote Arthur Conan Doyle, "It has long been an axiom of mine that the little things are infinitely the most important." While I usually associate that quote with the toppings I want on my sundae, it rings true for the holistic view of DevOps.
Scoop.it!
 Ansible (logiciel) - WikipédiaAnsible est une plate-forme logicielle libre pour la configuration et la gestion des ordinateurs. Elle combine le déploiement de logiciels multi-nœuds, l'exécution des tâches ad-hoc, et la gestion de configuration. Elle gère les différents nœuds par dessus SSH et ne nécessite l'installation d'aucun logiciel supplémentaire à distance sur eux.
Scoop.it!
In this article I aim to introduce Gulp, as it's fairly new, having been released around 6 months ago. Then, I'll compare it with Grunt, pointing out which tool does what better, and why.
Mickael Ruau's insight:
Grunt wins at teaching people how to do builds, and even then, it's pretty hard to put it in terms anyone can understand, but it fails at keeping it short.
Gulp wins at being terse and having a gorgeous API, but it fails at the entry level, because of streams being hard to grasp at first. In the low-risk low-gain corner we have npm run. It wins at not doing anything, resulting in no overhead, but it fails at being cross-platform, if that's something that worries you.
Make a choice by yourself, don't just pick something because XYZ said so. Pick the tool which works for you. The one you understand, are comfortable with. Above all, the one that fits your needs. Don't go blindly chasing the latest fad because someone else tells you to. Similarly, don't get stuck with monolithic jQuery applications (just to give out an example), try something else. Innovate. Be the change you want to see in the world.
Scoop.it!
Mickael Ruau's insight:
Objectif Périmètre Concepts de base Bénéfices et problèmes possibles Mise en oeuvre et planification Activités Contrôle du processus Interactions avec les autres processus
Scoop.it!
>>Automation of build and release >>Continuous Integration using ANT and Cruise Control >>Features of Cruise Control Using Cruise Control to achieve automatio
Scoop.it!
AnsibleWorks is the company behind Ansible, the radically simple IT orchestration solution that simplifies the way IT departments manage systems, applications, and cloud infrastructure.
Mickael Ruau's insight:
Un équivalent de Chef et Puppet.
"Ansible is a radically simple IT orchestration engine that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications— automate in a language that approaches plain English, using SSH, with no agents to install on remote systems. Ansible is the simplest way to automate and orchestrate: Application Deployment Configuration Management Continuous Delivery"
Scoop.it!
Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
Mickael Ruau's insight:
Setting up and using Salt is a simple task but its capabilities run much, much deeper. These documents will lead to a greater understating of how Salt will empower infrastructure management. REMOTE EXECUTIONRemote execution is the core function of Salt. Running pre-defined or arbitrary commands on remote hosts. ModulesSalt modules are the core of remote execution. They provide functionality such as installing packages, restarting a service, running a remote command, transferring files, and infinitely more. Full list of modulesThe giant list of core modules that ship with SaltWriting modulesA guide on how to write Salt modules.ReturnersSalt returners allow saving minion responses in various datastores or to various locations in addition to display at the CLI. Full list of returnersStore minion responses in Redis, Mongo, Cassandra, SQL or more.Writing returnersExtending Salt to communicate with more interfaces is easy, new databases can be supported or custom interfaces can be easily communicated with.TARGETINGTargeting is specifying which minions should execute commands or manage server configuration. Globbing and regexMatch minions using globbing and regular expressions.GrainsMatch minions using bits of static information about the minion such as OS, software versions, virtualization, CPU, memory, and much more.Node groupsStatically define groups of minions.Compound matchersCombine the above matchers as a single target.Batching executionLoop through all matching minions so that only a subset are executing a command at one time.CONFIGURATION MANAGEMENTBuilding on the remote execution core is a robust and flexible configuration management framework. Execution happens on the minions allowing effortless, simultaneous configuration of tens of thousands of hosts. StatesExpress the state of a host using small, easy to read, easy to understand configuration files. No programming required. Full list of statesInstall packages, create users, transfer files, start services, and much more.Pillar SystemSalt's Pillar systemStates OverviewAn overview of States and some of the core components.Highstate data structureA dry vocabulary and technical representation of the configuration format that states represent.Writing statesA guide on how to write Salt state modules. Extending Salt to directly manage in more software is easy.RenderersWrite state configuration files in the language, templating engine, or file type of choice. Salt's configuration management system is, under the hood, language agnostic. Full list of renderersYAML is not the only choice, many systems are available, from alternative templating engines to the PyDSL language for rendering sls formulas.RenderersSalt states are only concerned with the ultimate highstate data structure. How that data structure is created is not important.MISCELLANEOUS TOPICSSalt is many splendid things. File ServerSalt can easily and quickly transfer files (in fact, that's how Salt States work). Even under heavy load, files are chunked and served.SyndicA seamless master of masters. Scale Salt to tens of thousands of hosts or across many different networks.Peer CommunicationAllow minions to communicate amongst themselves. For example, configure one minion by querying live data from all the others. With great power comes great responsibility.Reactor SystemThe reactor system allows for Salt to create a self aware environment by hooking infrastructure events into actions.Firewall Settings and SaltA tutorial covering how to properly firewall a Salt Master server.Scheduling Executions (like states)The schedule system in Salt allows for executions to be run of all sorts from the master or minion at automatic intervals.Network topologyAt it's core, Salt is a highly scalable communication layer built on top of ZeroMQ that enables remote execution and configuration management. The possibilities are endless and Salt's future looks bright.Testing SaltA howto for writing unit tests and integration tests.Python API interfaceUse Salt programmatically from scripts and programs easily and simply via import salt.Automatic Updates and Frozen Binary DeploymentsUse a frozen install to make deployments easier (Even on Windows!). Or take advantage of automatic updates to keep minions running the latest builds.Windows Software Manager / Package RepositoryLooking for an easy way to manage software on Windows machines? Search no more! Salt has an integrated software package manager for Windows machines! Install software hosted on the master, somewhere on the network, or any HTTP, HTTPS, or ftp server.
Scoop.it!
PHP-CMDB is a webbased Configuration Management Database (CMDB). Based on your own model you can describe configuration items and relations between. Using the ...
Scoop.it!
Découvrez comment installer et utiliser Composer PHP pour inclure des bibliothèques PHP automatiquement.
Mickael Ruau's insight:
Tout comme Nuget pour le language .Net, PHP possède quelques installateurs de bibliothèques, qui installent vos bibliothèques préférées pour vous, tout en gérant les dépendances.
Scoop.it!
Learn what information is needed in your composer.json file and how to list your library on Packagist so others can easily find it.
Mickael Ruau's insight:
By now I’m sure you’ve seen first-hand how Composer can help manage dependencies; I’ve grown quite fond of it myself, using it for the downloadable code samples on GitHub for our articles. Readers can peruse through just the relevant source code on GitHub if they like, and a quick git clone and composer install can get them the code and all the dependencies necessary to play with the code locally. But what about taking it to the next level? You’ve created an awesome library, and now you’re ready to open source it and share it with the world. Hopefully someone else can benefit from your work, and maybe you’ll even receive a bug report or patch to make the library even better. But none of that can happen unless people can find it… and the modern way is increasingly becoming through Composer and Packagist. In this article I’ll show you what information is needed in your composer.json file and how to list your library on Packagist so others can easily find it.
|
TOML shares traits with other file formats used for application configuration and data serialization, such as YAML and JSON. TOML and JSON both are simple and use ubiquitous data types, making them easy to code for or parse with machines. TOML and YAML both emphasize human readability features, like comments that make it easier to understand the purpose of a given line. TOML differs in combining these, allowing comments (unlike JSON) but preserving simplicity (unlike YAML).
Because TOML is explicitly intended as a configuration file format, parsing it is easy, but it is not intended for serializing arbitrary data structures. TOML always has a hash table at the top level of the file, which can easily have data nested inside its keys, but it doesn't permit top-level arrays or floats, so it cannot directly serialize some data. There is also no standard identifying the start or end of a TOML file, which can complicate sending it through a stream. These details must be negotiated on the application layer.
INI files are frequently compared to TOML for their similarities in syntax and use as configuration files. However, there is no standardized format for INI and they do not gracefully handle more than one or two levels of nesting.
Further reading:
Get Involved
Documentation, bug reports, pull requests, and all other contributions are welcome!
Wiki
We have an Official TOML Wiki that catalogs the following: