La fête annuelle des Semences paysannes de Marcilly -le-Chatel est en train d’être organisée. c’est LA fête de la Maison de la Semence de la Loire. Elle se déroulera le samedi 21 mars à partir de 9 heures.

Demandez le programme (ci-dessous) !

Ne ratez pas la Conférence-débat de Marc-André Selosse !

Vivement le printemps!

Azure Local Cluster on‑site working in tandem with Azure Cloud, running Dockerized AI workloads at the edge — is not just viable. It’s exactly the direction modern distributed AI systems are heading.

Let me unpack how these pieces fit together and why the architecture is so compelling.

Azure Local Baseline reference Architecture

A powerful hybrid model for real‑world AI

Think of this setup as a two‑layer AI fabric:

• Layer 1: On‑site Azure Local Cluster
  Handles real‑time inference, local decision‑making, and data preprocessing.
  This is where Docker containers shine: predictable, isolated, versioned workloads running close to the data source.
• Layer 2: Azure Cloud
  Handles heavy lifting: model training, analytics, fleet management, OTA updates, and long‑term storage.

Together, they create a system that is fast, resilient, secure, and scalable

Why this architecture works so well

1. Ultra‑low latency inference

Your on‑site Azure Local Cluster can run Dockerized AI models directly on edge hardware (Jetson, x86, ARM).
This eliminates cloud round‑trips for:

• object detection
• anomaly detection
• robotics control
• industrial automation

Azure Local provides the core platform for hosting and managing virtualized and containerized workloads on-premises or at the edge.

2. Seamless model lifecycle management

Azure Cloud can:

• train new models
• validate them
• push them as Docker images
• orchestrate rollouts to thousands of edge nodes

Your local cluster simply pulls the new container and swaps it in.
This is exactly the “atomic update” pattern from the blogpost.

3. Strong separation of concerns

Local cluster = deterministic, real‑time execution
Cloud = dynamic, scalable intelligence

This separation avoids the classic problem of trying to run everything everywhere.

4. Enterprise‑grade security

Azure Arc, IoT Edge, and Container Registry gives you:

• signed images
• policy‑based deployments
• identity‑bound devices
• encrypted communication

This is critical when edge devices live in factories, stores, or public spaces.

5. Cloud‑assisted intelligence

Even though inference happens locally, the cloud can still:

• aggregate telemetry
• retrain models
• detect drift
• optimize pipelines
• coordinate multi‑site deployments

This is how AI systems improve over time. 

How Docker fits into this hybrid world

Docker becomes the unit of deployment across both environments for DevOps and developers.

On the edge:

• lightweight images
• Hardened images
• GPU‑enabled containers
• read‑only root filesystems
• offline‑capable workloads

In the cloud:

• CI/CD pipelines
• model registries
• automated scanning
• versioned releases

The same container image runs in both places — but with different responsibilities.

My take: This is one of the strongest architectures for real‑world AI

If your goal is:

• real‑time AI
• high reliability
• centralized control
• scalable deployments
• secure operations
• hybrid cloud + edge synergy

…then Azure Local Cluster + Azure Cloud + Docker AI Edge is a near‑ideal solution.

It gives you the best of both worlds:
cloud intelligence + edge autonomy.

Here you find more about Microsoft Azure Local 

Here you find more blogposts about Docker, Windows Server 2025, and Azure Cloud Services :

Windows Server 2025 Core and Docker – A Modern Container Host Architecture

Docker Desktop Container Images and Azure Cloud App Services

The Rise of Free Hardened Docker Images: A New Security Baseline for Developers and DevOps

Containerization has become the backbone of modern software delivery. But as adoption has exploded, so has the attack surface. Vulnerable base images, outdated dependencies, and misconfigured runtimes have quietly become some of the most common entry points for supply‑chain attacks.

The industry has been asking for a better baseline—something secure by default, continuously maintained, and frictionless for teams to adopt. And now we’re finally seeing it: free hardened Docker images becoming widely available from major vendors and open‑source security communities.

This shift isn’t just a convenience upgrade. It’s a fundamental change in how we think about container security.

Why Hardened Images Matter More Than Ever

A “hardened” image isn’t just a slimmer version of a base OS. It’s a container that has been:

• Stripped of unnecessary packages
  Fewer binaries = fewer vulnerabilities.
• Built with secure defaults
  Non‑root users, locked‑down permissions, and minimized attack surface.
• Continuously scanned and patched
  Automated pipelines ensure CVEs are fixed quickly.
• Cryptographically signed
  So you can verify provenance and integrity before deployment.
• Aligned with compliance frameworks
  CIS Benchmarks, NIST 800‑190, and other standards are increasingly baked in.

For developers, this means fewer surprises during security reviews. For DevOps teams, it means fewer late‑night patch cycles and fewer emergency rebuilds.

What’s New About the Latest Generation of Free Hardened Images

The newest wave of hardened images goes far beyond the “minimal OS” approach of the past. Here’s what’s changing:

1. Hardened Language Runtimes

We’re seeing secure-by-default images for:

• Python
• Node.js
• Go
• Java
• .NET
• Rust

These images often include:

• Preconfigured non‑root users
• Read‑only root filesystems
• Mandatory access control profiles
• Reduced dependency trees

2. Automated SBOMs (Software Bills of Materials)

Every image now ships with a machine‑readable SBOM.
This gives you:

• Full visibility into dependencies
• Faster vulnerability triage
• Easier compliance reporting

SBOMs are no longer optional—they’re becoming a standard part of secure supply chains.

3. Built‑in Image Signing and Verification

Tools like Sigstore Cosign, Notary v2, and Docker Content Trust are now integrated directly into image pipelines.

This means you can enforce:

• “Only signed images may run” policies
• Zero‑trust container admission
• Immutable deployment guarantees

4. Continuous Hardening Pipelines

Instead of waiting for monthly rebuilds, hardened images are now updated:

• Daily
• Automatically
• With CVE‑aware rebuild triggers

This dramatically reduces the window of exposure for newly discovered vulnerabilities.

Read the complete blogpost about a Safer Container Ecosystem with Docker: Free Docker Hardened Images here

Docker Desktop continues to evolve as the go-to platform for containerized development, and the latest release — version 4.51.0 — brings exciting new capabilities for developers working with Kubernetes.

What’s New in 4.51.0

1. Kubernetes Resource Setup Made Simple

One of the standout features in this release is the ability to set up Kubernetes resources directly from a new view inside Docker Desktop. This streamlined interface allows developers to configure pods, services, and deployments without leaving the Desktop environment. It’s a huge step toward making Kubernetes more approachable for teams who want to focus on building rather than wrestling with YAML files.

2. Real-Time Kubernetes Monitoring

The new Kubernetes view also provides a live display of your cluster state. You can now see pods, services, and deployments update in real time, making it easier to spot issues, monitor workloads, and ensure everything is running smoothly.

3. Smarter Dependency Management

Docker Desktop now integrates improvements with Kind (Kubernetes in Docker), ensuring that only required dependency images are pulled if they aren’t already available locally. This reduces unnecessary downloads and speeds up cluster setup.

4. Updated Core Components

• Docker Engine v28.5.2 ships with this release, ensuring stability and performance improvements.
• Enhanced Linux kernel support for smoother Kubernetes operations.

Why This Matters

Kubernetes has a reputation for being complex for some people, but Docker Desktop 4.51.0 is working to change that. By embedding Kubernetes resource management and monitoring directly into the Desktop experience, Docker is lowering the barrier to entry for developers and teams. Whether you’re experimenting with microservices or managing production-like environments locally, these new features make Kubernetes more accessible and intuitive.

Getting Started

To try out these new features:

1. Update to Docker Desktop 4.51.0.
2. Open the new Kubernetes view to configure resources.
3. Watch your pods, services, and deployments update in real time.

Update available with New Kubernetes UI
Click on Download Update

Click on Create Cluster

Here you can select a Single Node Cluster or with Kind a Multi-Node Cluster.
I selected for a Single node cluster.

Click on Install

Here is your Single Node Kubernetes Cluster running with version 1.34.1

Kubectl get nodes

My Nginx Container app is running on Kubernetes in Docker Desktop

Final Thoughts

Docker Desktop 4.51.0 is more than just an incremental update — it’s a meaningful step toward bridging the gap between container development and Kubernetes orchestration. With simplified setup and real-time monitoring, developers can spend less time configuring and more time innovating.

Here you find more information about Docker Desktop and Kubernetes Clustering

 

Docker Desktop and Azure App Cloud Services

Expanded Architecture: Docker developer environment with Azure Cloud Services.

Development Environment

• Docker Desktop + Tools: Visual Studio Code, Azure CLI, Docker Scout, AI, MCP
• Docker Scout CLI: Compares image versions, detects CVEs, integrates with pipelines

Container Host (Windows Server 2025 Core)

• Hyper-V Isolated Containers: For enhanced security
• Workloads: Microservices, legacy apps, AI containers
• GitOps Operator: Automated deployment via Git repositories
• Azure Arc Agent: Connects on-prem host to Azure Control Plane

Here you find more information about Docker on Windows Server 2025 Core

Your Windows 11 Laptop with Docker Desktop

• Hyper-V / WSL2: for your containers development
• Azure Arc Agent: for your Azure Cloud Services and security
• Docker Desktop for Windows installed

Azure Cloud Integrations

Component	Function
Azure App Service (Docker)	Hosts web apps as Docker containers with autoscaling and Key Vault integration
Azure DevOps + Pipelines	CI/CD for image build, scan, push, and deployment
Azure Copilot Security	AI-driven security recommendations and policy analysis
Azure Container Registry (ACR)	Secure storage and distribution of container images
Azure Key Vault	Secrets management: API keys, passwords, certificates
Microsoft Defender for Cloud	Runtime protection, image scanning, threat detection
Azure Policy & RBAC	Governance and access control
Azure Monitor + Sentinel	Logging, metrics, threat detection
Azure Update Manager	Hotpatching of Windows and container images without reboot

More information on Strengthening Container Security with Docker Hardened Images and Azure Container Registry

DevSecOps Workflow

1. Build & Harden Image → Dockerfile + SBOM
2. Scan with Docker Scout → CLI or pipeline
3. Push to ACR → With signing and RBAC
4. Deploy via Azure DevOps Pipelines → App Service or Arc-enabled host
5. Inject Secrets via Key Vault → Automatically at runtime
6. Monitor & Patch → Azure Monitor + Update Manager
7. Audit & Alerting → Azure Sentinel + Defender
8. Security Guidance → Copilot Security analyzes policies and offers recommendations

Example of Deploying a custom container to Azure App Service with Azure Pipelines

Microsoft Azure App Service is really scalable for Docker App Solutions:

Azure App Service is designed to scale effortlessly with your application’s needs. Whether you’re hosting a simple web app or a complex containerized microservice, it offers both vertical scaling (upgrading resources like CPU and memory) and horizontal scaling (adding more instances). With built-in autoscaling, you can respond dynamically to traffic spikes, scheduled workloads, or performance thresholds—without manual intervention or downtime.

From small startups to enterprise-grade deployments, App Service adapts to demand with precision, making it a reliable platform for modern, cloud-native applications.

Scale Up Features and Capacities Learn how to increase CPU, memory, and disk space by changing the pricing tier

Enable Automatic Scaling (Scale Out) Configure autoscaling based on traffic, schedules, or resource metrics

Per-App Scaling for High-Density Hosting Scale individual apps independently within the same App Service Plan

Conclusion

For modern developers, the combination of Azure App Services and Docker Desktop offers a powerful, flexible, and scalable foundation for building, testing, and deploying cloud-native applications.

• Developers can build locally with Docker, ensuring consistency and portability.
• Then deploy seamlessly to Azure App Services, leveraging its cloud scalability and integration.
• This workflow reduces configuration drift, accelerates testing cycles, and improves team collaboration.

Dix ans ont passé.
Nous en sommes à la onzième édition de la Fête des semences paysannes de la MS Loire.
Cette année, elle aura lieu le samedi 29 mars à partir de 9h, à Marcilly-le-Chatel comme d’habitude.

Le programme est très divers, comme d’habitude, avec un point fort : la conférence sur les plantes bio-indicatrices, par Delphine SUZOR qui nous initiera à la méthode de diagnostic des sols à partir des plantes qui poussent spontanément dans nos jardins.

Il y aura aussi :
– de la restauration sur place (mais attention, il faut prendre son ticket assez tôt car nos visiteurs ont vite fait de liquider le stock de repas disponibles)
– des ateliers tri de semences et taille de fruitiers
– un débat, bien actuel, sur agricultures et labels, avec des professionnels
– un marché de producteurs
– des semenciers professionnels artisanaux et des pépiniéristes
– des semenciers amateurs qui vous proposent quelques échantillons de leur production
– un grand troc de semences le matin
– une librairie et des stands associatifs, etc …

Consultez le détail :

On espère vous voir nombreux et nombreuses !

Docker Desktop main screen

In the ever-evolving world of software development, Docker Desktop for Windows has emerged as an indispensable tool for developers. This powerful platform simplifies the process of building, sharing, and running applications within containers, offering a host of features and benefits that streamline workflows and enhance productivity. Let’s dive into what makes Docker Desktop for Windows a must-have for developers.

Easy Installation and Setup

One of the standout features of Docker Desktop for Windows is its straightforward installation process. With just a few clicks, developers can have Docker up and running on their Windows machines. The intuitive setup ensures that even those new to Docker can get started without a hitch.

Integrated GUI

Docker Desktop comes with a user-friendly Graphical User Interface (GUI) that makes managing containers, images, and settings a breeze. The GUI provides a visual representation of your Docker environment, allowing you to easily monitor and control your containers without needing to rely solely on command-line instructions.

Seamless Integration with WSL 2

For developers working with both Windows and Linux containers, Docker Desktop offers seamless integration with Windows Subsystem for Linux 2 (WSL 2). This integration allows you to switch between Linux and Windows containers effortlessly, leveraging the best of both worlds. WSL 2 provides a lightweight Linux kernel that runs alongside your Windows OS, ensuring optimal performance and compatibility.

Resource Management

Docker Desktop includes robust resource management features, enabling developers to allocate CPU, memory, and disk resources to their containers. This ensures that your development environment remains responsive and efficient, even when running multiple containers simultaneously.

Automatic Updates

Docker Desktop Automatically check for updates.

Keeping your Docker environment up-to-date is crucial for security and performance. Docker Desktop simplifies this process with automatic updates, ensuring that you always have the latest features and security patches without manual intervention.

Docker Compose Integration

Docker Compose is a powerful tool for defining and running multi-container Docker applications. Docker Desktop integrates seamlessly with Docker Compose, allowing developers to easily manage complex applications with multiple services. This integration simplifies the orchestration of containers, making it easier to develop, test, and deploy applications.

Kubernetes Support

For developers looking to dive into the world of Kubernetes, Docker Desktop offers built-in support for Kubernetes. This feature allows you to run a single-node Kubernetes cluster on your local machine, providing a convenient environment for learning and experimentation. With Kubernetes support, you can develop and test containerized applications before deploying them to a production cluster.

Volume Management

Docker Desktop Volumes management

Managing data within containers is made simple with Docker Desktop’s volume management capabilities. You can easily create, manage, and share volumes between containers, ensuring that your data persists across container restarts and updates.

Benefits for Developers

Enhanced Productivity

Docker Desktop Dev Environments

Docker Desktop streamlines the development process by providing a consistent environment across different stages of development. This consistency reduces the “it works on my machine” problem, ensuring that applications run smoothly from development to production.

Simplified Collaboration

With Docker Desktop, sharing your development environment with team members is as simple as sharing a Docker image. This ensures that everyone on your team is working with the same setup, reducing discrepancies and improving collaboration.

Flexibility and Portability

Docker containers are inherently portable, allowing you to run your applications on any system that supports Docker. This flexibility is particularly beneficial for developers working in diverse environments or deploying applications across different platforms.

Improved Security

Docker Desktop Scout

Docker Desktop provides a secure environment for running containers, isolating applications from the host system and each other. This isolation reduces the risk of security vulnerabilities and ensures that your development environment remains protected.

Conclusion

Docker Desktop for Windows is a game-changer for developers, offering a comprehensive suite of features that enhance productivity, simplify collaboration, and improve security. Whether you’re a seasoned developer or just starting with containerization, Docker Desktop provides the tools you need to build, share, and run applications with ease. Embrace the power of Docker Desktop and take your development workflow to the next level.

Here you find more information about Docker Desktop:

The Website of Docker Desktop

Docker Desktop Documentation

Skill up with Docker

Whalecome to the Docker Community

Docker in VSCode

Happy coding!

Exploring Docker Desktop Dev Environments (Beta)

In the ever-evolving landscape of software development, Docker has consistently been at the forefront, providing developers with tools to streamline their workflows. One of the latest additions to Docker’s suite of tools is the Docker Desktop Dev Environments (Beta). This feature promises to revolutionize the way developers collaborate and manage their development environments. Let’s dive into what makes this new feature so exciting.

What is Docker Desktop Dev Environments?

Docker Desktop Dev Environments is a feature designed to simplify the process of setting up and sharing development environments. It allows developers to create, configure, and share their development setups with ease, ensuring consistency across different machines and team members. This is particularly useful in collaborative projects where maintaining identical environments can be challenging.

Key Features

• Environment Configuration: With Docker Desktop Dev Environments, you can define your development environment using a simple configuration file. This file includes all the necessary dependencies, tools, and settings required for your project. Once defined, the environment can be easily replicated on any machine with Docker Desktop installed.
• Seamless Sharing: Sharing your development environment with team members has never been easier. Docker Desktop Dev Environments allows you to package your environment configuration and share it via a URL or a file. Team members can then import this configuration and have their environment set up in minutes.
• Consistency and Reproducibility: One of the biggest challenges in software development is ensuring that all team members are working in the same environment. Docker Desktop Dev Environments addresses this by providing a consistent setup that can be easily reproduced. This reduces the “it works on my machine” problem and ensures that everyone is on the same page.
• Integration with Docker Hub: Docker Desktop Dev Environments integrates seamlessly with Docker Hub, allowing you to store and manage your environment configurations in the cloud. This makes it easy to access and share your environments from anywhere.

Benefits for Developers

• Simplified Onboarding: New team members can get up and running quickly by importing the development environment configuration. This reduces the time spent on setting up and troubleshooting environments.
• Enhanced Collaboration: By providing a consistent environment, Docker Desktop Dev Environments fosters better collaboration among team members. Everyone works with the same tools and settings, reducing discrepancies and integration issues.
• Improved Productivity: With a standardized environment, developers can focus more on coding and less on environment setup and maintenance. This leads to increased productivity and faster development cycles.

Getting Started

To get started with Docker Desktop Dev Environments (Beta), follow these simple steps:

1. Install Docker Desktop: Ensure you have the latest version of Docker Desktop installed on your machine.
2. Create a Dev Environment: Use the Docker Desktop interface to create a new development environment. Define your environment configuration using the provided templates or create your own.
3. Share Your Environment: Once your environment is set up, share it with your team by generating a URL or exporting the configuration file.
4. Import an Environment: Team members can import the shared environment configuration and have their setup ready in minutes.

In the following steps I will Create a Dev Environment in Docker Desktop for Windows:

Click on Dev Environments and then on Get Started

Give your environment a Name, select your source and choose your IDE,
Click then on Continue

Preparing and creating.

Click on Continue

You’re all set and you can open VSCode or your IDE.

Your Dev Environment in Docker Desktop for Windows.

Your Docker Desktop for Windows Dev Environment in VSCode.

Your Dev environment microservices running in Docker Desktop

 

Conclusion

Docker Desktop Dev Environments (Beta) is a game-changer for developers looking to streamline their workflows and enhance collaboration. By providing a consistent, reproducible, and easily shareable development environment, Docker is once again proving its commitment to making developers’ lives easier. Whether you’re working on a solo project or collaborating with a large team, Docker Desktop Dev Environments is a tool worth exploring.
Here you find more information about Dev environments at Docker.

Happy coding!

Docker for Windows Update

When you want to work with containers and Microsoft Visual Studio Code
Docker Desktop for Windows is awesome to work with on your pc. Docker Desktop is a one-click-install application for your Mac, Linux, or Windows environment that lets you build, share, and run containerized applications and microservices. You can work with docker container images from Hub here
But you can also work with Docker Desktop for Windows Kubernetes containers.
I like to work with Docker Desktop for Windows because it’s easy to manage and updates works fine with good documentation on fixes and changes.

Software Updates Overview

Installing New Update 4.33.1

Unpacking Files

Starting New docker Engine

Docker Desktop for Windows and Kubernetes are running again.

Docker Desktop for Windows is up-to-date.

What’s New in this Release.
Here you find the Release notes from Docker

Okay but what is next? Here you find the Docker road map

 

C’est pourquoi, cette année, nous n’avons jusqu’ici été cultiver à Goely que deux fois : le 12 avril et le 10 mai. Nous avons réussi à passer entre les gouttes et le terrain n’était pas trop mouillé.

A la fin de ce petit résumé, vous trouverez
– un rappel des fiches conseils pour produire de bonnes graines.
– des infos sur les distributions de plants de tomates à St Etienne et à Marcilly-le-Chatel.

Le 12 avril, JL nous avait préparé deux belles planches. Cette année nous avons décidé d’adopter ce mode de culture. 1,20m de large, accessible des deux cotés, destiné à devenir des planches permanentes avec enrichissement régulier du sol. Nous y avons semé les bulbes d’oignon patate, notre oignon fétiche.

Quant à la serre, un joyeux fouillis nous y attendait. Nous avons tuteuré le chou quintal d’Auvergne ; c’est la première fois que nous cultivons un chou pour la graine, on va voir ce qu’on va voir.
Sinon, nous avons repiqué en godets les 13 variétés de tomates que nous avions sélectionnées et semées en alvéoles à Annonay le 25 mars.

Le 10 mai, les oignons patate s’étaient bien développés ; ils n’ont certes pas manqué d’eau, mais n’ont pas pourri pour autant. Ils forment un joli alignement et ont été sarclés avec soin.
Nous avons pu planter une partie des tomates, celles qui avaient suffisamment grandi, idem pour les laitues.
Pendant qu’une partie de l’équipe faisait tout ça, quelques bras solides ont bêché à la grelinette le sol de la serre, pour y accueillir bientôt haricots, poivrons et courgettes.

Pour celles et ceux qui veulent récolter leurs graines dans les ‘règles de l’art’, il y a un outil précieux : les fiches semences du blog de la MS Loire :https://msloirepilat.wordpress.com/fiches-semences/. On y trouve des conseils pour produire des graines de toutes les familles de légumes. A déguster sans modération !

Au bas de cette page de liens il y a, par exemple, une fiche ‘produire des graines de haricots’. C’est pas long à lire et ça évite qq erreurs. On y insiste sur :
– prévoir des pieds réservés exclusivement à la production, où on ne cueille pas de haricots (prévoir rubalise ou laine rouge pour les marquer et s’en souvenir), sauf les frais en fin de saison (à partir de septembre, ça repart si les pieds ne sont pas morts de chaleur).
– planter les différentes variétés à un certain éloignement, pour éviter qu’elles ne se croisent.
– récolter des grains parfaitement secs, la cosse est cassante.
– et je rajouterai mon dada, la protection la plus efficace que je connaisse pour protéger des limaces bien gourmandes et nombreuses en ce moment : semer les haricots en poquets et les entourer d’un tronçon de bouteille plastique (8-10 cm de haut). Par sécurité, j’y mets dans ce cercle protégé quelques grains d’anti-limaces à base de fer (non toxique pour les humains).

Je nous souhaite bien du plaisir au jardin et un peu plus de soleil.

On ne fait pas que transpirer, à Goély, à notre terrain de culture collective. On travaille aussi avec notre tête, pour faire le bilan de l’année écoulée et prévoir la suite.
D’ailleurs, qui croit encore que l’intellect fonctionne séparément du ‘corps’, et lui est supérieur ?
Comme un des carburants de notre collectif est le bon boire et le bon manger, ça donne la scène ci-dessus.

Au programme de ce billet :
– la Fête de Reventin (38), le 3 mars, où nous tenons un stand de la grainothèque du Pilat
– Notre Fête des semences paysannes de Marcilly-le-Chatel (42), le 23 mars.
– Un article sur la souveraineté alimentaire, contribution au débat sur les mutations nécessaires dans l’agriculture.
– Et un autre article sur les plateformes numériques dans le domaine des semences.

Tout sur la Fête Nature de Reventin(38) du 3 mars de 9h à 13h : https://www.entrezcestouvert.fr/.
On y sera avec nos échantillons de graines à donner, et retrouver nos amis dans une ambiance tout spécialement chaleureuse.

Veuillez trouvez ici le tract-programme de la 10ème fête des semences paysannes, organisée par la Maison de la Semence de la Loire, le samedi 23 mars 2024 à la ferme Grenier à Marcilly Le Châtel dans le Forez.
Merci de nous aider à en faire connaître largement le programme, par mails et sur les réseaux sociaux !

Lisez ici l’article sur la souveraineté alimentaire, alibi de ceux qui ne veulent rien changer dans les pratiques (juteuses pour eux) de l’agroindustrie, et les alternatives en lien avec le respect des équilibres naturels.

Un autre article de fond sur le risque d’uberisation dans la production des semences. Le terme ‘uberisation’ est un peu accrocheur, mais l’article est intéressant. Extrait :
“Éléments pour une critique des plateformes numériques appliquées aux semences.
L’agriculture n’échappe pas à la numérisation du monde. L’intégration des objets connectés aux pratiques agricoles est un nouvel eldorado pour l’industrie.” La suite est là.

Et vive le printemps!

The internal name of a SharePoint column is a unique name that is automatically generated by SharePoint when a column is created. It is used by SharePoint internally to reference and retrieve the value of a particular column associated with an item or document. The internal name is generated based on the display name you provide but all special characters and spaces will be replaced with Unicode’s by SharePoint. Internal name is generated only once while creating a new column and it cannot be changed even if you change the display name of SharePoint column.

The internal name is not visible to users in the SharePoint user interface by default, but it is commonly used in various scenarios, such as in SharePoint REST APIs, Power Automate flow expressions, Power Apps formulas, PowerShell, etc. to interact with column data programmatically.

Where are Internal names of SharePoint columns used?

1. Custom Scripts: When creating custom scripts, such as JavaScript or PowerShell, the internal names of columns are required to reference and manipulate the values of the columns while interacting with SharePoint data.
2. Workflows: In SharePoint Designer workflows or Microsoft Power Automate (formerly known as Microsoft Flow), the internal names of columns are used to reference the values of the columns as inputs or outputs in the workflow actions and in expressions.
3. Custom Solutions: When building custom solutions, such as SharePoint apps, SharePoint framework (SPFx) web parts, or custom code, the internal names of columns are required to interact with the columns programmatically.
4. Power Apps: Few of the Power Apps functions like ShowColumns, SortByColumns, etc. requires using internal names of SharePoint columns in formula.
5. JSON Formatting: Internal name of SharePoint column is required in JSON formatting to reference the column value with [$InternalNameOfColumn] syntax.

How to find the Internal name of a SharePoint column?

Using Modern experience list view

You can use sorting or filtering options from SharePoint online modern experience list view to find the internal name of a SharePoint column. Sort by and Filter by options are supported by most of the column types in SharePoint like Single line of text, Choice, Number, Date and Time, Yes/No (Boolean), Person or Group (single selection), etc.

For this afticle, we will use sorting based on SharePoint choice column as an example:

1. Go to the SharePoint online list for which you want to check the internal name of a column.

2. Click on column name/header from the list view and select either Ascending (A to Z) or Descending (Z to A) option from the popup menu:

3. SharePoint will sort the list view based on selection and the browser URL will be changed like:

https://contoso.sharepoint.com/sites/wlive/Lists/InternalNames/AllItems.aspx?sortField=ChoiceColumn&isAscending=false

Where column name (ChoiceColumn) after sortField= is the internal name of your SharePoint choice column.

4. Similarly, when you use Filter by option in SharePoint modern experience to filter the list view based on Date and Time column (named as Start Date), SharePoint changes browser URL like:

https://contoso.sharepoint.com/sites/wlive/Lists/InternalNames/AllItems.aspx?FilterField1=Start_x0020_Date&FilterValue1=2023-04-05&FilterType1=DateTime

Where column name (Start_x0020_Date) after FilterField1= is the internal name of your SharePoint date and time column. Notice _x0020_ in internal column name which is an Unicode encoding of the space character in the display name of date and time column (Start Date).

Using Classic experience List settings page

Few of the SharePoint column types like Multiple lines of text, Hyperlink or Picture, Image, etc. does not support sorting or filtering from SharePoint modern experience list views. So, you have to use the classic experience list settings page to find the internal name for such SharePoint columns.

Follow below steps to find the internal name of multiple lines of text column using SharePoint classic experience list settings page:

1. Go to the SharePoint online list for which you want to check the internal name of a column.

2. Click on Settings (gear) icon from the top right corner and select List settings:

3. From list settings page, scroll down to the Columns section and click on the column name for which you want to find the internal name:

4. SharePoint will open column settings page for the respective column with browser URL like:

https://contoso.sharepoint.com/sites/wlive/_layouts/15/FldEdit.aspx?List=%7B6FBA7FAE-AFC0-45D6-99EE-0AB20629EE41%7D&Field=MultilineTextCol

Where column name (MultilineTextCol) after Field= is the internal name of your SharePoint online multiple lines of text column.

Note: You can use this classic experience method to find out the internal name of SharePoint columns for all column types.

Using SharePoint REST API

You can use SharePoint REST API endpoint like below to get the internal name of SharePoint column based on it’s display name. Open URL in below format directly from browser tab:

https://contoso.sharepoint.com/sites/SPConnect/_api/web/lists/getbytitle('InternalNames')/fields?$select=Title,InternalName&$filter=Title eq 'Multiline Text Column'

Using PnP PowerShell

You can use below PnP PowerShell script to find the internal name of SharePoint online list column using PnP PowerShell:

# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"

# Display name of SharePoint list
$listName = "InternalNames"

# Display name of SharePoint list column
$columnName = "Multiline Text Column"
 
# Connect to SharePoint online site
Connect-PnPOnline -Url $siteUrl -Interactive
 
# Get internal name of SharePoint list column
Get-PnPField -Identity $columnName -List $listName | Select Title,InternalName

Using CLI for Microsoft 365

You can use below CLI for Microsoft 365 script to find the internal name of SharePoint online list column using CLI for Microsoft 365:

# SharePoint online site URL
$siteUrl = "https://contoso.sharepoint.com/sites/wlive"

# Display name of SharePoint list
$listName = "InternalNames"

# Display name of SharePoint list column
$columnName = "Multiline Text Column"
 
# Get Credentials to connect
$m365Status = m365 status
if ($m365Status -match "Logged Out") {
	m365 login
}

# Get internal name of SharePoint list column
m365 spo field get --webUrl $siteUrl --listTitle $listName --title $columnName --output text

Best practices for naming SharePoint columns

When creating columns in SharePoint, it’s important to follow best practices for column naming to avoid using special characters or Unicode characters in internal names. Here are some recommended best practices:

1. Use only alphanumeric characters: Stick to using letters (A-Z, a-z) and numbers (0-9) in column names. Avoid using special characters such as @, #, $, %, _, etc. Avoid column names beginning with numbers.
2. Avoid spaces: Use PascalCase to separate words in column names instead of spaces. For example, use ColumnName instead of Column Name. This can help prevent issues with URLs, Unicode encoding, and referencing column names in scripts or code.
3. Avoid reserved words: SharePoint has reserved words that are used for system functionality, and using them in column names may cause conflicts. Examples of reserved words include “ID”, “Modified”, “Created”, “Title”, etc. Avoid using these reserved words as column names.
4. Keep it concise and meaningful: Use descriptive and meaningful names for columns that clearly indicate their purpose. Avoid using vague or generic names that may be confusing or ambiguous to users. Use column description to provide more information about the columns.
5. Be consistent: Establish a consistent naming convention for columns across your SharePoint site or site collection to ensure uniformity and ease of management. This can also help with documentation, training, and maintenance of your SharePoint environment.

I hope you liked this article. Give your valuable feedback & suggestions in the comments section below and share this article with others.

Learn more

• SharePoint Online: Apply JSON View formatting using SharePoint REST API
• Change SharePoint Online List URL using PnP PowerShell
• SharePoint Online: Download files using JSON Formatting
• Create a SharePoint online site using Power Automate flow

In this blog we will explore the SharePoint spaces, it’s history & roadmap and how to enable SharePoint spaces in a SharePoint online site.

What’s SharePoint Spaces

As per the Microsoft documentation, SharePoint spaces is defined as:

“SharePoint spaces is a web-based, immersive platform, which lets you create and share, secure and extensible mixed reality experiences. Add a new dimension to your intranet by using 2D and 3D web parts to create your mixed reality vision.”

SharePoint Spaces allows users to easily build mixed reality experiences that interact with content stored in SharePoint Online.

SharePoint spaces empower creators to build immersive mix reality experiences with point-and-click simplicity. You can get started with smart templates to create a mixed reality environment complete with beautiful surroundings, ambient sounds, rich textures, and lighting. You then add content, which can include files you already have in SharePoint, allowing you to repurpose your existing data, documents, and images.

History & Roadmap

• Microsoft announced SharePoint Spaces first time during its annual SharePoint Virtual Summit held in May 2018.
• Microsoft announced SharePoint spaces public preview in April 2020, Roadmap.
• Microsoft added 360° tour web part in SharePoint spaces which allows creation of immersive virtual tours for SharePoint sites, Roadmap.
• Microsoft added touch device support in SharePoint spaces which enables users to interact with a space using touch interactions in addition to the mouse and keyboard-based interactions, Roadmap.
• Microsoft announced General Availability of SharePoint spaces, Roadmap.

That’s it for SharePoint spaces introduction and history. Let’s see how you can enable SharePoint spaces in your SharePoint online site to get started with it.

Enable SharePoint spaces in a site

SharePoint spaces are not enabled by default in SharePoint online site. To use SharePoint spaces, we need to enable a site feature named “Spaces”.

You can activate this feature using any one of the methods given below:

Manually:

You can activate Spaces feature from user interface by navigating to Manage site features page.

Hit (URL: https://tenant.sharepoint.com/sites/siteName/_layouts/ManageFeatures.aspx) in browser tab by replacing tenant and siteName or follow below steps:

1. Go to SharePoint site where you want to build a space
2. Click on Settings (gear icon), select Site information and then select View all site settings.
3. On the Site settings page, select Manage site features under Site Actions.
4. Scroll down the page to Spaces feature and click on Activate button.
5. Wait till the page refreshes and confirm that feature is activated successfully.

Using PnP PowerShell:

You can easily activate features in SharePoint online using PnP PowerShell. To activate a site feature using PnP PowerShell you will need the GUID of feature. Check how you can quickly get the GUID of a site feature. GUID of Spaces feature is 2ac9c540-6db4-4155-892c-3273957f1926.

Use below command to activate Spaces feature:

Enable-PnPFeature -Identity 2ac9c540-6db4-4155-892c-3273957f1926 -Scope Web

You can find the detailed example of how to activate a site feature in SharePoint Online using PnP PowerShell here.

To get an idea about what you can do using SharePoint spaces, check out some of the awesome samples here.

See also

• SharePoint spaces to be available by default in New menu
• Introducing Embed web part in SharePoint spaces

Tech giant Microsoft is introducing Embed web part in SharePoint spaces which will allow users to show SharePoint pages or HTML page embed content as an interactable overlay on a SharePoint space. Space viewers will see a thumbnail image in the 3D space that can be viewed as a fully functional HTML overlay when selected by the user. Space viewers that are using a mixed reality headset will only see the thumbnail when selecting the web part unless they return to the browser to interact with the embedded content.

This new feature release will allow users to add content such as:

• Microsoft Forms
• The PowerPoint embed viewer
• SharePoint Pages
• Power Apps

This message is associated with Microsoft 365 Roadmap ID 70732.

Release Timeline

• Targeted release (selected users and entire organization): Roll out will begin in early November and expect to be complete by mid-November.
• Standard release: Roll out will begin in mid-November and expect to be complete by late November.

How this will affect your organization

SharePoint spaces authors will see a new embed web part available in the spaces web part toolbox while designing a SharePoint space.

SharePoint spaces authors will see embed web part as shown in below image:

What you need to do to prepare

You might want to notify your users about this new capability and update your training documentation as appropriate.

Learn more

• SharePoint spaces
• SharePoint spaces to be available by default in New menu

Inline message translation is a Microsoft Teams feature that allow users to translate Teams messages into the language specified by their personal language settings. This nice feature is already available in Microsoft Teams Desktop client and web.

Now, Microsoft is releasing the inline message translation feature for Microsoft Teams iOS and Android apps which will allow users to translate channel posts that are in another language, into the language of their choice. Microsoft will make this feature available to iOS and Android users with the latest app store updates starting from early June to mid-July.

How this works?

After updating the Microsoft Teams app from app store, end users will be able to translate channel posts into their preferred language while working on their Android and iOS devices.

To translate the channel post or reply, user has to press and hold the message and then select Translate. The post/reply will be translated to the language specified by their personal language settings. To return a translated message to the original language, press and hold the translated message and then select See original (language).

How to set the translation language?

To set the preferred language that you want messages translated to, go to Settings –> select Translation and then choose the desired language under Translate messages into this language.

How to Turn on/off inline message translation in Microsoft Teams?

The ability to translate messages will be on by default in Microsoft Teams. If you want to turn off the inline message translation in Microsoft Teams or if you have turned it off previously & now you want to turn it on, follow below steps:

1. Go to Microsoft Teams admin center
2. Select Messaging Policies from the left navigation
3. Either create a new policy or edit an existing policy
4. Set the Translate messages option to On/Off

You can also turn on/off inline message translation in Microsoft Teams using PowerShell command Set-CsTeamsMessagingPolicy. You need to set the -AllowUserTranslation parameter to true to allow users to translate messages & false to prohibit users from translating messages in Microsoft Teams.

Example

Set-CsTeamsMessagingPolicy -Identity MyMessageTranslationPolicy -AllowUserTranslation $false

Note

The Microsoft Teams policy takes few minutes to apply. Sometimes users might need to sign out and sign back in to Microsoft Teams.

Bonjour Notre organisation disposait et dispose toujours de licence Azure P2 pour, en autre chose, mettre en place la revue des accés (Access Review) sur les équipes Microsoft Teams et notamment les comptes invités. Cependant la venue des nouvelles licences Entra modifie quelque peu la donne. Voici ce que l’on peut lire lorsque l’on tente… Continue reading License requirements for this feature have changed. After October 30, 2023, access to capabilities formerly in preview will be read-only, unless you purchase the new Microsoft Entra ID Governance license

Microsoft vient de mettre à disposition une nouvelle version (1.2.4157) du client Windows pour Remote Desktop. Cette version apporte les éléments suivants : Redéfinition de la barre de connexion pour les bureaux de ...(read more)

Si vous possédez un site e-commerce, l’un de vos principaux objectifs est certainement d’augmenter votre taux de conversion. Pour y parvenir, il existe plusieurs astuces et bonnes pratiques à mettre en place. Dans cet article, nous allons vous présenter les meilleures astuces pour améliorer le taux de conversion de votre site e-commerce et ainsi booster vos ventes !

Optimiser la vitesse de chargement de votre site e-commerce

L’un des éléments clés pour améliorer la conversion de votre site e-commerce est d’optimiser sa vitesse de chargement. En effet, les internautes sont de plus en plus impatients et ne tolèrent pas les sites qui mettent trop de temps à se charger.

Voici quelques astuces pour optimiser la vitesse de chargement de votre site e-commerce :

• Réduisez la taille des images : Les images sont souvent responsables du ralentissement d’un site web. Pour éviter cela, vous pouvez compresser vos images ou utiliser des outils qui permettent une optimisation automatique.
• Utilisez un système de cache : Le cache permet à votre site web d’enregistrer temporairement certaines données afin qu’elles soient accessibles plus rapidement lorsqu’un visiteur revient sur le même page.
• Optimisez le code HTML, CSS et JavaScript : Un code bien structuré et épuré peut considérablement améliorer la vitesse du site.
• Hébergez votre site sur un serveur rapide : Si vous utilisez un hébergement partagé avec plusieurs autres sites, il est possible que cela ralentisse votre propre site. Dans ce cas-là, optez plutôt pour un hébergement dédié ou VPS.

En résumé, l’optimisation de la vitesse de chargement est essentielle pour augmenter le taux de conversion sur votre site e-commerce. En appliquant ces astuces simples mais efficaces, vous pouvez offrir une expérience utilisateur fluide et agréable qui encouragera les visiteurs à rester sur votre page et effectuer leurs achats.

Utiliser des call-to-action clairs et incitatifs

Les call-to-action (CTA) sont des éléments clés pour maximiser la conversion d’un site web. En effet, ils permettent de guider l’utilisateur vers une action précise comme s’inscrire à une newsletter, acheter un produit ou encore remplir un formulaire. Cependant, pour qu’ils soient efficaces, il est important qu’ils soient clairs et incitatifs.

Tout d’abord, le choix du texte est crucial. Il doit être court et direct afin que l’utilisateur comprenne immédiatement ce qui est attendu de lui. Par exemple, "Acheter maintenant" ou "S’inscrire" sont des CTA simples mais efficaces qui laissent peu de place à l’ambiguïté.

Ensuite, il est important d’utiliser des verbes d’action pour donner envie à l’utilisateur de cliquer sur le bouton. Des verbes comme "Découvrir", "Profiter", "Obtenir" ou encore "Essayer" sont très incitatifs car ils donnent une impression d’action et de bénéfice immédiat.

En dernier lieu, il ne faut pas hésiter à utiliser des éléments visuels pour mettre en avant les CTA et les rendre plus attractifs. Des couleurs vives et contrastées peuvent aider à attirer l’attention de l’utilisateur sur le bouton tandis que des flèches ou autres symboles peuvent renforcer le caractère incitatif du CTA.

En résumé, utiliser des call-to-action clairs et incitatifs est essentiel pour optimiser la conversion d’un site web. Il convient donc de bien choisir son texte ainsi que ses éléments visuels afin qu’ils attirent au maximum l’attention de l’utilisateur tout en lui donnant envie d’agir.

L’article Astuces pour améliorer le taux de conversion de votre site e-commerce est apparu en premier sur Constantin Boulanger.

Microsoft vient de mettre à disposition une nouvelle version (1.2.4157) du client Windows pour Remote Desktop . Cette version apporte les éléments suivants : Redéfinition de la barre de connexion pour les bureaux de session. Correction d'un problème qui faisait que le client rapportait des journaux d'erreur ErrorCode 0x108 trompeurs ou incorrects. Correction d'un problème qui faisait que le client interrompait parfois les connexions si l'utilisation d'une carte à puce, par exemple, mettait du temps à démarrer la connexion. Correction d'un bug qui empêchait les utilisateurs de mettre à jour le client si celui-ci était installé avec les paramètres ALLUSERS=2 et MSIINSTALLPERUSER=1. Correction d'un problème qui entraînait la déconnexion du client et l'affichage du message d'erreur 0x3000018 au lieu d'une invite à se reconnecter si le périphérique ne permettait pas aux utilisateurs de sauvegarder leurs informations d'identification. Correction de la vulnérabilité connue sous le nom de CVE-2023-28267 . Correction d'un problème qui générait des Activity IDs en double pour des connexions uniques. Amélioration de la journalisation du client, des diagnostics et de la classification des erreurs pour aider les administrateurs à résoudre les problèmes de connexion et d'alimentation.. Télécharger pour : Windows 64-bit Windows 32-bit Windows ARM64