Self-deploying DeepLX is mainly suitable for the following scenarios:
- Business users who need higher privacy protection
- Developers who expect full control over the stability of their service
- Advanced users requiring customized features
Deployment Steps:
- environmental preparation: Sign up for a Cloudflare account, install Node.js 18+ and Wrangler CLI
- Get Code::
git clone https://github.com/xixu-me/DeepLX.git - Configuration items: Modification
wrangler.jsoncThe account_id and application name in the - Creating a KV store: Implementation
npx wrangler kv:namespace createCreating CACHE_KV and RATE_LIMIT_KV - Deploying applications: Run
npx wrangler deployCompletion of release
After a successful deployment, you'll be given the file shaped likehttps://your-app-name.your-cloudflare-account.workers.devThe KV namespace should be created in the Cloudflare console first. Note that the KV namespace needs to be created in the Cloudflare console first, and its ID needs to be populated in the corresponding location in the configuration file.
This answer comes from the articleDeepLX: free DeepL and Google Translate API servicesThe
May not be reproduced without permission:AI productivity tools " Why should I choose to deploy DeepLX on my own and how does it work?
English 
简体中文 
日本語 
Deutsch 
Português do Brasil