Support
FAQ
Frequently asked questions and troubleshooting tips
General
- This playbook primarily uses
aptfor installing packages on Debian-based systems. - It also utilizes
brew(Homebrew) for installing additional packages not available in the default repositories.
- If the installation fails on a
homebrewtask, it is most likely due to a network issue. - Check your internet connection and try running the playbook again.
Griffin downloads many packages from GitHub releases. The rate limit for unauthenticated requests is 60 per hour.
Solutions:
- Use a GitHub token: Generate a personal access token and use
-e github_token=YOUR_TOKEN - Wait and retry: Rate limits reset every hour
- Install fewer packages: Use specific feature flags instead of
-e all=true
Troubleshooting
Ensure you are running the Ansible playbook with the
-K flag. It will ask you for root user password which is necessary for executing tasks that require elevated privileges, such as modifying system settings or installing packages..yaml files) to add, remove, or modify the list of installed software to suit your specific needs.If you're facing an issue you can't troubleshoot, you can:
- Create an issue on the project's GitHub repository.
Yes! Griffin fully supports WSL. The playbook automatically detects WSL environments and adjusts accordingly.
WSL-specific behavior:
- Visual Studio Code: Skipped on WSL (use Windows version with Remote-WSL extension)
- GUI applications: Install normally, but require X server on Windows to display
- Systemd services: May have limited functionality depending on WSL version
Recommendation:
- Use WSL 2 for better compatibility
- Install Windows Terminal for improved terminal experience
- Use VSCode with Remote-WSL extension for seamless development
Contributing
How can I contribute to Griffin?
We welcome contributions from the community! You can contribute by:
- Reporting bugs or suggesting enhancements.
- Submitting pull requests with code improvements or new features
- Helping with documentation or translations
Please refer to the Contributing Guidelines for detailed information on how to get involved
Other Questions
If you have any other questions not addressed here, feel free to reach out to the community or open an issue on the project's GitHub repository.