f-layer 2.0.0__py3-none-any.whl
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.
- f_layer-2.0.0.dist-info/METADATA +232 -0
- f_layer-2.0.0.dist-info/RECORD +45 -0
- f_layer-2.0.0.dist-info/WHEEL +4 -0
- f_layer-2.0.0.dist-info/entry_points.txt +2 -0
- f_layer-2.0.0.dist-info/licenses/LICENSE +201 -0
- flayer/__init__.py +5 -0
- flayer/__main__.py +247 -0
- flayer/_vpn_guest.py +130 -0
- flayer/core/__init__.py +1 -0
- flayer/core/config.py +198 -0
- flayer/core/contracts.py +114 -0
- flayer/core/lifecycle.py +767 -0
- flayer/core/state.py +351 -0
- flayer/diagnostics/__init__.py +20 -0
- flayer/diagnostics/benchmark.py +272 -0
- flayer/diagnostics/contracts.py +167 -0
- flayer/diagnostics/health.py +154 -0
- flayer/diagnostics/reporting.py +24 -0
- flayer/extensions/__init__.py +25 -0
- flayer/extensions/builtins.py +165 -0
- flayer/extensions/contracts.py +196 -0
- flayer/extensions/discovery.py +152 -0
- flayer/extensions/registry.py +347 -0
- flayer/guest.py +270 -0
- flayer/integrations/__init__.py +23 -0
- flayer/integrations/adapters.py +92 -0
- flayer/integrations/contracts.py +241 -0
- flayer/integrations/wire.py +273 -0
- flayer/profiles/__init__.py +33 -0
- flayer/profiles/_amnezia_export.py +176 -0
- flayer/profiles/_vless_guest.py +432 -0
- flayer/profiles/amneziawg.py +555 -0
- flayer/profiles/artifacts.py +609 -0
- flayer/profiles/gateway.py +729 -0
- flayer/profiles/static_site.py +596 -0
- flayer/profiles/vless.py +422 -0
- flayer/profiles/vpn.py +524 -0
- flayer/providers/__init__.py +1 -0
- flayer/providers/contracts.py +207 -0
- flayer/providers/lifecycle.py +177 -0
- flayer/providers/yandex.py +387 -0
- flayer/providers/yandex_lifecycle.py +781 -0
- flayer/py.typed +0 -0
- flayer/vpn_export.py +72 -0
- flayer/vpn_project.py +828 -0
|
@@ -0,0 +1,232 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: f-layer
|
|
3
|
+
Version: 2.0.0
|
|
4
|
+
Summary: Deploy and manage cloud gateways with explicit project configuration
|
|
5
|
+
Project-URL: Homepage, https://github.com/Fuzzy-Technologies/F-Layer
|
|
6
|
+
Project-URL: Documentation, https://fuzzy-technologies.github.io/F-Layer/
|
|
7
|
+
Project-URL: Repository, https://github.com/Fuzzy-Technologies/F-Layer
|
|
8
|
+
Project-URL: Issues, https://github.com/Fuzzy-Technologies/F-Layer/issues
|
|
9
|
+
Project-URL: Changelog, https://github.com/Fuzzy-Technologies/F-Layer/releases
|
|
10
|
+
Author: Fuzzy Technologies
|
|
11
|
+
License-Expression: Apache-2.0
|
|
12
|
+
License-File: LICENSE
|
|
13
|
+
Keywords: automation,cloud,infrastructure,security,yandex-cloud
|
|
14
|
+
Classifier: Intended Audience :: Developers
|
|
15
|
+
Classifier: Intended Audience :: System Administrators
|
|
16
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
19
|
+
Classifier: Topic :: System :: Systems Administration
|
|
20
|
+
Requires-Python: >=3.11
|
|
21
|
+
Provides-Extra: dev
|
|
22
|
+
Requires-Dist: cryptography==50.0.2; extra == 'dev'
|
|
23
|
+
Requires-Dist: hatchling==1.32.0; extra == 'dev'
|
|
24
|
+
Requires-Dist: mypy==2.3.1; extra == 'dev'
|
|
25
|
+
Requires-Dist: pytest-cov==7.1.0; extra == 'dev'
|
|
26
|
+
Requires-Dist: pytest==9.1.1; extra == 'dev'
|
|
27
|
+
Requires-Dist: ruff==0.16.6; extra == 'dev'
|
|
28
|
+
Requires-Dist: segno==1.6.6; extra == 'dev'
|
|
29
|
+
Provides-Extra: vpn
|
|
30
|
+
Requires-Dist: cryptography==50.0.2; extra == 'vpn'
|
|
31
|
+
Requires-Dist: segno==1.6.6; extra == 'vpn'
|
|
32
|
+
Description-Content-Type: text/markdown
|
|
33
|
+
|
|
34
|
+
# F-Layer
|
|
35
|
+
|
|
36
|
+

|
|
37
|
+
|
|
38
|
+
**Your cloud infrastructure, managed from one configuration.**
|
|
39
|
+
|
|
40
|
+
F-Layer is an open-source infrastructure automation platform for engineers,
|
|
41
|
+
small teams and applications that need repeatable deployments. Describe your
|
|
42
|
+
environment, create its resources, check their state and remove the resources
|
|
43
|
+
belonging to that deployment through the same CLI or Python API.
|
|
44
|
+
|
|
45
|
+
The main workflow in **F-Layer 2.0** is a self-hosted VPN on **Yandex Cloud**:
|
|
46
|
+
one server running **AmneziaWG 3.1** and **VLESS Reality**, with separate
|
|
47
|
+
connection files for each device. You own the cloud account, server and keys;
|
|
48
|
+
you pay the cloud provider for resources and traffic.
|
|
49
|
+
|
|
50
|
+
[Documentation](https://fuzzy-technologies.github.io/F-Layer/) ·
|
|
51
|
+
[English](https://fuzzy-technologies.github.io/F-Layer/en/) ·
|
|
52
|
+
[Русский](https://fuzzy-technologies.github.io/F-Layer/ru/) ·
|
|
53
|
+
[简体中文](https://fuzzy-technologies.github.io/F-Layer/zh-CN/) ·
|
|
54
|
+
[Releases](https://github.com/Fuzzy-Technologies/F-Layer/releases)
|
|
55
|
+
|
|
56
|
+
## What you get
|
|
57
|
+
|
|
58
|
+
- **A VPN you control:** provision the VM, network, firewall, public IP and disk,
|
|
59
|
+
install both services, and export private client profiles and native AmneziaVPN QR codes for both protocols.
|
|
60
|
+
- **Configurable resources:** choose CPU, RAM, platform, CPU performance level,
|
|
61
|
+
disk size and HDD/SSD type in `project.toml`.
|
|
62
|
+
- **One deployment lifecycle:** inspect status, recover interrupted cloud
|
|
63
|
+
operations and remove your stack using its retained local state.
|
|
64
|
+
- **More than VPN:** prepare restricted SSH gateways, run HTTP availability
|
|
65
|
+
and timing checks, or integrate the infrastructure APIs into your application.
|
|
66
|
+
|
|
67
|
+
## Quick Start
|
|
68
|
+
|
|
69
|
+
### Deploy with an AI assistant
|
|
70
|
+
|
|
71
|
+
Give an assistant with terminal access this task:
|
|
72
|
+
|
|
73
|
+
> Deploy my self-hosted VPN using F-Layer: https://github.com/Fuzzy-Technologies/F-Layer.
|
|
74
|
+
> Read its AI operator guide and use documentation matching the installed package.
|
|
75
|
+
> Ask for my cloud, region and devices. Install a verified package, prepare a
|
|
76
|
+
> private project and show the resources, access rules, costs and cleanup plan.
|
|
77
|
+
> Obtain my approval before creating paid resources. Deploy through F-Layer's
|
|
78
|
+
> public CLI, help import the client profiles, and verify actual traffic.
|
|
79
|
+
> Keep secrets local and report what passed, what remains untested and how to
|
|
80
|
+
> remove the deployment.
|
|
81
|
+
|
|
82
|
+
The [AI operator guide](https://fuzzy-technologies.github.io/F-Layer/en/guide/ai-operator/)
|
|
83
|
+
covers the full workflow. The assistant supplies your choices and runs F-Layer;
|
|
84
|
+
F-Layer supplies the configuration, deployment lifecycle and client artifacts.
|
|
85
|
+
|
|
86
|
+
### Deploy manually
|
|
87
|
+
|
|
88
|
+
**Outcome:** a server in your Yandex Cloud folder and private connection files
|
|
89
|
+
you can import on your devices. Finish by checking real traffic through each protocol.
|
|
90
|
+
|
|
91
|
+
**You need:** Linux or a user-managed WSL Linux distribution, Python 3.11+,
|
|
92
|
+
OpenSSH (`ssh` and `ssh-keygen`), and an authenticated
|
|
93
|
+
[Yandex Cloud CLI](https://yandex.cloud/en/docs/cli/quickstart) profile with
|
|
94
|
+
permissions in your chosen folder. Use an Ubuntu 24.04 **amd64** server image.
|
|
95
|
+
Git and Docker are not required to run the package. Windows can run local
|
|
96
|
+
package diagnostics; VPN deployment runs inside Linux/WSL.
|
|
97
|
+
|
|
98
|
+
#### 1. Install and check
|
|
99
|
+
|
|
100
|
+
Create and activate a virtual environment in Linux/WSL:
|
|
101
|
+
|
|
102
|
+
```bash
|
|
103
|
+
python3 -m venv ~/.venvs/flayer
|
|
104
|
+
source ~/.venvs/flayer/bin/activate
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
Download the wheel and `build-evidence.json` from the
|
|
108
|
+
[v2.0.0 release](https://github.com/Fuzzy-Technologies/F-Layer/releases/tag/v2.0.0).
|
|
109
|
+
Check the wheel SHA-256 against the build evidence, then install from the
|
|
110
|
+
download directory:
|
|
111
|
+
|
|
112
|
+
```bash
|
|
113
|
+
python -m pip install "./f_layer-2.0.0-py3-none-any.whl[vpn]"
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
After the separate PyPI publication, you can also install with
|
|
117
|
+
`python -m pip install "f-layer[vpn]==2.0.0"`. The `vpn` extra installs the
|
|
118
|
+
cryptography dependency needed for local key generation.
|
|
119
|
+
|
|
120
|
+
```bash
|
|
121
|
+
flayer --help
|
|
122
|
+
flayer check --format json
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
Expected: `"status": "ok"` and exit code `0`. This checks the local installation;
|
|
126
|
+
it does not contact the cloud or test VPN connectivity.
|
|
127
|
+
|
|
128
|
+
#### 2. Create your project
|
|
129
|
+
|
|
130
|
+
```bash
|
|
131
|
+
flayer project init ~/flayer-vpn
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
Edit `~/flayer-vpn/project.toml` before preparing it:
|
|
135
|
+
|
|
136
|
+
- Set `identity.scope_id` to your cloud folder ID and choose your project, stack and owner names.
|
|
137
|
+
- Set `cloud.yc_profile`, `zone_id` and `image_id` to your actual profile, zone
|
|
138
|
+
and image. Choose a subnet that does not overlap your other networks.
|
|
139
|
+
- Set `cloud.management_cidrs` to your administrator public IPv4 with `/32`.
|
|
140
|
+
- List your `devices` with unique tunnel addresses; the template includes
|
|
141
|
+
`laptop`. Choose full or split IPv4 routing in `[routes]`.
|
|
142
|
+
- Set `vless.target_host` and `server_name` to a reachable TLS 1.3 / HTTP/2
|
|
143
|
+
target with a matching certificate; replace the example hostname.
|
|
144
|
+
|
|
145
|
+
For explicit server sizing, uncomment the complete `[resources]` block in the template:
|
|
146
|
+
|
|
147
|
+
```toml
|
|
148
|
+
[resources]
|
|
149
|
+
platform_id = "standard-v3"
|
|
150
|
+
cores = 2
|
|
151
|
+
core_fraction = 50
|
|
152
|
+
memory_gib = 2
|
|
153
|
+
disk_size_gib = 10
|
|
154
|
+
disk_type = "network-hdd"
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
Check regional availability and the image's minimum disk size. Omitting this
|
|
158
|
+
block retains the default 2 vCPU, 2 GiB RAM and 20 GiB SSD configuration.
|
|
159
|
+
See [configuration](https://fuzzy-technologies.github.io/F-Layer/en/guide/configuration/)
|
|
160
|
+
for supported combinations. Keep the project outside Git and shared folders;
|
|
161
|
+
in WSL, use its Linux filesystem rather than `/mnt/c`.
|
|
162
|
+
|
|
163
|
+
#### 3. Prepare and deploy
|
|
164
|
+
|
|
165
|
+
`prepare` generates local keys and artifacts without cloud calls. After this
|
|
166
|
+
step, keep the configuration unchanged and retain the project directory.
|
|
167
|
+
|
|
168
|
+
```bash
|
|
169
|
+
flayer vpn prepare --project ~/flayer-vpn
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
Review the selected resources and their cost. **The next command creates paid
|
|
173
|
+
cloud resources.** Replace `YOUR_FOLDER_ID` with the same `identity.scope_id`:
|
|
174
|
+
|
|
175
|
+
```bash
|
|
176
|
+
flayer vpn deploy --project ~/flayer-vpn --allow-mutation --scope-confirm YOUR_FOLDER_ID
|
|
177
|
+
flayer vpn status --project ~/flayer-vpn
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
Expected: owned cloud resources, both server services reported as
|
|
181
|
+
`services-active`, and per-device files under `~/flayer-vpn/artifacts/`.
|
|
182
|
+
Server status alone does not prove that a client can access the Internet.
|
|
183
|
+
|
|
184
|
+
#### 4. Connect a device
|
|
185
|
+
|
|
186
|
+
The client guide uses **AmneziaVPN 5.0.3.0 on Android**. For the template's
|
|
187
|
+
`laptop` device, find these files inside your project:
|
|
188
|
+
|
|
189
|
+
- **AmneziaWG:** import `artifacts/device-laptop-amneziawg/amneziawg.conf`.
|
|
190
|
+
- **VLESS Reality:** import `artifacts/device-laptop-vless-reality/amnezia.vpn`,
|
|
191
|
+
or open `amnezia-qr-01.svg` from that directory on another screen and scan it
|
|
192
|
+
with AmneziaVPN's scanner. If several numbered QR files exist, scan all of
|
|
193
|
+
them in the same import session.
|
|
194
|
+
|
|
195
|
+
Connect one protocol at a time. Open an HTTPS site by hostname, verify the
|
|
196
|
+
server's public IPv4 as your exit address, and check DNS, routing and VPN/TUN settings.
|
|
197
|
+
This version routes **IPv4**; disable IPv6 on the client/device to prevent bypass.
|
|
198
|
+
The project's IPv6 setting does not change your device settings.
|
|
199
|
+
Keep client files and QR codes private: they grant access to your VPN.
|
|
200
|
+
|
|
201
|
+
See the [client walkthrough](https://fuzzy-technologies.github.io/F-Layer/en/guide/#4-connect-a-device)
|
|
202
|
+
for protocol-specific checks and import details.
|
|
203
|
+
|
|
204
|
+
## Manage your deployment
|
|
205
|
+
|
|
206
|
+
Use `flayer vpn status --project ~/flayer-vpn` to inspect your server.
|
|
207
|
+
For an interrupted cloud operation, retain the project and follow the
|
|
208
|
+
[recovery guide](https://fuzzy-technologies.github.io/F-Layer/en/guide/#5-recover-or-remove-the-deployment).
|
|
209
|
+
When you want to remove this project's cloud resources:
|
|
210
|
+
|
|
211
|
+
```bash
|
|
212
|
+
flayer vpn destroy --project ~/flayer-vpn --allow-mutation --scope-confirm YOUR_FOLDER_ID
|
|
213
|
+
```
|
|
214
|
+
|
|
215
|
+
Verify removal in the report and cloud folder. Local keys, artifacts and state
|
|
216
|
+
remain on disk. Disconnecting a client does not remove billable cloud resources.
|
|
217
|
+
|
|
218
|
+
**Current boundaries:** Yandex Cloud is the implemented provider. Prepared
|
|
219
|
+
projects are immutable; in-place resizing, device addition/revocation and key
|
|
220
|
+
rotation are not available through the VPN CLI. Changing these settings requires
|
|
221
|
+
a new project and the documented lifecycle for the old deployment.
|
|
222
|
+
|
|
223
|
+
## Explore further
|
|
224
|
+
|
|
225
|
+
[SSH gateway](https://fuzzy-technologies.github.io/F-Layer/en/guide/first-deployment/) ·
|
|
226
|
+
[CLI diagnostics](https://fuzzy-technologies.github.io/F-Layer/en/guide/cli/) ·
|
|
227
|
+
[Python API](https://fuzzy-technologies.github.io/F-Layer/en/api/) ·
|
|
228
|
+
[Changelog](https://github.com/Fuzzy-Technologies/F-Layer/blob/master/CHANGELOG.md)
|
|
229
|
+
|
|
230
|
+
Built by **Fuzzy Technologies**. Licensed under
|
|
231
|
+
[Apache 2.0](https://github.com/Fuzzy-Technologies/F-Layer/blob/master/LICENSE).
|
|
232
|
+
To contribute, start with [CONTRIBUTING.md](https://github.com/Fuzzy-Technologies/F-Layer/blob/develop/CONTRIBUTING.md).
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
flayer/__init__.py,sha256=5urI2QsgDBuEuYsvmjuVWQ7H_eWpVVdCZQKuNGyx1a8,93
|
|
2
|
+
flayer/__main__.py,sha256=qQNdXlY0XcpsFjAM4jDenXta4I5HHijGFjpL-k5pk70,10113
|
|
3
|
+
flayer/_vpn_guest.py,sha256=wIZmLKB-2KsgMNnfHfN1OHkGK2uElu6iDk2bBTAFTRs,4485
|
|
4
|
+
flayer/guest.py,sha256=0MTmu8-73F0ip4URhxwgWglHOswWqOr04oQz_PKns9I,11102
|
|
5
|
+
flayer/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
|
|
6
|
+
flayer/vpn_export.py,sha256=zXrwNHcJytdpF6T2GHMWcpaSzdrQ9GwHYrow5XyX3Dg,3100
|
|
7
|
+
flayer/vpn_project.py,sha256=5G8SrAoZf5jXwkAeyGugTSryshWEaCUznc0ueWb91iw,35810
|
|
8
|
+
flayer/core/__init__.py,sha256=eGJGFDVs30DTKCNvzZ154Eqa1qWFih-r_3HeXlLeZtA,76
|
|
9
|
+
flayer/core/config.py,sha256=-J4Sg-k0Dj7wm5DfpQJo8H19CIyBUV9Op_LWIOR35EE,6699
|
|
10
|
+
flayer/core/contracts.py,sha256=LByizB-LsnOpVLO3c9RnfiKMNeOfIfoAjA31uR2Cz4c,3922
|
|
11
|
+
flayer/core/lifecycle.py,sha256=7mbbuLKYT7hElTCnhxAJ1QqiKqSyP8tR18DdhbPLp64,28886
|
|
12
|
+
flayer/core/state.py,sha256=RUGUR6T87ytLXk5r9rJOyttMdzgVZZCo6WsGPhzmFM0,11144
|
|
13
|
+
flayer/diagnostics/__init__.py,sha256=3rwlXBYJ7sqCDsSSxwQK_Wxm58LsWGo0FAAAWWN0OP8,782
|
|
14
|
+
flayer/diagnostics/benchmark.py,sha256=jGu2ha0HXHT_UUvTEsEN-24jTQrD7ed-XiIJNzrQ6hw,9383
|
|
15
|
+
flayer/diagnostics/contracts.py,sha256=w_HF1i5Ww2eRd7podQ1PNFf5U4HF1Dx8NDhuo82Lank,5117
|
|
16
|
+
flayer/diagnostics/health.py,sha256=iV_4QIt7jy9a4iEuVmGyamkfiBZQGpv9G0n1k5f1M0I,4997
|
|
17
|
+
flayer/diagnostics/reporting.py,sha256=ZLf4_dnUc2Q4Ttq2JMWsm_Vg_pK2ZB2z90JScEhqOFk,769
|
|
18
|
+
flayer/extensions/__init__.py,sha256=1jb-GFEGjZkfmdW4aM5VxOZK5z2lKgrePVwfUcdCh-I,800
|
|
19
|
+
flayer/extensions/builtins.py,sha256=TcwRGSJqhaBxqXTGXP3OPOOxYJ2vqgOwRd0N6OaDkNQ,5963
|
|
20
|
+
flayer/extensions/contracts.py,sha256=aLHuAwaWu0qoGzKJEZCEoAjw7_BNCXBVydZkGciXJqk,7113
|
|
21
|
+
flayer/extensions/discovery.py,sha256=7nCrePWo0RracBZa3eBbm_TdZh_CF2gJoOWmVSyjWJI,6029
|
|
22
|
+
flayer/extensions/registry.py,sha256=HHvUK4dXUnnUBcgnIp9QSv9bsL7cVurjGD4moFcWheA,13134
|
|
23
|
+
flayer/integrations/__init__.py,sha256=Z9KujhbzFVSUh4x6tS2tnvXoA6AlBoahLKM4FpGB8G8,821
|
|
24
|
+
flayer/integrations/adapters.py,sha256=srpu-uVkA2QWbTCh2x5EB_ARK7TVei7GbBhwER2469Y,3415
|
|
25
|
+
flayer/integrations/contracts.py,sha256=4cxIKM46Xw5A-IbkpVu4PpnhgiCbqhK0hfnbUAlJcGk,8728
|
|
26
|
+
flayer/integrations/wire.py,sha256=YI5x1LlSWNdnGOuq78OsyKHXLZ8_D5nmUXP6nbrNMXw,10279
|
|
27
|
+
flayer/profiles/__init__.py,sha256=AfZu70kV_bn8aV2QAqOIutGWgQjftzLABue9CQyvoRs,902
|
|
28
|
+
flayer/profiles/_amnezia_export.py,sha256=RjN9jp5tRrooQUif43L9egrwJxNWHyZ7AyehHeJpJFU,7330
|
|
29
|
+
flayer/profiles/_vless_guest.py,sha256=qwhnGFlhowevQbBqzIbMJE3BkwMAT52l6SXyareZbhI,16760
|
|
30
|
+
flayer/profiles/amneziawg.py,sha256=FWiSAYU6kg0OTPCAbXdEItuOQeleXqCdRvy6e1qEbp0,21755
|
|
31
|
+
flayer/profiles/artifacts.py,sha256=thtqVJsTR9ndfq2UfVC9WNtBoMgVIAUhrLaO-eabTRw,22007
|
|
32
|
+
flayer/profiles/gateway.py,sha256=7_jFOVCvZH8TPVcCoKCyJc7C7M9OY2BevB7NWTzGk9w,30561
|
|
33
|
+
flayer/profiles/static_site.py,sha256=DmrDFHvSMBuAkQp6EYI8FReQT-9D8TBjbKT8xVWAO6w,24774
|
|
34
|
+
flayer/profiles/vless.py,sha256=qkatFisDCAbc9QsaafnGFISGnfew_1cf7eDBI55pgms,16762
|
|
35
|
+
flayer/profiles/vpn.py,sha256=ocDJ2Y9czrBJx2s4tYFU-AyY3xEUbeykOQokobizLsU,20391
|
|
36
|
+
flayer/providers/__init__.py,sha256=pSsMoj5nR_-pd5MErcK42f4lFmgvITRbEZ6NfoNini8,78
|
|
37
|
+
flayer/providers/contracts.py,sha256=umiy1GVwDA-zrDGU9Ry7G52gx67Cxw02NwXCNRsvUfo,6793
|
|
38
|
+
flayer/providers/lifecycle.py,sha256=IUNHV9F7zB2kkaGBhC91Mt89gcUv7pOVuDjK9pwHxgI,6294
|
|
39
|
+
flayer/providers/yandex.py,sha256=qLzwAfYVz0hbEMfR2Lliho4Y9y7MBmTJX5OscsLZrzk,14065
|
|
40
|
+
flayer/providers/yandex_lifecycle.py,sha256=4vRbSpI3iuIaKjGMYxSywpv7n4MJDBHBzsZxHMYdjyo,30078
|
|
41
|
+
f_layer-2.0.0.dist-info/METADATA,sha256=pv-COj3R8ivCiatnkgjhmtpt7kZjbfLKmNoAI5BDTLU,10352
|
|
42
|
+
f_layer-2.0.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
|
|
43
|
+
f_layer-2.0.0.dist-info/entry_points.txt,sha256=sCwq5X1obrUEhEUZjxAkYoGih0svwgMK0zHGLY6Rtm8,48
|
|
44
|
+
f_layer-2.0.0.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
|
|
45
|
+
f_layer-2.0.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|