qfield-driver 0.1.0__tar.gz

qfield_driver-0.1.0/LICENSE

@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

qfield_driver-0.1.0/PKG-INFO

@@ -0,0 +1,200 @@
+Metadata-Version: 2.4
+Name: qfield-driver
+Version: 0.1.0
+Summary: Drive a real QField app from Python, with a local QFieldCloud
+Keywords: QField,QFieldCloud,GIS,e2e
+License-Expression: GPL-2.0-or-later
+License-File: LICENSE
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Testing
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: POSIX :: Linux
+Requires-Dist: python-xlib>=0.33
+Requires-Dist: qfield-fetch
+Requires-Dist: requests>=2.32 ; extra == 'cloud'
+Requires-Dist: urllib3>=2 ; extra == 'cloud'
+Requires-Dist: typer>=0.16 ; extra == 'cloud'
+Requires-Python: >=3.12
+Project-URL: homepage, https://github.com/Joonalai/qfield-dev-tools
+Project-URL: repository, https://github.com/Joonalai/qfield-dev-tools
+Provides-Extra: cloud
+Description-Content-Type: text/markdown
+
+# qfield-driver
+
+Drive a real QField app from Python. It starts the stock QField release AppImage and
+uses it like a user: real taps, real typing, real forms, real projects. The `cloud`
+extra adds a local QFieldCloud, for several devices syncing through it.
+
+The driver has no pytest dependency. [pytest-qfield-e2e](https://github.com/Joonalai/qfield-dev-tools/tree/main/components/pytest-qfield-e2e)
+wraps it in fixtures, and [qfield-mcp](https://github.com/Joonalai/qfield-dev-tools/tree/main/components/qfield-mcp)
+lets AI agents drive it.
+
+Status: experimental. Linux x64 only.
+
+## How it works
+
+- QField AppImages are downloaded and extracted once by [qfield-fetch](https://github.com/Joonalai/qfield-dev-tools/tree/main/components/qfield-fetch).
+- QField runs on a private Xvfb with an isolated `HOME`, so it never touches your
+  own QField profile or running instances. Cameras, when the machine has any, are
+  hidden with a mount namespace (`unshare`). Telemetry is off.
+- A small app plugin, the driver, is installed into that profile. It polls a localhost
+  bridge (random token in the path) and runs JS function bodies sent from Python.
+  Results come back JSON-decoded.
+- Taps and keys are XTEST events on the private display, so they go through QField's
+  normal input handling. Non-ASCII text such as `ä` is typed too.
+- GNSS fixes come from a fake NMEA receiver that QField connects to over TCP.
+
+No custom QField build is needed, the driver runs the binary users run.
+
+## Requirements
+
+- `Xvfb`
+- The system libraries the AppImage does not bundle. On Ubuntu 24.04:
+  `xvfb ca-certificates libfontconfig1 libegl1 libopengl0 libgl1 libglx-mesa0
+  libxkbcommon-x11-0 libxcb-cursor0 libxcb-icccm4 libxcb-image0 libxcb-keysyms1
+  libxcb-randr0 libxcb-render-util0 libxcb-shape0 libxcb-xinerama0 libxcb-xkb1
+  libdbus-1-3`
+- On machines with cameras, util-linux `unshare` with unprivileged user namespaces.
+  Without `/dev/video*` QField starts directly, as in containers and CI.
+- For QFieldCloud: docker or rootless podman with `docker compose`, and `git`
+
+## Usage
+
+```bash
+pip install qfield-driver          # or qfield-driver[cloud]
+```
+
+```python
+from pathlib import Path
+
+from qfield_fetch import appimage
+from qfield_driver import actions
+from qfield_driver.app import QFieldApp
+
+with QFieldApp(appimage("4.2.9"), Path("/tmp/device/home")) as app:
+    app.host_plugin(Path("my_plugin/main.qml"))
+    actions.open_project(app, Path("project/project.qgs"))
+    actions.tap_object(app, "pluginButton")
+    actions.wait_for_message(app, "Plugin button clicked!")
+    print(app.eval("return plugin.clicks"))
+```
+
+`QFieldApp(app_run, home, app_plugins=None, settings=None, ...)` starts on enter and
+stops on exit. `app_run` is an extracted `AppRun`, an AppImage (runs through FUSE) or a
+build, `local_app(path)` checks it. `home` is created and becomes QField's profile, the
+log goes next to it as `<home>.log`. `settings` are QField settings written before the
+start, `{"myplugin/interval": 50}`, for values a plugin reads once on load.
+
+`QFieldApp.eval(code)` runs a JS function body inside QField. The body sees `iface`,
+`find` (`iface.findItemByObjectName`), `findItem` (scene search by objectName, also
+in popups and plugin toolbars), `walk`, `walkAll`, `scene`, `state` (kept between
+calls), `plugin` (the hosted plugin root), `qgisProject`, `layerObserver`,
+`pluginManager`, `settings`, `platformUtilities`, `messageLogModel`,
+`featureHistory`, `flatLayerTree`, `trackingModel`, `LayerUtils`, `GeometryUtils`,
+`FeatureUtils`, `StringUtils` and `Theme`. `wait(code)` polls it until truthy.
+
+Other methods: `click`, `long_press`, `drag`, `type_text`, `key`, `screenshot`,
+`log_text`, `wait_for_log`, `reset` (back to a clean state for reuse) and
+`diagnose` (message log, log tail and a screenshot of a failure).
+
+### Loading the plugin under test
+
+- `app.host_plugin(main_qml)` creates the plugin the way QField's plugin manager
+  does, but keeps its root reachable as `plugin`, so callers can inspect plugin
+  state. `reload_plugin()` loads it again with your edits. Unknown names in the
+  plugin resolve through the driver's context, which only has `_pqf` prefixed members.
+- `QFieldApp(app_plugins={uuid: directory})` installs it as a real app plugin
+  instead, a black box.
+- Project plugins come with the project, `actions.open_project(app, path,
+  grant_plugin=True)` answers QField's permission prompt.
+
+### Actions
+
+`qfield_driver.actions` has user level helpers built on QField's own item
+names: `tap_object`, `tap_text`, `tap_icon`, `type_into`, `expand_drawer`,
+`open_project`, `frame_map`, `tap_map`, `long_press_map`, `digitize_point`,
+`open_feature_form`, `edit_in_form`, `set_field`, `choose_option`, `toggle_switch`,
+`tick_item`, `search_and_tick`, `attach_photo`, `open_related`, `save_form`,
+`wait_visible`, `wait_for_text` (toasts), `frame_and_tap`, `scan_code` (QField's
+code reader), `features`, `geometries`, `feature_count`, `add_feature`,
+`change_geometry`, `evaluate_expression`, `import_js` (call a plugin's JS module),
+`highlighted_wkt`, `log_messages`, `wait_for_message`, and the cloud steps `login`,
+`download_project`, `push` and `synchronize`. `qfield_driver.wkt` has `length`
+and `interpolate`, which QField does not expose to QML.
+
+Differences from QGIS based stubs to expect: a NULL integer attribute reads as `0`
+in QField JS, `ExpressionEvaluator` hands back text, plugin popups animate open and
+closed so wait for `visible` instead of asserting it, and the message log lists
+newest first.
+
+Item names follow QField 4.2. Recheck them on a version bump, QField 4.3 renamed
+its QML sources.
+
+### Positioning
+
+```python
+app.set_position(389870.0, 6678167.0)  # project CRS
+app.wait_for_position(389870.0, 6678167.0)
+app.lose_position()
+```
+
+## QFieldCloud
+
+With the `cloud` extra. QFieldCloud releases often and only the newest release is
+maintained. `QFieldCloudStack` runs the official compose stack of one release,
+`resolve_ref("hosted")` follows app.qfield.cloud, so a run matches what field
+devices sync against. Each release gets its own compose project, images and volumes.
+The checkout lives in the qfield-fetch cache.
+
+```python
+from qfield_fetch import default_cache_dir
+from qfield_driver.cloud.client import QFieldCloudClient
+from qfield_driver.cloud.stack import QFieldCloudStack, resolve_ref
+
+stack = QFieldCloudStack(resolve_ref("hosted"), default_cache_dir())
+stack.up()  # builds once, then reuses the running stack
+admin = QFieldCloudClient(stack.url, *stack.admin, verify=stack.ca_certificate)
+project_id = admin.create_project("survey")
+admin.upload(project_id, Path("project"))
+admin.package(project_id)
+```
+
+`QFieldCloudStack.local(checkout, cache_dir)` runs a QFieldCloud checkout of your
+own instead. The stack writes its `.env` and compose overrides into that checkout.
+`stack.ensure_user(name, password)` creates a user, and the client covers projects,
+collaborators, files, jobs and deltas, with `wait_for_jobs` and `wait_for_deltas`.
+
+The stack binds its ports to localhost, only the object storage API also listens on
+the host's LAN address, where the containers reach it. The admin is
+`admin`/`admin123`, so keep it a disposable test stack. Clients verify TLS against
+the stack's own mkcert authority, `stack.ca_certificate`. HTTPS is on port 8543.
+
+```bash
+qfield-driver-cloud ref               # what `hosted` resolves to
+qfield-driver-cloud up --ref latest   # build and start
+qfield-driver-cloud prune             # remove stacks of older releases
+qfield-driver-cloud down
+qfield-driver-cloud up --source-dir ~/src/QFieldCloud  # a checkout of your own
+```
+
+`qfdc` is a short alias of `qfield-driver-cloud`.
+
+The stack runs on `https://localhost:8543` with a self-signed certificate. QField
+accepts it, it ignores TLS errors on hosts outside `.qfield.cloud`. Overrides
+applied to the upstream compose files:
+
+- Logging driver `json-file`, podman rejects the upstream `tag` option.
+- The worker mounts the docker or podman socket found on the host.
+- nginx gets the runtime's DNS resolver, docker and podman differ.
+- `TMP_DIRECTORY` stays `/tmp`, the worker hands its own temp path to the sibling
+  QGIS container.
+- `ofelia` is disabled and host ports are moved off common defaults.
+- Storage endpoints point at this machine's address and the published API port.
+  The upstream default, docker's bridge `172.17.0.1`, does not exist under podman.
+- Images to build are read from the release's compose files, so a new worker image
+  (`qgis4` in v26.30) is built without a code change.
+
+When a package job fails with exit code 0, read the job `feedback` through
+`client.jobs(project_id)`, the worker log alone is misleading.