confsync-client 0.2.0__tar.gz → 0.4.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: confsync-client
3
- Version: 0.2.0
3
+ Version: 0.4.0
4
4
  Summary: Client library and CLI for confsync — pull/push encrypted config documents
5
5
  Requires-Python: >=3.11
6
6
  Requires-Dist: httpx>=0.27
@@ -9,7 +9,7 @@ Typical usage from another project (e.g. flexgate):
9
9
  """
10
10
  from __future__ import annotations
11
11
 
12
- __version__ = "0.2.0"
12
+ __version__ = "0.4.0"
13
13
 
14
14
  from confsync.core import ConfsyncClient, ConfsyncError
15
15
  from confsync.credentials import load_client, login
@@ -27,13 +27,13 @@ $CONFSYNC_CREDENTIALS. Re-login anytime; logout = delete the file.
27
27
 
28
28
  Two kinds of credentials are accepted:
29
29
 
30
- 1. API key (cs_...) Create one in the web UI under /keys. Shown once;
31
- only its hash is stored server-side.
30
+ 1. API key (cs_...) Create one in the web UI under /keys. Logged-in
31
+ owners can view and copy it there anytime.
32
32
  2. Gitea access token If the server has Gitea configured, paste a token
33
33
  from Gitea (Settings -> Applications -> Access
34
34
  Tokens, scope read:user is enough). The server
35
35
  verifies it against your Gitea (cached ~5 min) and
36
- maps it to the confsync user with the same login.
36
+ maps it to your confsync account (identity or email).
37
37
 
38
38
  Requires client >= 0.2.0 for Gitea tokens (older clients insist on cs_ keys).\
39
39
  """,