Add deployment badge for Hostinger #2928
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR adds a new one-click deployment badge for Hostinger to the project README, enabling easy VPS deployment alongside existing providers. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Summary of ChangesHello @Minijus-Sa, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the project's deployment documentation by integrating a new option for Hostinger. By adding a dedicated badge and link to the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
WalkthroughA new Hostinger deployment option section is added to the README documentation under the Docker deployment section, including a header, image badge link, and appropriate spacing. No existing deployment configurations are modified. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a deployment badge for Hostinger to the README file. However, the deployment link uses a placeholder value for the compose_url parameter, which means the deployment button will not work as intended. I have provided a suggestion to fix this by pointing it to the compose.yaml file in the repository.
|
|
||
| #### Hostinger | ||
|
|
||
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url) |
There was a problem hiding this comment.
The compose_url parameter in the Hostinger deployment link has a placeholder value docker-compose-url. This will cause the deployment to fail. It should be replaced with the URL-encoded path to the compose.yaml file from this repository.
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url) | |
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=https%3A%2F%2Fraw.githubusercontent.com%2Faltair-graphql%2Faltair%2Fmaster%2Fcompose.yaml) |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/README.md
📄 CodeRabbit inference engine (.github/instructions/documentation.instructions.md)
**/README.md: Every package should have a clear README.md file
README.md should include purpose, installation, usage, and API documentation
**/README.md: Provide clear usage instructions in README files
Document configuration options in README files
Include troubleshooting guides in README files
Show example outputs in README files
Files:
README.md
**/*.{md,mdx}
📄 CodeRabbit inference engine (.github/instructions/documentation.instructions.md)
**/*.{md,mdx}: Provide working code examples in documentation
Organize documentation by feature and user journey
Include getting started guides and tutorials
Provide troubleshooting and FAQ sections
Use clear, concise language
Follow consistent terminology throughout documentation
Write for the target audience (developers, end users)
Use active voice and present tense
Provide complete, working code examples
Test all code examples to ensure they work
Use realistic, relevant examples
Include both basic and advanced usage patterns
Use clear headings and subheadings
Organize content logically from basic to advanced
Use bullet points and numbered lists for clarity
Include a table of contents for long documents
Document all public functions and classes with parameter types, descriptions, return values, exceptions, and usage examples
Document all public interfaces and types with purpose, usage context, examples, and constraints
Explain features from the user's perspective
Include step-by-step instructions with screenshots in user guides
Cover common use cases and workflows
Provide troubleshooting tips in feature docs
Create migration guides for breaking changes with before/after examples and reasoning; include automated tools when possible
Document the development environment setup, prerequisites, and troubleshooting
Keep development setup instructions up to date
Document coding standards, architecture decisions, and examples of good/bad practices; reference automated tools
Release notes should highlight major features, include upgrade instructions, mention breaking changes, and link to detailed docs
Update examples to match current API
Remove outdated information from docs
Fix broken links and references
Use inclusive, accessible language; avoid jargon when possible; define technical terms; consider non-native English speakers
Use proper heading hierarchy for visual accessibility
Include alt text for images and screenshots
Ensure sufficient color contrast in embedded vi...
Files:
README.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Sourcery review
| #### Hostinger | ||
|
|
||
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url) |
There was a problem hiding this comment.
🧩 Analysis chain
Verify Hostinger deployment link is complete and functional.
The Hostinger deployment URL contains a placeholder parameter ?compose_url=docker-compose-url that appears incomplete. Compare this with the DigitalOcean example (line 101-103), which includes an actual repository reference in its deployment URL.
Ensure the Hostinger URL either:
- Includes the correct docker-compose file reference, or
- Contains the appropriate repository parameter like the other providers
Testing the link to verify it opens a valid Hostinger deployment flow would help confirm it's correctly configured.
If the URL needs to reference the docker-compose file, apply a fix like:
-[](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url)
+[](https://www.hostinger.com/vps/docker-hosting?compose_url=https://raw.githubusercontent.com/altair-graphql/altair/master/docker-compose.yml)Or if Hostinger uses a different parameter pattern, adjust accordingly based on their deployment documentation.
---
🏁 Script executed:
```shell
#!/bin/bash
# Extract README.md lines 90-115 to see deployment section context
if [ -f "README.md" ]; then
sed -n '90,115p' README.md
else
echo "README.md not found"
fi
Length of output: 1305
🏁 Script executed:
#!/bin/bash
# Find docker-compose files in repository
fd -e yml -e yaml | grep -i docker-composeLength of output: 81
🏁 Script executed:
#!/bin/bash
# Search for all deployment provider links in README.md
rg -n "digitalocean|vercel|render|hostinger" -i README.mdLength of output: 1268
---
🌐 Web query:
```web
Hostinger Docker deployment compose_url parameter documentation
💡 Result:
Hostinger documents the compose_url query parameter in its "Deploy on Hostinger" and Docker Manager docs: it’s a URL parameter you add to the VPS Docker-hosting URL that points to a docker-compose.yml (raw GitHub/GitLab or direct file URL). Example usage and referral-code option are shown in the docs:
- Deploy on Hostinger button (shows ?compose_url=your-docker-compose-url and example). [1]
- Docker Manager / Compose from URL (explains the Compose-from-URL flow and supported sources). [2]
References:
[1] Hostinger — Deploy on Hostinger button.
[2] Hostinger — How to deploy your first container with Hostinger Docker manager.
Fix Hostinger deployment URL with correct docker-compose.yml path.
The Hostinger deployment URL contains placeholder text ?compose_url=docker-compose-url that must reference the actual docker-compose.yml file. The repository has this file at packages/altair-api/docker-compose.yml, so the URL should be updated to:
-[](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url)
+[](https://www.hostinger.com/vps/docker-hosting?compose_url=https://raw.githubusercontent.com/altair-graphql/altair/master/packages/altair-api/docker-compose.yml)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #### Hostinger | |
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=docker-compose-url) | |
| #### Hostinger | |
| [](https://www.hostinger.com/vps/docker-hosting?compose_url=https://raw.githubusercontent.com/altair-graphql/altair/master/packages/altair-api/docker-compose.yml) |
🤖 Prompt for AI Agents
In README.md around lines 97 to 99, the Hostinger deploy link uses the
placeholder query ?compose_url=docker-compose-url; replace that placeholder with
the URL-encoded raw URL to the repository's
packages/altair-api/docker-compose.yml (i.e. the
raw.githubusercontent.com/<owner>/<repo>/<branch>/packages/altair-api/docker-compose.yml
path encoded into the compose_url query param) so Hostinger points to the actual
docker-compose.yml in this repo.
1 participant
Fixes
Checks
yarn test-buildChanges proposed in this pull request:
Summary by Sourcery
Documentation:
Summary by CodeRabbit