pax_global_header00006660000000000000000000000064134540410210014504gustar00rootroot0000000000000052 comment=4f086521ad998520a1a14d72667790d29c87d818 argonaut-1.3/000077500000000000000000000000001345404102100131675ustar00rootroot00000000000000argonaut-1.3/.gitlab-ci.yml000066400000000000000000000116121345404102100156240ustar00rootroot00000000000000# Specify docker image image: debian:stretch # Define variable to disable SSL verification of GIT variables: GIT_SSL_NO_VERIFY: "true" stages: - test-perl - test-manpages - tarballs # Generate perlcritic rapport create_perlcritic_rapport: stage: test-perl only: - branches - tags before_script: - apt-get update -qq - apt-get install -y -qq libperl-critic-perl script: - perlcritic . # Perl lint create_perl_lint_rapport: stage: test-perl only: - branches - tags before_script: - apt-get update -qq - apt-get install -y -qq libapp-daemon-perl libconfig-inifiles-perl libdigest-sha-perl libfile-pid-perl libio-socket-ssl-perl - apt-get install -y -qq libjson-perl libjson-rpc-perl liblog-handler-perl libmodule-pluggable-perl libnet-ldap-perl libpath-class-perl libxml-sax-expatxs-perl - apt-get install -y -qq bind9utils libdns-zoneparse-perl - apt-get install -y -qq libquota-perl - apt-get install -y -qq libdatetime-perl libpoe-perl libpoe-component-pool-thread-perl libpoe-component-schedule-perl libpoe-component-server-jsonrpc-perl libpoe-component-server-simplehttp-perl libpoe-component-sslify-perl - apt-get install -y -qq libhttp-daemon-ssl-perl - apt-get install -y -qq fuse libfuse-perl - apt-get install -y -qq debmirror libwww-perl - apt-get install -y -qq libmail-sendmail-perl - apt-get install -y -qq libfile-slurp-perl libdigest-perl-md5-perl script: - find . -type f -name '*.pm' -print0 | xargs -0 -n1 perl -cw -I argonaut-ldap2zone -I argonaut-common # generate man pages to test validity test_manpages: stage: test-manpages only: - branches - tags before_script: - apt-get update -qq - apt-get install -y -qq perl man-db script: - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-client/bin/argonaut-client argonaut-client/man/argonaut-client.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-common/man/argonaut.conf.pod argonaut-common/man/argonaut.conf.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-mirror/bin/argonaut-debconf-crawler argonaut-fai-mirror/man/argonaut-debconf-crawler.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-mirror/bin/argonaut-repository argonaut-fai-mirror/man/argonaut-repository.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-monitor/bin/argonaut-fai-monitor argonaut-fai-monitor/man/argonaut-fai-monitor.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-nfsroot/bin/argonaut-ldap2fai argonaut-fai-nfsroot/man/argonaut-ldap2fai.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-server/bin/fai2ldif argonaut-fai-server/man/fai2ldif.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-server/bin/yumgroup2yumi argonaut-fai-server/man/yumgroup2yumi.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fuse/bin/argonaut-fuse argonaut-fuse/man/argonaut-fuse.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fusiondirectory/bin/argonaut-clean-audit argonaut-fusiondirectory/man/argonaut-clean-audit.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fusiondirectory/bin/argonaut-user-reminder argonaut-fusiondirectory/man/argonaut-user-reminder.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-ldap2zone/bin/argonaut-ldap2zone argonaut-ldap2zone/man/argonaut-ldap2zone.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-quota/bin/argonaut-quota argonaut-quota/man/argonaut-quota.1 - pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-server/bin/argonaut-server argonaut-server/man/argonaut-server.1 - lexgrog argonaut-client/man/argonaut-client.1 - lexgrog argonaut-common/man/argonaut.conf.1 - lexgrog argonaut-fai-mirror/man/argonaut-debconf-crawler.1 - lexgrog argonaut-fai-mirror/man/argonaut-repository.1 - lexgrog argonaut-fai-monitor/man/argonaut-fai-monitor.1 - lexgrog argonaut-fai-nfsroot/man/argonaut-ldap2fai.1 - lexgrog argonaut-fai-server/man/fai2ldif.1 - lexgrog argonaut-fai-server/man/yumgroup2yumi.1 - lexgrog argonaut-fuse/man/argonaut-fuse.1 - lexgrog argonaut-fusiondirectory/man/argonaut-clean-audit.1 - lexgrog argonaut-fusiondirectory/man/argonaut-user-reminder.1 - lexgrog argonaut-ldap2zone/man/argonaut-ldap2zone.1 - lexgrog argonaut-quota/man/argonaut-quota.1 - lexgrog argonaut-server/man/argonaut-server.1 build-tarballs: stage: tarballs script: - tar -cvzf argonaut.tar.gz * artifacts: paths: - argonaut.tar.gz expire_in: 1h build-release: stage: tarballs only: - tags script: - tar -cvzf argonaut-$(grep '%' Changelog.md | head -n1 | cut -d ' ' -f3 | tr -d '"').tar.gz * artifacts: paths: - argonaut-$(grep '%' Changelog.md | head -n1 | cut -d ' ' -f3 | tr -d '"').tar.gz argonaut-1.3/.gitlab/000077500000000000000000000000001345404102100145075ustar00rootroot00000000000000argonaut-1.3/.gitlab/.gitkeep000066400000000000000000000000001345404102100161260ustar00rootroot00000000000000argonaut-1.3/.gitlab/issue_templates/000077500000000000000000000000001345404102100177155ustar00rootroot00000000000000argonaut-1.3/.gitlab/issue_templates/.gitkeep000066400000000000000000000000001345404102100213340ustar00rootroot00000000000000argonaut-1.3/.gitlab/issue_templates/Backporting.md000066400000000000000000000012101345404102100224740ustar00rootroot00000000000000### Description ### Source Argonaut Version ### Destination Argonaut Version ### component with the new code ### Reason of Backporting code ### What defect does it correct ### Additional Information argonaut-1.3/.gitlab/issue_templates/Bugs.md000066400000000000000000000014041345404102100211360ustar00rootroot00000000000000### Description ### Distribution Name and Version ### Argonaut Version ### PERL version used ### Origin of perl packages ### Steps to Reproduce 1. [First Step] 2. [Second Step] 3. [and so on...] **Expected behavior:** **Actual behavior:** **Reproduces how often:** ### Additional Information argonaut-1.3/.gitlab/issue_templates/Contribution.md000066400000000000000000000015761345404102100227270ustar00rootroot00000000000000### Requirements * Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion. * All new code requires tests to ensure against regressions ## Descriptive title for this contribution ### Step by step description of this contribution 1. [First Step] 2. [Second Step] 3. [and so on...] ### Does this contribution need a new FusionDirectory plugin ### Benefits ### Possible Drawbacks ### Actual use cases argonaut-1.3/.gitlab/issue_templates/Enhancement.md000066400000000000000000000015311345404102100224640ustar00rootroot00000000000000### Requirements * Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion. * All new code requires tests to ensure against regressions ## Descriptive title for this enhancement ### Actual behavior ### Expected behavior ### Step by step description of new behaviour 1. [First Step] 2. [Second Step] 3. [and so on...] ### Benefits ### Possible Drawbacks ### Applicable Issues argonaut-1.3/.gitlab/merge_request_templates/000077500000000000000000000000001345404102100214345ustar00rootroot00000000000000argonaut-1.3/.gitlab/merge_request_templates/.gitkeep000066400000000000000000000000001345404102100230530ustar00rootroot00000000000000argonaut-1.3/.gitlab/merge_request_templates/Merge.md000066400000000000000000000013071345404102100230160ustar00rootroot00000000000000### Requirements * Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion. * All new code requires tests to ensure against regressions ## Title of the Pull Requests ### Description of the Change ### Benefits ### Possible Drawbacks ### Applicable Issues argonaut-1.3/Authors.md000066400000000000000000000013421345404102100151360ustar00rootroot00000000000000Argonaut AUTHORS ======================= This is the alphabetical list of all people that have contributed to the Argonaut project, beeing code, translations, documentation and additional help. * Benoit Mortier Butracking, QA * Antoine Gallavardin Quota original code * Bernigaud Côme All the new deployment stuff :) * Samuel Bosquin Help and test with the RPM code and FAI * Jonathan Swaelens QA, Testing, Systemd units * Sean Thatcher papertray3@gmail.com Corrected Argonaut systemd units * Thomas Niercke Code for the samba share argonaut module argonaut-1.3/CODE_OF_CONDUCT.md000066400000000000000000000062611345404102100157730ustar00rootroot00000000000000# Contributor Covenant Code of Conduct ## Our Pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. ## Our Standards Examples of behavior that contributes to creating a positive environment include: * Using welcoming and inclusive language * Being respectful of differing viewpoints and experiences * Gracefully accepting constructive criticism * Focusing on what is best for the community * Showing empathy towards other community members Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and unwelcome sexual attention or advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic address, without explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. ## Scope This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at . All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://www.contributor-covenant.org/version/1/4][version] [homepage]: https://www.contributor-covenant.org [version]: https://www.contributor-covenant.org/version/1/4/ argonaut-1.3/CONTRIBUTING.md000066400000000000000000000206361345404102100154270ustar00rootroot00000000000000# Contributing to FusionDirectory projects ## Table Of Contents 1. [Welcome](#Welcome) 2. [Code of Conduct](#code-of-conduct) 3. [I just have a question!](#i-just-have-a-question) 4. [How Can I Contribute?](#how-can-i-contribute) * [Finding Wonderful Bugs](#finding-wonderful-bugs) * [Any Feedback To Enhance Our Apps](#any-feedback-to-enhance-our-apps) * [Your Awesome And Mighty Codes Contributions](#your-awesome-and-mighty-codes-contributions) 5. [Coding with style](#coding-with-style) * [Git Commit Messages](#git-commit-messages) 6. [Licensing](#licensing) --- ## Welcome > «Here's a list of our guidelines, If you want to share a best practice, or think one of these guidelines should be removed, feel free to share it with us.» :tada: First off, thanks for taking the time to contribute! Now, sit comfortably at the fireplace, grab your glasses and immerse yourself in our documentation. ## Code Of Conduct All projects and everyone participating in it is governed by [FusionDirectory Code Of Conduct](./CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please read this before. ## I just have a question! > **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resource below. We have an various channel of communications * [#fusiondirectory, the irc channel of FusionDirectory on freenode](https://webchat.freenode.net/), channel #fusiondirectory * [FusionDirectory Users mailing list](https://lists.fusiondirectory.org/wws/info/users) * [FusionDirectory dev mailing list](https://lists.fusiondirectory.org/wws/info/developpers) ## How Can I Contribute? So, you've developed a new cool feature? Fixed an annoying bug? Found a mistake? We'd be happy to hear from you! :+1: ### Register for a FusionDirectory project account To create a FusionDirectory project Account you must go to * [FusionDirectory Sign UP](https://register.fusiondirectory.org) ### Put Argonaut in debug mode * Stop the service if it is running * Start in console with -v to get more log * Start with -X if you want it to be in foreground and send logging to console ### Finding Wonderful Bugs >This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports. When you are creating a bug report, please include as many details as possible. Fill out the **Bugs** template to create issues, the information it asks for helps us resolve issues faster. Explain the problem and include additional details to help maintainers reproduce the problem: * **Use a clear and descriptive title** for the issue to identify the problem. * **Describe the exact steps which reproduce the problem** in as many details as possible. * **Describe the behavior** you observed after following the steps and point out what exactly is the problem with that behavior. * **Explain which behavior** you expected to see instead and why. * **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and this tool or [this tool](https://github.com/GNOME/byzanz) on Linux. * **Include the Perl errors and trace** collected at the debug step above * **If the problem is linked to a specific LDAP entry** attach its LDAP dump. Fill in a report on : * [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues) ### Any Feedback To Enhance FusionDirectory >This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions. When you are creating a enhancement report, please include as many details as possible. Fill out the **Enhancement** template to create thoses issues, the information it asks for helps us resolve issues faster. * [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues) * **Use a clear and descriptive title** for the issue to identify the suggestion. * **Provide a step-by-step description of the suggested enhancement** in as many details as possible. * **Describe the current behavior** and **explain which behavior you expected to see instead** and why. * **Include screenshots and animated GIFs** which help you demonstrate the steps which the suggestion is related to. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. * **Explain why this enhancement would be useful** to most Argonaut users. ### Your awesome And Mighty Codes Contributions >This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions. When you are contributing a new fonctionnality or plugin, please include as many details as possible. Fill out the **Contribution** template to create thoses issues, the information it asks for helps us resolve issues faster. * [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues) * **Use a clear and descriptive title** for the issue to identify your contribution * **Provide a step-by-step description of the contribution** in as many details as possible. * **Include screenshots and animated GIFs** which help you demonstrate what this contribution is about. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. * **Explain why this contribution would be useful** to most Argonaut users. * **Run** [Perl critic](https://metacpan.org/pod/Perl::Critic) on your code. ## Coding with style ### Git Commit Messages >Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. Here are some rules of thumb : * Use the present tense ("Add feature" not "Added feature") * If you have a body, separate the subject from the body with a newline * Limit the subject line to 72 characters * Do not end the subject line with a period * Use imperative [mood](https://en.wikipedia.org/wiki/Imperative_mood#English) in the subject line * If the subject is not clear enough, use the body to explain what and why as opposed to how * Consider starting the commit message with an applicable emoji, when you feel it's an important commit : * :tada: When first / initial commit * :sparkles: When introducing new features * :ambulance: When fixing a bug * :handshake: When merging files * :tractor: When you changing file structure or refactoring * :books: When writing docs * :gem: When new Release * :lipstick: For cosmetics purposes #### Commit Message Format Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ``` ():