yadunut/clan-core
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request 'Replace funky utf-8 singlequotes with decent ones' (#4923) from replace-backticks into main

Browse Source 
Reviewed-on: https://git.clan.lol/clan/clan-core/pulls/4923
This commit is contained in:
Mic92
2025-08-25 10:03:46 +00:00
parent a50b6f7bc7 cdd241d8ff
commit 289732ad20
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -8,7 +8,7 @@ Our mission is simple: to democratize computing by providing tools that empower
## Features of Clan ## Features of Clan
- **Full-Stack System Deployment:** Utilize Clan’s toolkit alongside Nix's reliability to build and manage systems effortlessly. - **Full-Stack System Deployment:** Utilize Clan's toolkit alongside Nix's reliability to build and manage systems effortlessly.
- **Overlay Networks:** Secure, private communication channels between devices. - **Overlay Networks:** Secure, private communication channels between devices.
- **Virtual Machine Integration:** Seamless operation of VM applications within the main operating system. - **Virtual Machine Integration:** Seamless operation of VM applications within the main operating system.
- **Robust Backup Management:** Long-term, self-hosted data preservation. - **Robust Backup Management:** Long-term, self-hosted data preservation.

6
docs/site/guides/clanServices.md
View File

@@ -1,6 +1,6 @@
# Using `clanServices` # Using `clanServices`
Clan’s `clanServices` system is a composable way to define and deploy services across machines. Clan's `clanServices` system is a composable way to define and deploy services across machines.
This guide shows how to **instantiate** a `clanService`, explains how service definitions are structured in your inventory, and how to pick or create services from modules exposed by flakes. This guide shows how to **instantiate** a `clanService`, explains how service definitions are structured in your inventory, and how to pick or create services from modules exposed by flakes.
@@ -130,7 +130,7 @@ inventory.instances = {
## Picking a clanService ## Picking a clanService
You can use services exposed by Clan’s core module library, `clan-core`. You can use services exposed by Clan's core module library, `clan-core`.
🔗 See: [List of Available Services in clan-core](../reference/clanServices/index.md) 🔗 See: [List of Available Services in clan-core](../reference/clanServices/index.md)
@@ -152,7 +152,7 @@ You might expose your service module from your flake — this makes it easy for
--- ---
## What’s Next? ## What's Next?
* [Author your own clanService →](../guides/services/community.md) * [Author your own clanService →](../guides/services/community.md)
* [Migrate from clanModules →](../guides/migrations/migrate-inventory-services.md) * [Migrate from clanModules →](../guides/migrations/migrate-inventory-services.md)

2
lib/jsonschema/default.nix
View File

@@ -328,7 +328,7 @@ rec {
# To get the type of a Deferred modules we need to know the interface of the place where it is evaluated. # To get the type of a Deferred modules we need to know the interface of the place where it is evaluated.
# i.e. in case of a clan.service this is the interface of the service which dynamically changes depending on the service # i.e. in case of a clan.service this is the interface of the service which dynamically changes depending on the service
# We assign "type" = [] # We assign "type" = []
# This means any value is valid — or like TypeScript’s unknown. # This means any value is valid — or like TypeScript's unknown.
# We can assign the type later, when we know the exact interface. # We can assign the type later, when we know the exact interface.
# tsType = "unknown" is a type that we preload for json2ts, such that it gets the correct type in typescript # tsType = "unknown" is a type that we preload for json2ts, such that it gets the correct type in typescript
(option.type.name == "deferredModule") (option.type.name == "deferredModule")