{"id":32525965,"url":"https://github.com/ansible-collections/community.beszel","last_synced_at":"2025-10-28T09:54:52.338Z","repository":{"id":307902464,"uuid":"1028585540","full_name":"ansible-collections/community.beszel","owner":"ansible-collections","description":"Ansible content to automate the configuration of Beszel Hub and Agents.","archived":false,"fork":false,"pushed_at":"2025-10-11T17:51:30.000Z","size":109,"stargazers_count":7,"open_issues_count":4,"forks_count":5,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-10-20T03:35:00.942Z","etag":null,"topics":["ansible","beszel","collection","community"],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/ansible-collections.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":"MAINTAINERS","copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-07-29T18:45:44.000Z","updated_at":"2025-10-18T20:26:24.000Z","dependencies_parsed_at":"2025-08-26T16:43:13.591Z","dependency_job_id":"4de4f0af-10b5-43e0-b76f-ade930e5671f","html_url":"https://github.com/ansible-collections/community.beszel","commit_stats":null,"previous_names":["ansible-collections/community.beszel"],"tags_count":3,"template":false,"template_full_name":"ansible-collections/collection_template","purl":"pkg:github/ansible-collections/community.beszel","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ansible-collections%2Fcommunity.beszel","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ansible-collections%2Fcommunity.beszel/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ansible-collections%2Fcommunity.beszel/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ansible-collections%2Fcommunity.beszel/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/ansible-collections","download_url":"https://codeload.github.com/ansible-collections/community.beszel/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/ansible-collections%2Fcommunity.beszel/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":281418064,"owners_count":26497723,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-10-28T02:00:06.022Z","response_time":60,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ansible","beszel","collection","community"],"created_at":"2025-10-28T09:52:46.444Z","updated_at":"2025-10-28T09:54:52.333Z","avatar_url":"https://github.com/ansible-collections.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Ansible Collection - `community.beszel`\n\u003c!-- Add CI and code coverage badges here. Samples included below. --\u003e\n[![CI](https://github.com/ansible-collections/community.beszel/actions/workflows/ansible-test.yml/badge.svg)](https://github.com/ansible-collections/community.beszel/actions)\n[![Ansible Lint](https://github.com/ansible-collections/community.beszel/actions/workflows/ansible-lint.yml/badge.svg)](https://github.com/ansible-collections/community.beszel/actions)\n[![Molecule](https://github.com/ansible-collections/community.beszel/actions/workflows/ansible-molecule.yml/badge.svg)](https://github.com/ansible-collections/community.beszel/actions)\n[![Codecov](https://img.shields.io/codecov/c/github/ansible-collections/community.beszel)](https://codecov.io/gh/ansible-collections/community.beszel)\n\n\u003c!-- Describe the collection and why a user would want to use it. What does the collection do? --\u003e\n\n## Our mission\n\n\u003c!-- Put your collection's mission statement in here. Example follows. --\u003e\n\nAt `community.beszel`, our mission is to make automation against [Beszel](https://beszel.dev/) simple. We aim to provide Ansible content that you can use to automate the configuration of [Beszel Hub and Agents](https://beszel.dev/guide/what-is-beszel#architecture).\n\nWe welcome members from all skill levels to participate actively in our open, inclusive, and vibrant community.\nWhether you are an expert or just beginning your journey with Ansible and `community.beszel`,\nyou are encouraged to contribute, share insights, and collaborate with fellow enthusiasts!\n\n## Code of Conduct\n\nWe follow the [Ansible Code of Conduct](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html) in all our interactions within this project.\n\nIf you encounter abusive behavior, please refer to the [policy violations](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html#policy-violations) section of the Code for information on how to raise a complaint.\n\n## Communication\n\n\u003c!--\nIf your collection is not present on the Ansible forum yet, please check out the existing [tags](https://forum.ansible.com/tags) and [groups](https://forum.ansible.com/g) - use what suits your collection. If there is no appropriate tag and group yet, please [request one](https://forum.ansible.com/t/requesting-a-forum-group/503/17).\n--\u003e\n\n* Join the Ansible forum:\n  * [Get Help](https://forum.ansible.com/c/help/6): get help or help others. Please add appropriate tags if you start new discussions, for example the `beszel` tag.\n  * [Posts tagged with 'beszel'](https://forum.ansible.com/tag/beszel): subscribe to participate in collection/technology-related conversations.\n  * [The `community-beszel` collection group on the Ansible forum](https://forum.ansible.com/g/): by joining the team you will automatically get subscribed to the posts tagged with [beszel](https://forum.ansible.com/tags).\n  * [Social Spaces](https://forum.ansible.com/c/chat/4): gather and interact with fellow enthusiasts.\n  * [News \u0026 Announcements](https://forum.ansible.com/c/news/5): track project-wide announcements including social events. The [Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn), which is used to announce releases and important changes, can also be found here.\n\nFor more information about communication, see the [Ansible communication guide](https://docs.ansible.com/ansible/devel/community/communication.html).\n\n## Contributing to this collection\n\n\u003c!--Describe how the community can contribute to your collection. At a minimum, fill up and include the CONTRIBUTING.md file containing how and where users can create issues to report problems or request features for this collection. List contribution requirements, including preferred workflows and necessary testing, so you can benefit from community PRs. If you are following general Ansible contributor guidelines, you can link to - [Ansible Community Guide](https://docs.ansible.com/ansible/devel/community/index.html). List the current maintainers (contributors with write or higher access to the repository). The following can be included:--\u003e\n\nThe content of this collection is made by people like you, a community of individuals collaborating on making the world better through developing automation software. Read the [CONTRIBUTING.md](CONTRIBUTING.md) file for steps on how to get started contributing to `community.beszel`.\n\nWe are actively accepting new contributors and all types of contributions are very welcome.\n\nDon't know how to start? Refer to the [Ansible community guide](https://docs.ansible.com/ansible/devel/community/index.html)!\n\nWe also use the following guidelines:\n\n* [Collection review checklist](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_reviewing.html)\n* [Quick-start development guide](https://docs.ansible.com/ansible/devel/community/create_pr_quick_start.html)\n* [Ansible development guide](https://docs.ansible.com/ansible/devel/dev_guide/index.html)\n* [Ansible collection development guide](https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html#contributing-to-collections)\n\n## Collection maintenance\n\nThe current maintainers are listed in the [MAINTAINERS](MAINTAINERS) file. If you have questions or need help, feel free to mention them in the proposals.\n\nTo learn how to maintain/become a maintainer of this collection, refer to the [Maintainer guidelines](https://docs.ansible.com/ansible/devel/community/maintainers.html).\n\nIt is necessary for maintainers of this collection to be subscribed to:\n\n* The collection itself (the `Watch` button -\u003e `All Activity` in the upper right corner of the repository's homepage).\n* The [news-for-maintainers repository](https://github.com/ansible-collections/news-for-maintainers).\n\nThey also should be subscribed to Ansible's [The Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn).\n\n## Governance\n\n\u003c!--Describe how the collection is governed. Here can be the following text:--\u003e\n\nThe process of decision making in this collection is based on discussing and finding consensus among participants.\n\nEvery voice is important. If you have something on your mind, create an issue or dedicated discussion and let's discuss it!\n\n## Tested with Ansible\n\n\u003c!-- List the versions of Ansible the collection has been tested with. Must match what is in galaxy.yml. --\u003e\n\nAnsible Core 2.17, 2.18 and 2.19.\n\n## External requirements\n\n\u003c!-- List any external resources the collection depends on, for example minimum versions of an OS, libraries, or utilities. Do not list other Ansible collections here. --\u003e\n\nTo use the modules in this collection you will need:\n\n- Python \u003e= 3.9\n- Pocketbase \u003e= 0.15.0\n\n## Using this collection\n\n\u003c!--Include some quick examples that cover the most common use cases for your collection content. It can include the following examples of installation and upgrade (change NAMESPACE.COLLECTION_NAME correspondingly):--\u003e\n\n### Installing the Collection from Ansible Galaxy\n\nBefore using this collection, you need to install it with the Ansible Galaxy command-line tool:\n\n```bash\nansible-galaxy collection install community.beszel\n```\n\nYou can also include it in a `requirements.yml` file and install it with `ansible-galaxy collection install -r requirements.yml`, using the format:\n\n```yaml\n---\ncollections:\n  - name: community.beszel\n```\n\nNote that if you install the collection from Ansible Galaxy, it will not be upgraded automatically when you upgrade the `ansible` package. To upgrade the collection to the latest available version, run the following command:\n\n```bash\nansible-galaxy collection install community.beszel --upgrade\n```\n\nYou can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax to install version `0.1.0`:\n\n```bash\nansible-galaxy collection install community.beszel:==0.1.0\n```\n\nSee [using Ansible collections](https://docs.ansible.com/ansible/devel/user_guide/collections_using.html) for more details.\n\n## Release notes\n\nSee the [changelog](https://github.com/ansible-collections/community.beszel/tree/main/CHANGELOG.rst).\n\n## Roadmap\n\n\u003c!-- Optional. Include the roadmap for this collection, and the proposed release/versioning strategy so users can anticipate the upgrade/update cycle. --\u003e\n\n## More information\n\n\u003c!-- List out where the user can find additional information, such as working group meeting times, slack/IRC channels, or documentation for the product this collection automates. At a minimum, link to: --\u003e\n\n- [Ansible user guide](https://docs.ansible.com/ansible/devel/user_guide/index.html)\n- [Ansible developer guide](https://docs.ansible.com/ansible/devel/dev_guide/index.html)\n- [Ansible collections requirements](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html)\n- [Ansible community Code of Conduct](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html)\n- [The Bullhorn (the Ansible contributor newsletter)](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn)\n- [Important announcements for maintainers](https://github.com/ansible-collections/news-for-maintainers)\n\n## Licensing\n\n\u003c!-- Include the appropriate license information here and a pointer to the full licensing details. If the collection contains modules migrated from the ansible/ansible repo, you must use the same license that existed in the ansible/ansible repo. See the GNU license example below. --\u003e\n\nGNU General Public License v3.0 or later.\n\nSee [LICENSE](https://www.gnu.org/licenses/gpl-3.0.txt) to see the full text.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fansible-collections%2Fcommunity.beszel","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fansible-collections%2Fcommunity.beszel","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fansible-collections%2Fcommunity.beszel/lists"}