| Name | arpx JSON |
| Version |
0.0.21
JSON |
| download |
| home_page | None |
| Summary | Dynamic multi-IP LAN HTTP/HTTPS server manager with ARP visibility |
| upload_time | 2025-09-08 17:53:57 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License. |
| keywords |
arp
certificates
http
https
lan
lets-encrypt
mkcert
network
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# ARPx
**Dynamic multi-IP LAN HTTP/HTTPS server manager with ARP visibility and optional Docker/Podman Compose bridging.**
`arpx` makes local services instantly visible across your network using ARP announcements. It’s ideal for rapid prototyping and testing where you want each service to feel like it’s running on its own host with its own IP and TLS certificate—without touching router configs.
---
## Table of Contents
- [What makes `arpx` different?](#what-makes-arpx-different)
- [Requirements](#requirements)
- [Installation](#installation)
- [Quick Start](#quick-start)
- [Real-World Use Case: Solving Port Conflicts in Docker Projects](#real-world-use-case-solving-port-conflicts-in-docker-projects)
- [Docker/Podman Compose Bridge](#dockerpodman-compose-bridge)
- [Architecture](#architecture)
- [Navigation Menu](#navigation-menu)
- [Contributing](#contributing)
- [Author](#author)
- [License](#license)
---
### What makes `arpx` different?
Typical local dev setups bind everything to `localhost:port`. `arpx` fills the gap by providing:
* 🌐 **LAN visibility** – Services get unique IPs visible to *all* devices on your network.
* 🔑 **HTTPS everywhere** – Built-in cert management (self-signed, mkcert, Let’s Encrypt).
* 🐳 **Container bridging** – Map Docker/Podman Compose services directly to LAN IPs.
* ⚡ **Zero router hacks** – No port forwarding or DNS server required.
* 🧩 **Lightweight & scriptable** – Simple CLI for easy integration into dev/test workflows.
Think of it as giving your LAN **mini cloud-like behavior**, where each service can live on its own IP with real HTTPS.
### Requirements
- Linux with root privileges for network configuration.
- Required tools: `ip`, `arping` (from `iputils-arping` or similar).
- Optional for certificates: `mkcert` or `certbot`.
`arpx` will check for these dependencies at runtime and provide installation hints if they are missing.
### Installation
#### From PyPI (Recommended)
```bash
# Install with pip or uv
pip install arpx
# Install with optional extras for Docker bridging or mDNS
pip install "arpx[compose,mdns]"
```
#### From Repository
For development or to ensure `sudo arpx` works out of the box:
```bash
# This script installs with pip and creates a system-wide symlink
make install
```
### Quick Start
Create 3 virtual IPs with HTTP servers:
```bash
sudo arpx up -n 3
```
Enable HTTPS with a self-signed certificate:
```bash
sudo arpx up -n 2 --https self-signed --domains myapp.lan
```
### Real-World Use Case: Solving Port Conflicts in Docker Projects
Imagine you're working on multiple Docker-based projects simultaneously. One project, already running on your local machine, occupies port 80 for its web server. You need to test a new project that also defaults to port 80. Normally, you'd face a dilemma: either modify the new project's configuration (and potentially dig through someone else's code to update hardcoded port references and URIs), or stop the first project to free up the port. Both options are time-consuming and disruptive to your workflow.
With `arpx`, this problem disappears. Here's how it works:
- **Dynamic IP Allocation**: `arpx` generates new, unique IP addresses within your local network's DHCP range. These virtual IPs are assigned to your services, so you don't need to worry about port conflicts on your primary machine IP.
- **Zero Configuration**: Instead of reconfiguring ports or URIs in your Docker project, `arpx` bridges the services to these new IPs. For instance, even if port 80 is occupied on your machine, you can run the new project's service on port 80 of a dynamically assigned IP.
- **LAN Visibility**: These IPs are visible across your local network, allowing you to test from other devices (like a phone or another computer) without touching router settings.
**Scenario Example**:
A developer named Alex is running a web app on `localhost:80`. He clones a new open-source project that also binds to port 80 by default. Instead of editing the project's `docker-compose.yml` or source code (which could have hardcoded URIs and untested default port assumptions), Alex uses `arpx`:
```bash
# Bridge the new project's services to unique LAN IPs
sudo arpx compose -f docker-compose.yml
```
`arpx` assigns new IPs (e.g., `192.168.1.120` and `192.168.1.121`) to each service in the Docker Compose file, mapping their ports without conflicts. Alex can now access the new app at `http://192.168.1.120:80` while his original app remains on `localhost:80`. No code changes, no downtime.
**Addressing Common Doubts**:
- *Can't Docker just redirect traffic to different ports?* While Docker allows port mapping (e.g., `-p 8080:80`), this often isn't enough. Many projects have hardcoded URIs or dependencies on specific ports across multiple services, requiring extensive reconfiguration and testing. `arpx` sidesteps this by providing entirely new IPs, avoiding the need to touch port configurations.
- *Why not run Docker in a virtual environment?* Virtual environments or separate workstations add overhead and complexity. `arpx` keeps everything on your local machine, seamlessly integrating with your existing setup.
This makes `arpx` uniquely powerful for developers dealing with complex, pre-built projects or needing to test across multiple network-visible IPs without router hacks.
### Docker/Podman Compose Bridge
Make your Compose services visible on the LAN by assigning each an alias IP:
```bash
# In your project directory with docker-compose.yml
sudo arpx compose -f docker-compose.yml
```
For more detailed examples, see the `examples/` directory.
### Architecture
For a detailed explanation of the internal components and workflows, see the [**Architecture Overview**](docs/architecture.md).
### Navigation Menu
Explore the project structure and key files:
- **Documentation:**
- [Architecture Overview](docs/architecture.md) - Understand the internal design and workflows.
- [Specification](docs/SPEC.md) - Detailed technical specification.
- **Core Code:**
- [CLI Entry Point](src/arpx/cli.py) - Main command-line interface logic.
- [Network Manager](src/arpx/network.py) - Handles virtual IPs and ARP announcements.
- [Certificate Utilities](src/arpx/certs.py) - TLS certificate generation.
- **Tests:**
- [Unit Tests for Network](tests/unit/test_network.py) - Tests for network operations.
- [Unit Tests for Certs](tests/unit/test_certs.py) - Tests for certificate handling.
- [Unit Tests for Utils](tests/unit/test_utils.py) - Tests for utility functions.
### Contributing
Contributions are welcome! Here's how you can get involved:
1. **Setup Development Environment:**
```bash
# Clone the repository if you haven't already
git clone https://github.com/dynapsys/arpx.git
cd arpx
# Install development dependencies
make dev
```
2. **Run Tests:**
```bash
# Run all tests to ensure nothing is broken
make test
```
3. **Coding Guidelines:**
- Follow PEP 8 for Python code style.
- Use type hints where applicable.
- Add unit tests for new functionality.
- Format code with `make format` before committing.
4. **Submit a Pull Request:**
- Create a branch for your feature or bugfix.
- Commit your changes with descriptive messages.
- Push your branch to the repository.
- Open a pull request with a clear description of your changes.
For major changes, please open an issue first to discuss what you would like to change.
### Author
- **Name:** Tom Sapletta
- **Contact:** [info@softreck.dev](mailto:info@softreck.dev)
`arpx` is created and maintained by Tom Sapletta, a software architect and open-source enthusiast with a passion for creating tools that simplify complex development workflows. His work focuses on networking, automation, and building elegant solutions for developers.
### License
This project is licensed under the Apache License 2.0. See the `LICENSE` file for details.
Raw data
{
"_id": null,
"home_page": null,
"name": "arpx",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "arp, certificates, http, https, lan, lets-encrypt, mkcert, network",
"author": null,
"author_email": "Tom Sapletta <info@softreck.dev>",
"download_url": "https://files.pythonhosted.org/packages/5c/99/9edec34f09322ddb8c96dd1b6bc9a7321970c2483c755593ed5bc1a0de3f/arpx-0.0.21.tar.gz",
"platform": null,
"description": "# ARPx\n\n\n\n\n\n\n\n**Dynamic multi-IP LAN HTTP/HTTPS server manager with ARP visibility and optional Docker/Podman Compose bridging.**\n\n`arpx` makes local services instantly visible across your network using ARP announcements. It\u2019s ideal for rapid prototyping and testing where you want each service to feel like it\u2019s running on its own host with its own IP and TLS certificate\u2014without touching router configs.\n\n---\n\n## Table of Contents\n\n- [What makes `arpx` different?](#what-makes-arpx-different)\n- [Requirements](#requirements)\n- [Installation](#installation)\n- [Quick Start](#quick-start)\n- [Real-World Use Case: Solving Port Conflicts in Docker Projects](#real-world-use-case-solving-port-conflicts-in-docker-projects)\n- [Docker/Podman Compose Bridge](#dockerpodman-compose-bridge)\n- [Architecture](#architecture)\n- [Navigation Menu](#navigation-menu)\n- [Contributing](#contributing)\n- [Author](#author)\n- [License](#license)\n\n---\n\n### What makes `arpx` different?\n\nTypical local dev setups bind everything to `localhost:port`. `arpx` fills the gap by providing:\n\n* \ud83c\udf10 **LAN visibility** \u2013 Services get unique IPs visible to *all* devices on your network.\n* \ud83d\udd11 **HTTPS everywhere** \u2013 Built-in cert management (self-signed, mkcert, Let\u2019s Encrypt).\n* \ud83d\udc33 **Container bridging** \u2013 Map Docker/Podman Compose services directly to LAN IPs.\n* \u26a1 **Zero router hacks** \u2013 No port forwarding or DNS server required.\n* \ud83e\udde9 **Lightweight & scriptable** \u2013 Simple CLI for easy integration into dev/test workflows.\n\nThink of it as giving your LAN **mini cloud-like behavior**, where each service can live on its own IP with real HTTPS.\n\n### Requirements\n\n- Linux with root privileges for network configuration.\n- Required tools: `ip`, `arping` (from `iputils-arping` or similar).\n- Optional for certificates: `mkcert` or `certbot`.\n\n`arpx` will check for these dependencies at runtime and provide installation hints if they are missing.\n\n### Installation\n\n#### From PyPI (Recommended)\n\n```bash\n# Install with pip or uv\npip install arpx\n\n# Install with optional extras for Docker bridging or mDNS\npip install \"arpx[compose,mdns]\"\n```\n\n#### From Repository\n\nFor development or to ensure `sudo arpx` works out of the box:\n\n```bash\n# This script installs with pip and creates a system-wide symlink\nmake install\n```\n\n### Quick Start\n\nCreate 3 virtual IPs with HTTP servers:\n\n```bash\nsudo arpx up -n 3\n```\n\nEnable HTTPS with a self-signed certificate:\n\n```bash\nsudo arpx up -n 2 --https self-signed --domains myapp.lan\n```\n\n### Real-World Use Case: Solving Port Conflicts in Docker Projects\n\nImagine you're working on multiple Docker-based projects simultaneously. One project, already running on your local machine, occupies port 80 for its web server. You need to test a new project that also defaults to port 80. Normally, you'd face a dilemma: either modify the new project's configuration (and potentially dig through someone else's code to update hardcoded port references and URIs), or stop the first project to free up the port. Both options are time-consuming and disruptive to your workflow.\n\nWith `arpx`, this problem disappears. Here's how it works:\n\n- **Dynamic IP Allocation**: `arpx` generates new, unique IP addresses within your local network's DHCP range. These virtual IPs are assigned to your services, so you don't need to worry about port conflicts on your primary machine IP.\n- **Zero Configuration**: Instead of reconfiguring ports or URIs in your Docker project, `arpx` bridges the services to these new IPs. For instance, even if port 80 is occupied on your machine, you can run the new project's service on port 80 of a dynamically assigned IP.\n- **LAN Visibility**: These IPs are visible across your local network, allowing you to test from other devices (like a phone or another computer) without touching router settings.\n\n**Scenario Example**:\nA developer named Alex is running a web app on `localhost:80`. He clones a new open-source project that also binds to port 80 by default. Instead of editing the project's `docker-compose.yml` or source code (which could have hardcoded URIs and untested default port assumptions), Alex uses `arpx`:\n\n```bash\n# Bridge the new project's services to unique LAN IPs\nsudo arpx compose -f docker-compose.yml\n```\n\n`arpx` assigns new IPs (e.g., `192.168.1.120` and `192.168.1.121`) to each service in the Docker Compose file, mapping their ports without conflicts. Alex can now access the new app at `http://192.168.1.120:80` while his original app remains on `localhost:80`. No code changes, no downtime.\n\n**Addressing Common Doubts**:\n- *Can't Docker just redirect traffic to different ports?* While Docker allows port mapping (e.g., `-p 8080:80`), this often isn't enough. Many projects have hardcoded URIs or dependencies on specific ports across multiple services, requiring extensive reconfiguration and testing. `arpx` sidesteps this by providing entirely new IPs, avoiding the need to touch port configurations.\n- *Why not run Docker in a virtual environment?* Virtual environments or separate workstations add overhead and complexity. `arpx` keeps everything on your local machine, seamlessly integrating with your existing setup.\n\nThis makes `arpx` uniquely powerful for developers dealing with complex, pre-built projects or needing to test across multiple network-visible IPs without router hacks.\n\n### Docker/Podman Compose Bridge\n\nMake your Compose services visible on the LAN by assigning each an alias IP:\n\n```bash\n# In your project directory with docker-compose.yml\nsudo arpx compose -f docker-compose.yml\n```\n\nFor more detailed examples, see the `examples/` directory.\n\n### Architecture\n\nFor a detailed explanation of the internal components and workflows, see the [**Architecture Overview**](docs/architecture.md).\n\n### Navigation Menu\n\nExplore the project structure and key files:\n- **Documentation:**\n - [Architecture Overview](docs/architecture.md) - Understand the internal design and workflows.\n - [Specification](docs/SPEC.md) - Detailed technical specification.\n- **Core Code:**\n - [CLI Entry Point](src/arpx/cli.py) - Main command-line interface logic.\n - [Network Manager](src/arpx/network.py) - Handles virtual IPs and ARP announcements.\n - [Certificate Utilities](src/arpx/certs.py) - TLS certificate generation.\n- **Tests:**\n - [Unit Tests for Network](tests/unit/test_network.py) - Tests for network operations.\n - [Unit Tests for Certs](tests/unit/test_certs.py) - Tests for certificate handling.\n - [Unit Tests for Utils](tests/unit/test_utils.py) - Tests for utility functions.\n\n### Contributing\n\nContributions are welcome! Here's how you can get involved:\n\n1. **Setup Development Environment:**\n ```bash\n # Clone the repository if you haven't already\n git clone https://github.com/dynapsys/arpx.git\n cd arpx\n\n # Install development dependencies\n make dev\n ```\n2. **Run Tests:**\n ```bash\n # Run all tests to ensure nothing is broken\n make test\n ```\n3. **Coding Guidelines:**\n - Follow PEP 8 for Python code style.\n - Use type hints where applicable.\n - Add unit tests for new functionality.\n - Format code with `make format` before committing.\n4. **Submit a Pull Request:**\n - Create a branch for your feature or bugfix.\n - Commit your changes with descriptive messages.\n - Push your branch to the repository.\n - Open a pull request with a clear description of your changes.\n\nFor major changes, please open an issue first to discuss what you would like to change.\n\n### Author\n\n- **Name:** Tom Sapletta\n- **Contact:** [info@softreck.dev](mailto:info@softreck.dev)\n\n`arpx` is created and maintained by Tom Sapletta, a software architect and open-source enthusiast with a passion for creating tools that simplify complex development workflows. His work focuses on networking, automation, and building elegant solutions for developers.\n\n### License\n\nThis project is licensed under the Apache License 2.0. See the `LICENSE` file for details.\n",
"bugtrack_url": null,
"license": "Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n \n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n \n 1. Definitions.\n \n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n \n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n \n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n \n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n \n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n \n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n \n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n \n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n \n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n \n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n \n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n \n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n \n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n \n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n \n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n \n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n \n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n \n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n \n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n \n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n \n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n \n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n \n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n \n END OF TERMS AND CONDITIONS\n \n APPENDIX: How to apply the Apache License to your work.\n \n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n \n Copyright [yyyy] [name of copyright owner]\n \n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n \n http://www.apache.org/licenses/LICENSE-2.0\n \n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.",
"summary": "Dynamic multi-IP LAN HTTP/HTTPS server manager with ARP visibility",
"version": "0.0.21",
"project_urls": {
"Homepage": "https://github.com/dynapsys/arpx",
"Issues": "https://github.com/dynapsys/arpx/issues"
},
"split_keywords": [
"arp",
" certificates",
" http",
" https",
" lan",
" lets-encrypt",
" mkcert",
" network"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "e948b27d25e60922a728d700ead89ce4d62e3c6062370730eca203cb477edb73",
"md5": "3d7c4e6f09c56700c357fdcd8694bc33",
"sha256": "18615b4c92125cba844c7faf1fda7164b892cbe77236281c20d0437f68d7c086"
},
"downloads": -1,
"filename": "arpx-0.0.21-py3-none-any.whl",
"has_sig": false,
"md5_digest": "3d7c4e6f09c56700c357fdcd8694bc33",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 37324,
"upload_time": "2025-09-08T17:53:55",
"upload_time_iso_8601": "2025-09-08T17:53:55.667541Z",
"url": "https://files.pythonhosted.org/packages/e9/48/b27d25e60922a728d700ead89ce4d62e3c6062370730eca203cb477edb73/arpx-0.0.21-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "5c999edec34f09322ddb8c96dd1b6bc9a7321970c2483c755593ed5bc1a0de3f",
"md5": "eae6279657c6d47560cfc3b33bfd1f5e",
"sha256": "d8ed3f095290242497ba373593cd9a6278d86eb67672abd1c5693c141f6ae1c3"
},
"downloads": -1,
"filename": "arpx-0.0.21.tar.gz",
"has_sig": false,
"md5_digest": "eae6279657c6d47560cfc3b33bfd1f5e",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 38652,
"upload_time": "2025-09-08T17:53:57",
"upload_time_iso_8601": "2025-09-08T17:53:57.267261Z",
"url": "https://files.pythonhosted.org/packages/5c/99/9edec34f09322ddb8c96dd1b6bc9a7321970c2483c755593ed5bc1a0de3f/arpx-0.0.21.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-09-08 17:53:57",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "dynapsys",
"github_project": "arpx",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "arpx"
}
