pethost 0.2.0__tar.gz → 0.2.2__tar.gz

{pethost-0.2.0 → pethost-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pethost
-Version: 0.2.0
+Version: 0.2.2
 Summary: The Python SDK for Pethost, hosting for Docker Compose projects: deploy, read logs and requests, run commands and move files through its API.
 Project-URL: Homepage, https://pethost.dev
 Project-URL: Documentation, https://pethost.dev/docs/api/

{pethost-0.2.0 → pethost-0.2.2}/pethost/_async_client.py

@@ -418,17 +418,24 @@ class AsyncPethost:
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 

{pethost-0.2.0 → pethost-0.2.2}/pethost/_client.py

@@ -414,17 +414,24 @@ class Pethost:
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 

{pethost-0.2.0 → pethost-0.2.2}/pethost/_version.py

@@ -1,3 +1,3 @@
 """The package's version: what a call's User-Agent says. Generated with the package: do not edit."""
 
-VERSION = "0.2.0"
+VERSION = "0.2.2"

{pethost-0.2.0 → pethost-0.2.2}/pethost/_wire/v1/panel_connect.py

@@ -103,17 +103,24 @@ class PanelService(Protocol):
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 
@@ -628,17 +635,24 @@ class PanelServiceClient(ConnectClient):
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 
@@ -1142,17 +1156,24 @@ class PanelServiceSync(Protocol):
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 
@@ -1662,17 +1683,24 @@ class PanelServiceClientSync(ConnectClientSync):
 
         The file runs as written, or is refused: the machine corrects nothing in it, in any version.
         Refused, each violation saying what to write instead:
-        - `container_name`, `profiles`; `name`, `driver`, `driver_opts`, `external` or `ipam` of a
-          volume or network: remove them.
-        - a writable bind mount (`.:/app`, `./data:/data`): project files take `:ro`, data a named
-          volume (`data:/data`, with `data:` under `volumes:`).
+        - a volume's `name`; `driver` (but Docker's default, `local` or `bridge`), `driver_opts`,
+          `external` or `ipam` of a volume or network: remove them.
+        - a writable bind mount of the whole project (`.:/app`): add `:ro`.
         - a volume with no name (`- /data`): name it. Below a bind mount it is allowed, as scratch
           space (`/app/node_modules`).
         - `env_file` naming a file the files lack: write it, empty if it sets nothing, or give the
           entry `required: false`.
-        - `privileged`, `cap_add`, `security_opt`, `devices`, host namespaces, the Docker socket, a
-          path outside the directory; more than one replica; `include` or `extends` from a URL; a
-          git URL as a build context.
+        - `privileged`, `cap_add`, `security_opt` (but `no-new-privileges`), `devices`, host
+          namespaces, the Docker socket, a path outside the directory; more than one replica;
+          `include` or `extends` from a URL; a git URL as a build context.
+        Not refused, and read the machine's way: a `container_name` and a network's `name` name
+        nothing on the machine, so two projects may write the same (the project's services still
+        reach the container by it); a service with `profiles` runs only while `COMPOSE_PROFILES`
+        in /.env names one of them, and is no service of the project until then; a bind mount of a
+        folder without `:ro` (`./data:/data`) mounts the project's volume named after the path
+        (`data`), which deploys keep and backups hold, with none of the version's files in it, so
+        project files take `:ro`, and data is plainer in a named volume (`data:/data`, with `data:`
+        under `volumes:`); a bind mount of a file without `:ro` mounts it read-only.
         An image's VOLUME that no mount covers fails the deploy (UNCOVERED_IMAGE_VOLUME): mount a
         named volume or a tmpfs there.
 

{pethost-0.2.0 → pethost-0.2.2}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pethost"
-version = "0.2.0"
+version = "0.2.2"
 description = "The Python SDK for Pethost, hosting for Docker Compose projects: deploy, read logs and requests, run commands and move files through its API."
 readme = "README.md"
 requires-python = ">=3.10"