semvec/pypi-packages huggingface dataset:
django-management-auth 0.0.0
Login to a Django application from a management command
Requires Python: >=3.8

# Django management auth

![CI](https://github.com/RealOrangeOne/django-management-auth/workflows/CI/badge.svg)
![PyPI](https://img.shields.io/pypi/v/django-management-auth.svg)
![PyPI - Python Version](https://img.shields.io/pypi/pyversions/django-management-auth.svg)
![PyPI - License](https://img.shields.io/pypi/l/django-management-auth.svg)

Login to a Django application from a management command.

## Installation

```
pip install django-management-auth
```

Then, add `management_auth` to `INSTALLED_APPS`.

Finally, add the required URLs:

```python
# urls.py

urlpatterns += [path(".login-as", include("management_auth.urls"))]
```

## Usage

Authentication happens using a short-lived signed URL, generated from a management command.

```
./manage.py login_as <username>
```

This will create a URL for `<username>`. By default, the URLs are valid for 60 seconds (configurable with `--timeout`).

### Fully-qualified URLs

Where possible, URLs, are displayed fully-qualified, such that they can be quickly clicked to log in.

- To specify manually, use `MANAGEMENT_AUTH_BASE_URL`
- For Wagtail users, `WAGTAILADMIN_BASE_URL` is used to create the URL.
- For `django.contrib.sites` users, `SITE_ID` is correctly considered

If no base URL is found, a relative path is shown.

## Design considerations

- Tokens are only valid for a short amount of time, intended to prevent reuse / sharing.
- Tokens are signed URLs, rather than requiring a database table. This means the validation view is faster and more lightweight, and a database leak doesn't risk exposing sessions.
- Because tokens are signed, they can be used multiple times (however this is a bad idea)
alivebot 0.1.22
A script to find and react to ALIVE commands in comments
Requires Python: >=3.6

# Alivebot

A script to find and react to !ALIVE commands in comments on the Hive blockchain.

*Please note that this software is in early Beta stage, and that you need to know what you are doing to use it.*

## Installation 

For Ubuntu and Debian install these packages:
```
sudo apt-get install python3-pip build-essential libssl-dev python3-dev python3-setuptools python3-gmpy2
```

### Install Python Packages

Install alivebot by (you may need to replace pip3 by pip):
```
sudo pip3 install -U alivebot beem hiveengine
```

## Configure And Run Alivebot

First clone the Github repository to your home directory:
```
cd ~
git clone https://github.com/flaxz/alivebot
```

After that edit your comment templates using Nano, there are 4 comment templates.
```
sudo apt install nano 
cd ~/alivebot/templates
ls
nano COMMENT-TEMPLATE-1-2-3-4
```

Then edit your configuration file.
```
cd ~/alivebot
nano alivebot.config
```

Copy your configuration and comment templates to your working directory.
```
cd ~/alivebot
sudo cp -R templates /usr/local/bin
sudo cp alivebot /usr/local/bin
sudo cp alivebot.config /usr/local/bin
sudo cp run-alivebot.sh /usr/local/bin
```

Make the startup scripts executable.
```
cd /usr/local/bin
sudo chmod u+x alivebot
sudo chmod u+x run-alivebot.sh
```

Copy the Systemd config to it's directory.
```
cd ~/alivebot
sudo cp alivebot.service /etc/systemd/system
```

Reload Systemd and start the bot.
```
sudo systemctl daemon-reload
sudo systemctl start alivebot.service
```

Get status and error messages.
```
sudo systemctl status alivebot.service
q
```

Stop the bot.
```
sudo systemctl stop alivebot.service
```

As has been stated above this bot is in early Beta and bugs and issues are likely to occur.