feat: add a install script #184
Conversation
|
Warning Rate limit exceeded@karlprieb has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 7 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughWalkthroughThe Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Installer
participant Docker
participant GitHub
User->>Installer: Start installation
Installer->>User: Display welcome message
Installer->>User: Check OS compatibility
Installer->>Docker: Check for Docker and Docker Compose
Docker-->>Installer: Respond with status
Installer->>GitHub: Fetch latest release
GitHub-->>Installer: Return release tag
Installer->>User: Select services to enable
Installer->>User: Configure settings (START_HEIGHT, STOP_HEIGHT)
Installer->>Docker: Start selected services
Docker-->>User: Services up and running
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| # Final Step: Start the Node | ||
| echo "" | ||
| print_message "Starting your AR.IO node services with Docker Compose... ⏳" | ||
| echo "" | ||
| docker compose up -d | ||
| echo "" | ||
|
|
||
| if [ $? -eq 0 ]; then | ||
| print_success "Your AR.IO node services are now running in the background! 🎉" | ||
| else | ||
| print_error "There was an issue starting your AR.IO node services. Please check the output above for details." | ||
| exit 1 | ||
| fi |
There was a problem hiding this comment.
Fix the use of $? to ensure it refers to the intended command.
The current use of $? may not refer to the intended command due to intervening commands. Assign the result of docker compose up -d to a variable to avoid this issue.
- docker compose up -d
- if [ $? -eq 0 ]; then
+ docker compose up -d
+ DOCKER_UP_STATUS=$?
+ if [ $DOCKER_UP_STATUS -eq 0 ]; thenCommittable 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.
| # Final Step: Start the Node | |
| echo "" | |
| print_message "Starting your AR.IO node services with Docker Compose... ⏳" | |
| echo "" | |
| docker compose up -d | |
| echo "" | |
| if [ $? -eq 0 ]; then | |
| print_success "Your AR.IO node services are now running in the background! 🎉" | |
| else | |
| print_error "There was an issue starting your AR.IO node services. Please check the output above for details." | |
| exit 1 | |
| fi | |
| # Final Step: Start the Node | |
| echo "" | |
| print_message "Starting your AR.IO node services with Docker Compose... ⏳" | |
| echo "" | |
| docker compose up -d | |
| DOCKER_UP_STATUS=$? | |
| echo "" | |
| if [ $DOCKER_UP_STATUS -eq 0 ]; then | |
| print_success "Your AR.IO node services are now running in the background! 🎉" | |
| else | |
| print_error "There was an issue starting your AR.IO node services. Please check the output above for details." | |
| exit 1 | |
| fi |
Tools
Shellcheck
[warning] 280-280: This $? refers to echo/printf, not a previous command. Assign to variable to avoid it being overwritten.
(SC2320)
karlprieb
force-pushed
the
install-script
branch
2 times, most recently
from
51c0dab
to
2cc0a69
Compare
karlprieb
force-pushed
the
install-script
branch
from
2cc0a69
to
5fb476b
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #184 +/- ##
========================================
Coverage 68.05% 68.05%
========================================
Files 31 31
Lines 7419 7419
Branches 408 408
========================================
Hits 5049 5049
Misses 2369 2369
Partials 1 1 ☔ View full report in Codecov by Sentry. |
Automated AR.IO Node Installation Script for *nix Systems
This script was designed to simplify the process of configuring and launching an AR.IO node, making it accessible to both seasoned developers and those new to decentralized networks.
Why This Script Was Created
Setting up an AR.IO node manually involves several steps, including configuring environment variables, choosing which services to run, and ensuring all dependencies are properly installed. For newcomers or even experienced users, this can be a daunting and error-prone process.
To address these challenges, the AR.IO Node Setup Script was created with the following goals in mind:
How the Script Works
By automating the setup process and providing guidance, the AR.IO Node Setup Script empowers users to participate in the decentralized ar.io network with confidence, contributing to a more robust and resilient network.