…es for api, chat id, photo capture support, and testing. Instructions for setup are included. Built on the current email implementation using all standard libraries or those already used within motionEye

Removed test material I left in by accident.

…t a caption to the image to make it cleaner and take up less space. Also removed email formatting to take up less space

…o dev

Add link to release notes in README

Add support for privacy mask

- Moved to debian buster.
- Some packages need to come from sid (E.g. motion itself). In that
  case, make the build reproducible by fixing sid to a snapshot.

Fix docker build, move to Debian buster.

- Added RUN_UID and RUN_GID args to Dockerfile. This allows the creation
  of an image that runs as a non-privileged user. If no args are
  specified at the container creation time, UID and GID will default
  to root/root, as before.
- Reordered commands in the Dockerfile a bit.
- Removed /var/run/motion as a PID, since we may want to run
  another instance of motion on a docker and this could prevent it.
- Added docker specific documentation.

Add support to run motionEye as a non-root user.

Delete also thumbnails with movies

Add Delete button to picture dialog

Add basic validation to webhook URL to avoid crash in config parsing

I believe '-rm' needs to be '--rm'

Update README.md

I tried to build my own docker image and got the following error:

```
Reading package lists...
E: Release file for http://snapshot.debian.org/archive/debian/20200630T024205Z/dists/sid/InRelease is expired (invalid since 91d 3h 59min 33s). Updates for this repository will not be applied.
```

The proposed change aims to replace the hardcoded snapshot link with an actual snapshot valid on time of build and decrease chance of such an issue in future

replace hardcoded Debian snapshot with latest

Added support for telegram motion notifications (UI & Backend).

….file

At line 329, motionEye is requesting a Google Drive scope of "drive" which grants access to *all* of a user's files. This PR reduces the scope to "drive.file" which allows motionEye to create files on a user's Google Drive and to then only access/delete those files. This is the recommended best practice from Google, ie. to only request the minimum scope necessary for the application's needs. See https://developers.google.com/drive/api/v2/about-auth

Update to uploadservices.py to reduce the Google Drive scope to drive…

docker compose override with reasonable defaults

fixed typos

fix broken docker build (issue #2193)

Python breaks on the third split (`libcamera interfaces=0`). As it splits on the empty part, it becomes `[libcamera, interfaces=0]`, which it can't split any further on an equal sign.

Signed-off-by: MichaIng <[email protected]>
Co-authored-by: Christian Clauss <[email protected]>

Create pypi_daily_build.yml

generate build on main pypi site

Preparing for a new workflow on dev which triggers on (GitHub) releases. The daily uploads might disturb in this case.

The workflow is renamed on default branch so that a workflow with this name can be manually triggered from dev as well manually.

Signed-off-by: MichaIng <[email protected]>

required for it to run and also to allow manual "workflow_dispatch" triggers.

Signed-off-by: MichaIng <[email protected]>

Avoid concurrent and doubled execution. Update setup-python action. Do not install packages which are not required for Python 2 code lint. Do not install and run pytest since the Python 2 branch does not contain any tests.

Signed-off-by: MichaIng <[email protected]>

Add scheduled workflow to default branch

Signed-off-by: MichaIng <[email protected]>

Start with a minimal approach for releases based on action version string of current branch/tag