# abs-storage
## Installing
Before work with our storage, you need to install:
sudo apt-get install docker.io make docker-compose
Make and docker is not required features. This tools is needed for more useful development. We recommend to use Anaconda or another environment manager for safety system interpreter. You can download Anaconda [here](https://www.anaconda.com/). After installing Anaconda please create new environment:
conda create –name abc-storage python=3.7 conda activate
## Starting
Before starting please install all python package dependencies:
make deps
We have three mode of starting:
full subsystem
development
make
### docker-compose full
We use docker-compose for local development and starting you service and environment. If you want to start full subsystem, you need to do this:
make run-full
After that our service and environment is started. If you want to start our service the first time, docker container with service is built. Other container is pulled.
If you want to start service not first time, maybe you need rebuilt service for apply last changes:
make run-rebuild
### development
For development, you can use only environment:
make run-env
After that, it starts all dependencies services. Now, you can run our service in your IDE for development.
### make
For fast start our service we use command:
make run
## Environment variables
Our service takes all environments variables from config: deployments/.envs/local.env. More about it you can read into this file: abc_storage/__service/config.py. You can add new variables there and here: deployments/.envs/local.env.
We separates variables by namespaces, therefore we set prefix before variable name. You can see in files, which we denote above.
## Testing
We have three mode of testing:
unit testing
integration testing
all: unit and integration testing
We have three commands:
make test-integration
Before starting integration tests (above) you need to start environment:
make run-env
Unit tests:
make test-unit
All tests:
make test
## Notice
We use makefile as interface for communicate our application with our systems by command line while development and deployments
Metadata
Release files for abc-storage 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| abc_storage-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for abc_storage-0.1.0-py3-none-any.whl |
Release files / abc_storage-0.1.0-py3-none-any.whl
| Download URL | abc_storage-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
698a0961e556af81d99195ca13a637ef1eb968a7f2056977959a101f2deef039
|
|
BLAKE2b-256 checksum How to use checksums |
3790ff538acc34026567c19a5c8102ba3c3206a6ba4d80c00a649814790928e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.7
|
Security for abc-storage 0.1.0
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.