semvec/pypi-packages huggingface dataset:
rtconfig 0.1.8
A simple python real-time remote configuration framework.
License: BSD
Requires Python: >=3.5

## rtconfig

A simple Python lib for manage remote server configuration. 
- Configuration remote unified management center.
- When the configuration changes, pushed to client in real time.

## Installing
```
pip install rtconfig
```

## Server deploy
You can start server directly by single process.
```
python -m rtconfig.server
```
Command options:
- --host: str, server host
- --port: str, server port
- --auto-reload: bool, if auto reload
- --store-type: str, rtconfig server store type
- --broker-url: str, rtconfig server broker url
- --login-disable: bool, rtconfig server disable login
- --config: str, rtconfig server config file path

## Client connect
Create a new python module `conf.py`, then write code like this:
```
from rtconfig import RtConfigClient
client = RtConfigClient('demo',ws_url='ws://127.0.0.1:8089',config_module=globals())
```
So, you can use real time configuration like this:
```
conf.config_name
```

## Configuration
You can create `service.py` python config file, And add file path to params `--config=services.py`. 

Configuration options:

| config name |  type  | default | description |
|--------|--------|--------|--------|
|    DEBUG    | bool |   false   |    debug mode    |
|    MAX_CONNECTION  | int |  1024   |    max client connections    |
|    STORE_TYPE   | string  | json_file   |  data store type    |
|    BROKER_URL   |  string  |  |  data store broker url   |
|    LOGIN_DISABLED   |  bool  | false  |  server disable login   |
|    OPEN_CLIENT_AUTH_TOKEN   |  bool  | false |  data store broker url   |

## Config data store method broker url
json_file
>BROKER_URL = "~/rtconfig" (默认可不填)

redis
>BROKER_URL = "redis://127.0.0.1:6379/0"

mongodb
>BROKER_URL = "mongodb://127.0.0.1:27017/demo?connect=false"

## Notes
- `rtconfig` not support multiprocess deploy now.
dm.zope.reseller 1.1
Zope package for reselling
License: BSD
Keywords: product order delivery management reselling

A package to support resellers.

It maintains in a postgres database information about providers,
products (called articles),
clients, orders and deliveries. It uses a Zope2 frontend
for user interaction.

It assumes a single (implicit) reseller
and several "provider"s and "client"s.

Each provider provides "article"s which the clients can buy.

Clients buy articles in "unit"s; the provider provides them
in "packet"s which contain an integral number of "unit"s. If
the "packet_size" is different from 1, then the reseller repackages
the delivered articles for its clients.

The reseller continously collects "client_order_item"s and
periodically issues "order"s to a provider consisting of
"provider_order_item"s.

The reseller occationally receives a "provider_delivery" for an order
consisting of "provider_delivery_item"s and splits them into
"client_delivery_item"s.

There is a special client, used as stock. It can be used to
balance orders and deliveries. It (and it alone) can have
negative "unit" values in its "client_delivery_items" - indicating
that units have been taken out of the stock.

Usually, we do not delete items. Instead, we mark them as not "active".
This is in order not to break references.