You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on Coolify issue #2731 and its community-discovered solutions, the documentation should be updated to explain how to properly configure private Git submodules when deploying applications.
Problem
Users encounter authentication failures when trying to clone private Git submodules, with errors like:
fatal: could not read Username for 'https://github.com': No such device or address
fatal: clone of 'https://github.com/???/submodule.git' into submodule path failed
Solutions to Document
Prerequisites
GitHub App Permissions:
The GitHub App must have access permissions to both the main repository AND all submodule repositories
Solution 1: Use Relative Paths in .gitmodules (Recommended)
The most reliable solution is to use relative paths instead of absolute URLs in the .gitmodules file:
Description
Based on Coolify issue #2731 and its community-discovered solutions, the documentation should be updated to explain how to properly configure private Git submodules when deploying applications.
Problem
Users encounter authentication failures when trying to clone private Git submodules, with errors like:
Solutions to Document
Prerequisites
GitHub App Permissions:
Solution 1: Use Relative Paths in .gitmodules (Recommended)
The most reliable solution is to use relative paths instead of absolute URLs in the
.gitmodulesfile:Before:
After:
Important Notes:
Solution 2: Alternative Workaround
Some users report success by:
Solution 3: SSH Key Configuration
For cases where relative paths don't work:
Suggested Documentation Location
This information should be added to:
Additional Context
References