Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.
Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think.
If you are a junior developer, and want to learn how your more experienced colleagues think, these books are the place to start. If you are an intermediate or senior developer, and want to see how your peers have solved hard design problems, these books can help you too.
Follow us on our blog at http://aosabook.org/blog/ or on Twitter at @aosabook and using the #aosa hashtag.
Sometimes the size of the ondisk transaction area does not fit the update package size and will fail on reboot.
You can circumvent this by extend this area with the command before update and reboot the system:
fsutil resource setlog maxextents 100 C:\Consensus algorithms in their theoretical and applied forms can be difficult to reason about. Often, these algorithms are solutions that have stumbled upon some good problems to solve. Unfortunately, the problems are evolving. And I don’t think these solutions are going to remain relevant much longer. Let’s start with defining the problems they solve:
Distributed Durability: In case of node failures, your data is guaranteed to be elsewhere.
Availability: The ability for the system to continue serving if some nodes have become unavailable.
Automation: If there is a failure, the system knows how to remedy itself without human intervention.It’s truly amazing how little we can achieve in a day, and how much we can achieve in a year. But discipline and patience have always been my Achilles heel, and none of the habit self-help mumbo jumbo seemed to help.
Turns out, I’ve been framing my workouts, learning, and work stuff completely wrong. The goal is not to push yourself to the redline every day — that simply never lasts. The goal is to work so little you have to ask yourself, is that it? And then realize that “if this is so simple, I’ll definitely do this again tomorrow.”
Here’s the concept explained by some of the world’s leading coaches, teachers, and researchers.
Der Werkzeugkasten „Freie Software“ ist im Gegensatz zu den anderen Unterrichtseinheiten kein vorbereitetes didaktisches Konzept zur Durchführung von Unterricht, sondern versteht sich als eine Sammlung von sinnvoller Software, mit der Unterricht in einem digitalen und Zeitalter gestaltet werden kann.
Shaarli Material is a theme for Shaarli, the famous personal, minimalist, super-fast, database free, bookmarking service.
We launched our Backblaze S3 Compatible APIs in May of 2020 and released them for GA in July. After a launch, it’s easy to forget about the hard work that made it a reality. With that in mind, we’ve asked Malay Shah, our Senior Software Engineering Manager, to explain one of the challenges he found intriguing in the process. If you’re interested in developing your own APIs, or just curious about how ours have come to be, we think you’ll find Malay’s perspective interesting.
Meshroom is a free, open-source 3D Reconstruction Software based on the AliceVision framework.
Vim plugin artist
- fugitive.vim: A Git wrapper so awesome, it should be illegal
- pathogen.vim: manage your runtimepath
- commentary.vim: comment stuff out
2014 gegründet, etablierte sich WiRo Motorradtechnik zu DER Anlaufstelle für alle Motorradfahrer, welche auf professionelle Beratung und Top Produkte zu fairen Preisen nicht verzichten wollen.
" Nicht ärgern, sondern anrufen ! "
Professionelle Beratung, TOP - Qualität unserer Produkte und vor allem die Zufriedenheit unserer Kunden stehen bei uns an erster Stelle. Aus diesem Grund sind wir auch an Sonn und Feiertagen für Sie telefonisch erreichbar um eine optimale Kundenbetreuung zu garantieren.
Ganz nach unserem Motto „ Nicht ärgern , sondern anrufen !“
DATAGERRY is an OpenSource CMDB & Asset Management Tool, which completely leaves the definition of a data model to the user
Use DATAGERRY as a central database for automating your IT environment. DATAGERRY can store all the information you need for your operating and push that information to external systems like DNS, ticket system, config management (e.g. Ansible), monitoring system and many more. A push to an external system can be triggered event based, when objects are added, updated or deleted in DATAGERRY.
FUNCTIONALITY
- Object Handling
- File Import & Export
- Exportd – Eventbased Export to external systems
- APIs
- …and many many more on the roadmap
Git push using SSH
git push --set-upstream git@gitlab.example.com:namespace/nonexistent-project.git master
Git push using HTTPS
git push --set-upstream https://gitlab.example.com/namespace/nonexistent-project.git master
Add remote repository
git remote add origin git@gitlab.example.com:namespace/nonexistent-project.git
Reliable Detection with 300 Micron Repeat Accuracy
Key Features:
CMOS Laser Measurement Sensor
Digital Display
200mm to 600mm Sensing Range
300 to 800 Micron Repeat Accuracy
NPN Output with 0 to 5 Volt DC Now with 4-20ma selection option
2 Meter Integral CableIf you’re into DNSSEC, you’ll probably have to troubleshoot or at least to verify it. While there are some good online tools such as DNSViz, there is also a command-line tool to test DNSSEC signatures onsite: delv.
This is an introductory howto to get DNSSEC running with BIND >=9.9 on Debian >=8 (jessie). We assume an "clean", freshly installed bind9 here.
This document provides introductory information on how DNSSEC works, how to configure BIND 9 to support some commonDNSSEC features, as well as some basic troubleshooting tips. The chapters are organized as such:
Chapter 1 covers the intended audience for this document, assumed background knowledge, and a basic introduction to
the topicof DNSSEC.
Chapter 2 covers various requirements that are needed before implementing DNSSEC, such as software
versions, hardwarecapacity, network requirements, and security changes.
Chapter 3 walks through setting up a validating resolver, more information on the validation process, as well as
examples ofusing tools to verify that the resolver is validating answers.
Chapter 4 walks through setting up a basic signed authoritative zone, explains the relationship with the parent zone,
and on-goingmaintenance tasks.
Chapter 5 provides some tips on how to analyze and diagnose DNSSEC-related problems.
Chapter 6 covers several topics, from key generation, key storage, key management, NSEC and NSEC3, to
disadvantages ofDNSSEC.
Chapter 7 provides several working examples of common solutions, with step-by-step details
Ventoy is an open source tool to create bootable USB drive for ISO files.
With ventoy, you don't need to format the disk over and over, you just need to copy the iso file to the USB drive and boot it.
You can copy many iso files at a time and ventoy will give you a boot menu to select them.
Both Legacy BIOS and UEFI are supported in the same way. 200+ ISO files are tested.
A "Ventoy Compatible" concept is introduced by ventoy, which can help to support any ISO file.
See https://www.ventoy.net for detail.
Ansible modules contain documentation in form of YAML blocks documenting the parameters, examples and return values of the module. The Ansible documentation site is built using Sphinx from reStructuredText. As the modules don't contain reStructuredText, Ansible hashad a tool to generate it from the documentation YAML: build-ansible.py document-plugins. The tool and the accompanying libraries are not part of the Ansible distribution - they just live in the hacking directory. To run them we need a git checkout of Ansible and source hacking/env-setup to set PYTHONPATH and a few other variables correctly for Ansible to run directly from that checkout.