mirror of
https://github.com/justlovemaki/AIClient-2-API.git
synced 2026-04-26 01:45:56 +03:00
[GH-ISSUE #177] Running AIClient-2-API on cloud servers #137
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AIClient-2-API-justlovemaki#137
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Kartvya69 on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/justlovemaki/AIClient-2-API/issues/177
I have been using AIClient-2-API locally as a proxy service for models like Gemini, Claude, and others. The service works well in my local environment.
I would like to know if it is possible to deploy and run this service on cloud servers (for example AWS, Google Cloud, Azure, or other remote hosting platforms) so that it can be accessed remotely and used in a scalable way.
After reviewing the repository documentation and existing issues, I could not find clear instructions or examples related to cloud deployment.
Question:
Is there any recommended or supported method to run AIClient-2-API on cloud servers?
If yes, what deployment pattern should be used (such as Docker containers, virtual machines, or managed services), and are there any specific configuration considerations like environment variables, ports, persistence, or scaling?
If no, are there any plans to officially support cloud-based deployment in the future?
@justlovemaki commented on GitHub (Jan 8, 2026):
You can deploy using Docker cloud services, or you can run it directly on a cloud server using a Node.js environment.