Windows deployment powershell and renamed LLM_PROVIDER and runtime#2050
Windows deployment powershell and renamed LLM_PROVIDER and runtime#2050dartpain merged 3 commits intoarc53:mainfrom
Conversation
|
@poncema4 is attempting to deploy a commit to the Arc53 Team on Vercel. A member of the Team first needs to authorize it. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2050 +/- ##
==========================================
+ Coverage 34.67% 35.46% +0.78%
==========================================
Files 131 135 +4
Lines 8703 9258 +555
==========================================
+ Hits 3018 3283 +265
- Misses 5685 5975 +290 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dartpain
left a comment
There was a problem hiding this comment.
Thank you, all looks good except for this one spot
|
i think you accidentally did the opposite, remove changes on docker compose file, keep the ps1 changes |
|
perfect |
|
There is something weird with this PR, maybe try recreating new one. |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Windows shell script was not working so it needed redefining some names and making sure that all options stayed functional, so renaming the script to work when creating docker images for example it will now generate them properly rather than using localhost in docker-compose-hub.yaml
Why was this change needed? (You can also link to an open issue here)
Huge fix for people using windows and needing to run the powershell command so they are now able to run the application locally and be able to make changes and prs and do more testing :)
Other information:
Fixed issue: #2049 (P.S anymore bugs or issues with Windows Powershell start feel free to let me know to fix and make another PR)