375 private links
Une alternative à Docker: pas de deamon, sans privilège root, support des standards OCI comme Docker, intégré avec systemd et une API http.
Podman gère plusieurs conteneurs comme docker compose
Le projet est disponible sur Github https://github.com/containers/podman
Une introduction à Nix afin de recréer des environnements.
On remarque que Nix évite toute la couche OS de Docker.
How to measure web server capacity resource management: here a quick introduction with Rust snippets.
#idea: rewrite it in JS for backend in JS.
Continuant Scribouilli, Ardoise "va télécharger le dépôt fourni, l'analyser et générer le site. Puis, Ardoise publie le site à une adresse correspondant au nom du dépôt. Par exemple, si le dépôt s'appelle "citron", le site sera disponible à l'adresse : https://citron.ardoise.net/"
Ardoise est un outil libre permettant à tout un chacun de publier un site statique en ligne.
Ardoise est un projet né suite au constat qu'énormément de personnes utilisent les outils privateurs Github de Microsoft pour publier des blogs personnels, de la documentation de projets open-source et d'autres choses encore.
Suite à ce constat, le besoin de permettre à ces personnes de s'émanciper de cette nasse logicielle a grandi et les idées parfois floues ont abouties à un projet concret.
Un retour pertinent sur les choix entre PAAS et faire soi-même.
Great insights
It seems to be a lighweight project. It's perfect for small projects!
Setup SSH on a server
Static web publishing for Front-End Developers
That's great to have such simple deployment. Maybe one for rust with such a script or command could be great too.
Or a bash script :)
The author shares its point of view on Shuttle that needs little to nearly 0 configuration to get started.
Zerocal was the first project I deployed on Shuttle. The principle was very simple yet innovative: encode calendar data directly into a URL. [https://endler.dev/2022/zerocal/]
#project #idea improve the UI or make a custom one that calls the API
#project #idea use such API to generate other files. Contacts?
Le jour où je n’aurai plus aucun incident ni anomalie, je considérerai qu’on a mal fait notre travail en surinvestissant dans la qualité par rapport à nos besoins réels.
Et si j’assume d’avoir un risque casser des choses, ce n’est pas déconnant de choisir quand je veux gérer ce risque. La règle de la mise en production du vendredi, pour les équipes qui en ont une, n’est parfois que cela.
Lint Github workflow files
How much uptime guarantees should be needed?
A crash course with further resources
On a 4-core machine, running all our tests sequentially would take 3 days, 15 hours, 10 minutes, and 3 seconds. It’s extremely difficult to run a subset of tests since we’ve built a pure monolith with deeply interwoven concerns, so we run every test on every push of every PR … in only 18 minutes!
Docker-compose is a tool that accepts a YAML file that specifies a cross container application and automates the creation and removal of all those containers without the need to write several docker commands for each one. It should be used for testing and development.
Kubernetes, on the other hand, is a platform for managing production-ready containerized workloads and services that allows for declarative setup as well as automation.
I will read more when I will need it :)
Unit > Integration > E2E is still a valid pyramid for testing; but better can be found.
Static analysis > Unit + Integration > e2e
Static analysis means to check the code without running it. We already have examples with Eslint as a javascript code style fixer; Stylelint for CSS code fixing (I have to try); Sonarqube
Unit and integration tests are mixed together as:
- The definition of a unit is often “to be discussed”: If you ask a group of developers to define a unit, you will mostly get various, differing answers. As some refer to a function, class, or service — minor units — another developer will count in the complete component.
- In addition to those definition struggles, drawing a line between unit and integration can be tricky, as it’s very blurry. This struggle is real, especially for Frontend, as we often need the DOM to validate the test basis successfully.
- It’s usually possible to use the same tools and libraries to write both integration tests. So, we might be able to save resources by merging them.
There are also visual tests. We can group e2e-tests and visual tests into a UI test category. Btw the recommended open-source and fully self-hosted tool for visual testing is Visual Regression Tracker