CommunityScrapers VS controller_configuration

A quick glance at the page shows some features that normal "video organizers" don't generally have:

- Metadata scrapers (core + community ones [which, seems to be A LOT of them, see https://github.com/stashapp/CommunityScrapers/tree/master/sc...]) tailored to adult sites

- Videos also have N scenes, which also can be tagged

- Videos (and scenes) have "performers" and tags, rather than just one video file having actors/actresses and categories

- Videos/scenes have markers with tags

Doesn't seem like the feature set (except the scrapers) HAVE to be adult-only, but I guess there is a big audience enough to justify a niche application like this.

Would someone be able to use the data within this stash scraper .yml file and use it to create a .py file for a ThePornDB scraper like one of the "site" scrapers here?. I tried to find a "relatively" tame example/reference for a page to be scraped, buuuut I couldn't so it's SUPER NSFW.

It has some porn specific features, like bookmarking/tagging certain scenes in a video. And yes it does recognize metadata for xxx performers, xxx movies and also xxx videos clips that aren't full movies, the metadata is scraped from a lot of sites, just check out the community scrapers https://github.com/stashapp/CommunityScrapers/tree/master/scrapers They also have new interesting project called stashbox for sharing the scraped metadata in a centralized database, so that users can contribute their own metadata fixes, etc. https://github.com/stashapp/stash-box

I am new to Github and I am trying to use this repo.

infra.controller_configuration 2.5.1 has been released. This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules.

The controller_configuration collection version 2.4.0 has been released.

The Infra config as Code collection group will have a Public Office hours meeting on May 11th at 9am EST/1pm UTC. Details here.

one thing is to play to what you know. Also know that collections can be roles, modules, or both. A few biased collections to look at to see the difference would be infra.controller_configuration - a set of roles to implement either the awx.awx collection or ansible.controller collection for doing configuration as code.

multiple collections with grouped roles, then playbooks to execute those roles as needed. You can also do role include like dispatch here to make it more flexible.

The infra collections have had recent updates: * infra.ah_configuration 1.1.0 Automation hub and galaxy_ng configuration. Majorly improved testing and as a result of fixes all modules and roles work on the last 3 versions of galaxy_ng and Automation Hub. * infra.controller_configuration 2.2.5 Various fixes and additions and improvements to collection, including methods to export configuration files from controller to be used by the collection. * infra.ee_utilities 2.0.6 Updated several bugs and add ability to use types in collection requirements for building execution environments

All of the collections in this group have recently released changes. This includes: * infra.controller_configuration 2.1.9 released to be compatible with recently added AWX changes. Changelog here. * infra.ah_configuration 0.9.2 Automation hub and galaxy_ng configuration. Fixed various major errors, including a major publishing error. Changelog here. * infra.ee_utilities 2.0.1 Updated to add several use cases to Execution Environment Creation. * infra.aap_utilities 2.2.2 Update to OCP installer to allow individual components.

For the server configuration, its on the kubernetes side, however for the AWX configuration of projects, job templates, credentials and the like is the redhat_cop.controller_configuration collection. It uses the awx.awx collection or the ansible.controller configuration to interact with the API to manage things in AWX. The collections are built to work with Ansible Automation Controller, but 99.9% of the time its going to work with AWX.