lokalise-deploy-integration
Deploy Lokalise integrations to Vercel, Netlify, and Cloud Run platforms. Use when deploying apps with Lokalise translations to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy lokalise", "lokalise Vercel", "lokalise production deploy", "lokalise Netlify", "lokalise Cloud Run".
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2.0k
- Forks
- 234
01 前言 Front Matter
- name
- lokalise-deploy-integration
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Deploy Lokalise integrations to Vercel, Netlify, and Cloud Run platforms. Use when deploying apps with Lokalise translations to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy lokalise", "lokalise Vercel", "lokalise production deploy", "lokalise Netlify", "lokalise Cloud Run".
- allowed-tools
- Read, Write, Edit, Bash(vercel:*), Bash(netlify:*), Bash(gcloud:*)
03 SKILL.md 正文
Lokalise Deploy Integration
Overview
Deploy applications with Lokalise translations to popular platforms with proper secrets management.
Prerequisites
- Lokalise API token for production
- Platform CLI installed (vercel, netlify, or gcloud)
- Application code ready for deployment
- Translations synced and verified
Vercel Deployment
Environment Setup
# Add Lokalise secrets to Vercel
vercel env add LOKALISE_API_TOKEN production
vercel env add LOKALISE_PROJECT_ID production
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
vercel.json Configuration
{
"build": {
"env": {
"LOKALISE_API_TOKEN": "@lokalise_api_token",
"LOKALISE_PROJECT_ID": "@lokalise_project_id"
}
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
Pre-build Translation Sync
// package.json
{
"scripts": {
"prebuild": "npm run i18n:pull",
"build": "next build",
"i18n:pull": "lokalise2 file download --token $LOKALISE_API_TOKEN --project-id $LOKALISE_PROJECT_ID --format json --unzip-to ./public/locales"
}
}
Netlify Deployment
netlify.toml
[build]
command = "npm run build"
publish = "dist"
[build.environment]
NODE_VERSION = "20"
[[plugins]]
package = "./plugins/lokalise-sync"
[context.production.environment]
LOKALISE_ENV = "production"
Netlify Build Plugin
// plugins/lokalise-sync/index.js
module.exports = {
onPreBuild: async ({ utils }) => {
try {
const { execSync } = require("child_process");
console.log("Downloading translations from Lokalise...");
execSync(`
curl -sL https://github.com/lokalise/lokalise-cli-2-go/releases/latest/download/lokalise2_linux_x86_64.tar.gz | tar xz
./lokalise2 file download \
--token "$LOKALISE_API_TOKEN" \
--project-id "$LOKALISE_PROJECT_ID" \
--format json \
--unzip-to ./src/locales
`, { stdio: "inherit" });
console.log("Translations downloaded successfully!");
} catch (error) {
utils.build.failBuild("Failed to download translations", { error });
}
},
};
Netlify Environment Variables
# Using Netlify CLI
netlify env:set LOKALISE_API_TOKEN "your-token"
netlify env:set LOKALISE_PROJECT_ID "123456.abcdef"
# Deploy
netlify deploy --prod
Google Cloud Run
Dockerfile
FROM node:20-slim AS builder
WORKDIR /app
# Install Lokalise CLI
RUN apt-get update && apt-get install -y curl && \
curl -sL https://github.com/lokalise/lokalise-cli-2-go/releases/latest/download/lokalise2_linux_x86_64.tar.gz | tar xz && \
mv lokalise2 /usr/local/bin/
COPY package*.json ./
RUN npm ci
# Download translations at build time
ARG LOKALISE_API_TOKEN
ARG LOKALISE_PROJECT_ID
RUN lokalise2 file download \
--token "$LOKALISE_API_TOKEN" \
--project-id "$LOKALISE_PROJECT_ID" \
--format json \
--unzip-to ./src/locales
COPY . .
RUN npm run build
# Production image
FROM node:20-slim
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
CMD ["node", "dist/index.js"]
Cloud Run Deployment
#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="my-app"
REGION="us-central1"
# Build with Lokalise token as build arg
gcloud builds submit \
--tag gcr.io/$PROJECT_ID/$SERVICE_NAME \
--build-arg LOKALISE_API_TOKEN="$LOKALISE_API_TOKEN" \
--build-arg LOKALISE_PROJECT_ID="$LOKALISE_PROJECT_ID"
# Deploy to Cloud Run
gcloud run deploy $SERVICE_NAME \
--image gcr.io/$PROJECT_ID/$SERVICE_NAME \
--region $REGION \
--platform managed \
--allow-unauthenticated
OTA (Over-the-Air) Updates for Mobile
Setup OTA in Lokalise
// Initialize OTA SDK for React Native
import { LokaliseOta } from "@lokalise/react-native-ota";
const ota = new LokaliseOta({
projectId: process.env.LOKALISE_PROJECT_ID!,
token: process.env.LOKALISE_OTA_TOKEN!, // OTA-specific token
preloadLanguages: ["en", "es", "fr"],
});
// Check for updates on app start
async function initTranslations() {
try {
const updated = await ota.checkForUpdates();
if (updated) {
console.log("Translations updated!");
}
} catch (error) {
console.warn("OTA update failed, using bundled translations");
}
}
Health Check Endpoint
// api/health.ts
export async function GET() {
const health = {
status: "healthy",
timestamp: new Date().toISOString(),
services: {
translations: await checkTranslations(),
},
};
const statusCode = health.services.translations.ok ? 200 : 503;
return Response.json(health, { status: statusCode });
}
async function checkTranslations() {
try {
const locales = ["en", "es", "fr"];
for (const locale of locales) {
const path = `./public/locales/${locale}.json`;
if (!fs.existsSync(path)) {
return { ok: false, error: `Missing ${locale}.json` };
}
}
return { ok: true, locales };
} catch (error) {
return { ok: false, error: error.message };
}
}
Instructions
Step 1: Choose Deployment Platform
Select the platform that best fits your infrastructure needs.
Step 2: Configure Secrets
Store Lokalise API token securely using the platform's secrets management.
Step 3: Set Up Pre-build Sync
Configure translation download before build step.
Step 4: Deploy and Verify
Deploy application and verify translations are included.
Output
- Application deployed to production
- Lokalise secrets securely configured
- Translations bundled with deployment
- Health check endpoint functional
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Missing translations | Pre-build failed | Check build logs for Lokalise errors |
| Secret not found | Missing configuration | Add secret via platform CLI |
| Build timeout | Large translations | Cache translations or increase timeout |
| OTA fails | Network/token issue | Fall back to bundled translations |
Examples
Quick Deploy Script
#!/bin/bash
# Platform-agnostic deploy helper
set -e
# Ensure translations are fresh
npm run i18n:pull
# Build
npm run build
# Deploy based on platform
case "${DEPLOY_PLATFORM:-vercel}" in
vercel)
vercel --prod
;;
netlify)
netlify deploy --prod
;;
cloudrun)
./scripts/deploy-cloud-run.sh
;;
esac
CDN-Cached Translations
// Load translations from CDN with cache
const CACHE_TTL = 3600; // 1 hour
async function loadTranslations(locale: string) {
const cdnUrl = `https://cdn.example.com/locales/${locale}.json`;
const response = await fetch(cdnUrl, {
next: { revalidate: CACHE_TTL },
});
if (!response.ok) {
// Fall back to bundled translations
return import(`./locales/${locale}.json`);
}
return response.json();
}
Resources
Next Steps
For webhook handling, see lokalise-webhooks-events.
04 同仓库更多 Skills
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
neuropixels-analysis
Neuropixels neural recording analysis. Load SpikeGLX/OpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen/IBL curation, AI-assisted visual analysis, for Neuropixels 1.0/2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
slack-gif-creator
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."