pethost 0.2.1__tar.gz → 0.2.2__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.
Files changed (30) hide show
  1. {pethost-0.2.1 → pethost-0.2.2}/PKG-INFO +1 -1
  2. {pethost-0.2.1 → pethost-0.2.2}/pethost/_async_client.py +6 -3
  3. {pethost-0.2.1 → pethost-0.2.2}/pethost/_client.py +6 -3
  4. {pethost-0.2.1 → pethost-0.2.2}/pethost/_version.py +1 -1
  5. {pethost-0.2.1 → pethost-0.2.2}/pethost/_wire/v1/panel_connect.py +24 -12
  6. {pethost-0.2.1 → pethost-0.2.2}/pyproject.toml +1 -1
  7. {pethost-0.2.1 → pethost-0.2.2}/.gitignore +0 -0
  8. {pethost-0.2.1 → pethost-0.2.2}/LICENSE +0 -0
  9. {pethost-0.2.1 → pethost-0.2.2}/README.md +0 -0
  10. {pethost-0.2.1 → pethost-0.2.2}/pethost/__init__.py +0 -0
  11. {pethost-0.2.1 → pethost-0.2.2}/pethost/_convert.py +0 -0
  12. {pethost-0.2.1 → pethost-0.2.2}/pethost/_errors.py +0 -0
  13. {pethost-0.2.1 → pethost-0.2.2}/pethost/_runtime.py +0 -0
  14. {pethost-0.2.1 → pethost-0.2.2}/pethost/_types.py +0 -0
  15. {pethost-0.2.1 → pethost-0.2.2}/pethost/_wire/__init__.py +0 -0
  16. {pethost-0.2.1 → pethost-0.2.2}/pethost/_wire/v1/__init__.py +0 -0
  17. {pethost-0.2.1 → pethost-0.2.2}/pethost/_wire/v1/panel_pb.py +0 -0
  18. {pethost-0.2.1 → pethost-0.2.2}/pethost/py.typed +0 -0
  19. {pethost-0.2.1 → pethost-0.2.2}/tests/__init__.py +0 -0
  20. {pethost-0.2.1 → pethost-0.2.2}/tests/api.py +0 -0
  21. {pethost-0.2.1 → pethost-0.2.2}/tests/fake.py +0 -0
  22. {pethost-0.2.1 → pethost-0.2.2}/tests/harness.py +0 -0
  23. {pethost-0.2.1 → pethost-0.2.2}/tests/samples.py +0 -0
  24. {pethost-0.2.1 → pethost-0.2.2}/tests/test_clients.py +0 -0
  25. {pethost-0.2.1 → pethost-0.2.2}/tests/test_declarations.py +0 -0
  26. {pethost-0.2.1 → pethost-0.2.2}/tests/test_errors.py +0 -0
  27. {pethost-0.2.1 → pethost-0.2.2}/tests/test_json.py +0 -0
  28. {pethost-0.2.1 → pethost-0.2.2}/tests/test_messages.py +0 -0
  29. {pethost-0.2.1 → pethost-0.2.2}/tests/test_runtime.py +0 -0
  30. {pethost-0.2.1 → pethost-0.2.2}/tests/test_streams.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: pethost
3
- Version: 0.2.1
3
+ Version: 0.2.2
4
4
  Summary: The Python SDK for Pethost, hosting for Docker Compose projects: deploy, read logs and requests, run commands and move files through its API.
5
5
  Project-URL: Homepage, https://pethost.dev
6
6
  Project-URL: Documentation, https://pethost.dev/docs/api/
@@ -420,8 +420,7 @@ class AsyncPethost:
420
420
  Refused, each violation saying what to write instead:
421
421
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
422
422
  `external` or `ipam` of a volume or network: remove them.
423
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
424
- volume (`data:/data`, with `data:` under `volumes:`).
423
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
425
424
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
426
425
  space (`/app/node_modules`).
427
426
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -432,7 +431,11 @@ class AsyncPethost:
432
431
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
433
432
  nothing on the machine, so two projects may write the same (the project's services still
434
433
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
435
- in /.env names one of them, and is no service of the project until then.
434
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
435
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
436
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
437
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
438
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
436
439
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
437
440
  named volume or a tmpfs there.
438
441
 
@@ -416,8 +416,7 @@ class Pethost:
416
416
  Refused, each violation saying what to write instead:
417
417
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
418
418
  `external` or `ipam` of a volume or network: remove them.
419
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
420
- volume (`data:/data`, with `data:` under `volumes:`).
419
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
421
420
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
422
421
  space (`/app/node_modules`).
423
422
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -428,7 +427,11 @@ class Pethost:
428
427
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
429
428
  nothing on the machine, so two projects may write the same (the project's services still
430
429
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
431
- in /.env names one of them, and is no service of the project until then.
430
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
431
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
432
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
433
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
434
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
432
435
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
433
436
  named volume or a tmpfs there.
434
437
 
@@ -1,3 +1,3 @@
1
1
  """The package's version: what a call's User-Agent says. Generated with the package: do not edit."""
2
2
 
3
- VERSION = "0.2.1"
3
+ VERSION = "0.2.2"
@@ -105,8 +105,7 @@ class PanelService(Protocol):
105
105
  Refused, each violation saying what to write instead:
106
106
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
107
107
  `external` or `ipam` of a volume or network: remove them.
108
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
109
- volume (`data:/data`, with `data:` under `volumes:`).
108
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
110
109
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
111
110
  space (`/app/node_modules`).
112
111
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -117,7 +116,11 @@ class PanelService(Protocol):
117
116
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
118
117
  nothing on the machine, so two projects may write the same (the project's services still
119
118
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
120
- in /.env names one of them, and is no service of the project until then.
119
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
120
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
121
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
122
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
123
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
121
124
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
122
125
  named volume or a tmpfs there.
123
126
 
@@ -634,8 +637,7 @@ class PanelServiceClient(ConnectClient):
634
637
  Refused, each violation saying what to write instead:
635
638
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
636
639
  `external` or `ipam` of a volume or network: remove them.
637
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
638
- volume (`data:/data`, with `data:` under `volumes:`).
640
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
639
641
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
640
642
  space (`/app/node_modules`).
641
643
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -646,7 +648,11 @@ class PanelServiceClient(ConnectClient):
646
648
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
647
649
  nothing on the machine, so two projects may write the same (the project's services still
648
650
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
649
- in /.env names one of them, and is no service of the project until then.
651
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
652
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
653
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
654
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
655
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
650
656
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
651
657
  named volume or a tmpfs there.
652
658
 
@@ -1152,8 +1158,7 @@ class PanelServiceSync(Protocol):
1152
1158
  Refused, each violation saying what to write instead:
1153
1159
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
1154
1160
  `external` or `ipam` of a volume or network: remove them.
1155
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
1156
- volume (`data:/data`, with `data:` under `volumes:`).
1161
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
1157
1162
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
1158
1163
  space (`/app/node_modules`).
1159
1164
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -1164,7 +1169,11 @@ class PanelServiceSync(Protocol):
1164
1169
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
1165
1170
  nothing on the machine, so two projects may write the same (the project's services still
1166
1171
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
1167
- in /.env names one of them, and is no service of the project until then.
1172
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
1173
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
1174
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
1175
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
1176
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
1168
1177
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
1169
1178
  named volume or a tmpfs there.
1170
1179
 
@@ -1676,8 +1685,7 @@ class PanelServiceClientSync(ConnectClientSync):
1676
1685
  Refused, each violation saying what to write instead:
1677
1686
  - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
1678
1687
  `external` or `ipam` of a volume or network: remove them.
1679
- - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
1680
- volume (`data:/data`, with `data:` under `volumes:`).
1688
+ - a writable bind mount of the whole project (`.:/app`): add `:ro`.
1681
1689
  - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
1682
1690
  space (`/app/node_modules`).
1683
1691
  - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
@@ -1688,7 +1696,11 @@ class PanelServiceClientSync(ConnectClientSync):
1688
1696
  Not refused, and read the machine's way: a `container_name` and a network's `name` name
1689
1697
  nothing on the machine, so two projects may write the same (the project's services still
1690
1698
  reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
1691
- in /.env names one of them, and is no service of the project until then.
1699
+ in /.env names one of them, and is no service of the project until then; a bind mount of a
1700
+ folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
1701
+ (`data`), which deploys keep and backups hold, with none of the version's files in it, so
1702
+ project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
1703
+ under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
1692
1704
  An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
1693
1705
  named volume or a tmpfs there.
1694
1706
 
@@ -6,7 +6,7 @@ build-backend = "hatchling.build"
6
6
 
7
7
  [project]
8
8
  name = "pethost"
9
- version = "0.2.1"
9
+ version = "0.2.2"
10
10
  description = "The Python SDK for Pethost, hosting for Docker Compose projects: deploy, read logs and requests, run commands and move files through its API."
11
11
  readme = "README.md"
12
12
  requires-python = ">=3.10"
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes