At community.beszel, our mission is to make automation against Beszel simple. We aim to provide Ansible content that you can use to automate the configuration of Beszel Hub and Agents.

We welcome members from all skill levels to participate actively in our open, inclusive, and vibrant community. Whether you are an expert or just beginning your journey with Ansible and community.beszel, you are encouraged to contribute, share insights, and collaborate with fellow enthusiasts!

We follow the Ansible Code of Conduct in all our interactions within this project.

If you encounter abusive behavior, please refer to the policy violations section of the Code for information on how to raise a complaint.

• Join the Ansible forum:
  • Get Help: get help or help others. Please add appropriate tags if you start new discussions, for example the beszel tag.
  • Posts tagged with 'beszel': subscribe to participate in collection/technology-related conversations.
  • The community-beszel collection group on the Ansible forum: by joining the team you will automatically get subscribed to the posts tagged with beszel.
  • Social Spaces: gather and interact with fellow enthusiasts.
  • News & Announcements: track project-wide announcements including social events. The Bullhorn newsletter, which is used to announce releases and important changes, can also be found here.

For more information about communication, see the Ansible communication guide.

The 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 file for steps on how to get started contributing to community.beszel.

We are actively accepting new contributors and all types of contributions are very welcome.

Don't know how to start? Refer to the Ansible community guide!

We also use the following guidelines:

• Collection review checklist
• Quick-start development guide
• Ansible development guide
• Ansible collection development guide

The current maintainers are listed in the MAINTAINERS file. If you have questions or need help, feel free to mention them in the proposals.

To learn how to maintain/become a maintainer of this collection, refer to the Maintainer guidelines.

It is necessary for maintainers of this collection to be subscribed to:

• The collection itself (the Watch button -> All Activity in the upper right corner of the repository's homepage).
• The news-for-maintainers repository.

They also should be subscribed to Ansible's The Bullhorn newsletter.

The process of decision making in this collection is based on discussing and finding consensus among participants.

Every voice is important. If you have something on your mind, create an issue or dedicated discussion and let's discuss it!

Ansible Core 2.17, 2.18 and 2.19.

None.

Before using this collection, you need to install it with the Ansible Galaxy command-line tool:

ansible-galaxy collection install community.beszel

You can also include it in a requirements.yml file and install it with ansible-galaxy collection install -r requirements.yml, using the format:

---
collections:
  - name: community.beszel

Note 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:

ansible-galaxy collection install community.beszel --upgrade

You 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:

ansible-galaxy collection install community.beszel:==0.1.0

See using Ansible collections for more details.

See the changelog.

• Ansible user guide
• Ansible developer guide
• Ansible collections requirements
• Ansible community Code of Conduct
• The Bullhorn (the Ansible contributor newsletter)
• Important announcements for maintainers

GNU General Public License v3.0 or later.

See LICENSE to see the full text.