Overview
cloudcix is a Python client for the CloudCIX REST API for rapidly building secure, scalable CloudCIX applications.
For more information about CloudCIX, see here.
Installation
Prerequisites
Create an account on the CloudCIX Platform
Retrieve your API Key
Under the My Membership tab in the sidebar, click on Member Details
The API Key should be available at the top of the form
Ensure that you have both Python and pip installed
Installing the cloudcix library
The cloudcix library is installed using the pip module.
Depending on your version of Python, you need to install different versions of cloudcix
- Python3
pip3 install -U cloudcix
- Python2
pip install -U 'cloudcix<0.3'
The 0.2 releases are the last to support Python2. If you still use Python2 we recommend you upgrade to Python3 as support will be dropped for these versions in time.
Required settings
In order to run a project, the module requires some settings to exist.
The variables required are as follows:
CLOUDCIX_API_URL = https://legacyapi.api.cloudcix.com/ - The base url of the Python2 API
CLOUDCIX_API_V2_URL = https://api.cloudcix.com/ - The API name is prepended to this url after the https:// for the Python3 API.
CLOUDCIX_API_VERSION = 2 - The version of the api
CLOUDCIX_API_USERNAME - The email of the account that you signed up with
CLOUDCIX_API_PASSWORD - The password associated with your CloudCIX account
CLOUDCIX_API_KEY - The API key associated with your CloudCIX Member (see Prerequisites)
These variables can be declared in a settings file, as follows
# In main python script
import os
os.environ.setdefault('CLOUDCIX_SETTINGS_MODULE', 'my_project.my_settings')# In my_project/my_settings.py
CLOUDCIX_API_URL = 'https://legacyapi.api.cloudcix.com/'
CLOUDCIX_API_V2_URL = 'https://api.cloudcix.com/'
CLOUDCIX_API_USERNAME = 'EMAIL' # CloudCIX login
CLOUDCIX_API_PASSWORD = 'PASSWORD' # CloudCIX password
CLOUDCIX_API_KEY = 'NUMBER/CHARACTER STRING' # CloudCIX api key
CLOUDCIX_API_VERSION = 2 # CloudCIX versionExamples
See here for examples on how to use this library.
1 maintainer
Metadata
1 maintainer
Release files for cloudcix 5.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cloudcix-5.0.11.tar.gz | 26.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cloudcix-5.0.11-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 62.2 kB
Release files / cloudcix-5.0.11.tar.gz
| Download URL | cloudcix-5.0.11.tar.gz |
|---|---|
| Size | 26.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3af7609c2f1ea967c9dfba7c133cfe8994a5049ae0447619fea1a6fd5a88540
|
|
BLAKE2b-256 checksum How to use checksums |
d768f3ea87789d7048031ab8083004e5020121305f693970ff3eb1a4f130b321
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / cloudcix-5.0.11-py2.py3-none-any.whl
| Download URL | cloudcix-5.0.11-py2.py3-none-any.whl |
|---|---|
| Size | 35.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
198d31b09ee9aa11ff9fde5186f6c472f4afe752a6a68c0068fe80098d4049f3
|
|
BLAKE2b-256 checksum How to use checksums |
8efc599ec5a5f8bc8e8d6bf67a36c49c2d1c28ac82bb352f04277cdef2e9819c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for cloudcix 5.0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
