Metadata-Version: 2.1
Name: arcsecond
Version: 3.0.0
Summary: CLI for arcsecond.io
Home-page: https://github.com/arcsecond-io/cli
Author: Cedric Foellmi
Author-email: cedric@arcsecond.io
License: MIT
Platform: any
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: POSIX
Classifier: Operating System :: MacOS
Classifier: Operating System :: Unix
Classifier: Operating System :: Microsoft :: Windows
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development :: Libraries :: Python Modules
License-File: LICENSE
Requires-Dist: click
Requires-Dist: requests
Requires-Dist: requests-toolbelt
Requires-Dist: configparser
Requires-Dist: progress

[![Upload Python Package to Pypi](https://github.com/arcsecond-io/cli/actions/workflows/pythonpublish.yml/badge.svg)](https://github.com/arcsecond-io/cli/actions/workflows/pythonpublish.yml) [![Run Tests and Linting](https://github.com/arcsecond-io/cli/actions/workflows/pythonpackage.yml/badge.svg)](https://github.com/arcsecond-io/cli/actions/workflows/pythonpackage.yml) [![Deploy Docs](https://github.com/arcsecond-io/cli/actions/workflows/docsdeploy.yml/badge.svg)](https://github.com/arcsecond-io/cli/actions/workflows/docsdeploy.yml) [![Downloads](http://pepy.tech/badge/arcsecond)](http://pepy.tech/project/arcsecond)

# Arcsecond CLI

The Command-line interface (CLI) for Arcsecond. It can be used as Python 
module too. The CLI makes it easy to login/register and access Arcsecond resources,
public and private ones.

[Read the docs](https://docs.arcsecond.io/cli)

# Development

To start developing the arcsecond CLI, fork the project, `git clone` it, 
then, in the arcsecond-cli folder, do 
(assuming [virtualenv](https://virtualenv.pypa.io/en/stable/) is installed):

```bash
$ cd ~/arcsecond-cli
$ virtualenv --python=pythonX.Y env
$ source env/bin/activate
$ pip install -e .
``` 

The last line ensure you can call the "locally installed" version of the 
code of that folder. Once done one first time, only the `source 
env/bin/activate` is needed when you restart a debugging session.
