Если вы видите "0 workflow runs":
-
Проверьте файлы:
ls -la .github/workflows/
Должны быть:
deploy.ymlиci.yml✅ -
Подключите GitHub репозиторий:
git remote add origin https://github.com/YOUR_USERNAME/Taxered.git git push -u origin main
-
Настройте GitHub Secrets (Settings → Secrets):
GCP_PROJECT_ID- ваш GCP project IDGCP_SA_KEY- JSON ключ service account
📖 Полная инструкция: QUICKSTART_GITHUB_ACTIONS.md
Taxered is an open-source platform for filing tax declarations across multiple countries. The system supports country-specific tax forms with multi-language interfaces.
- 📱 Progressive Web App (PWA) - Install on any device, works offline
- 🌐 Multi-country support - Tax forms for 10+ countries
- 🗣️ Multi-language - Interface in 7+ languages
- 🔒 Privacy-first - All data stays in your browser
- 📊 Tax calculator - Built-in calculations
- 📄 PDF export - Download filled forms
- 🌙 Dark mode - Theme support
- 🇺🇦 Ukraine - F0100214, F0121214 (Fully Implemented)
- 🇵🇱 Poland - PIT-37, PIT-38, PIT-39
- 🇫🇷 France - 2042, 2042-C, 2044
- 🇩🇪 Germany - EST 1A, Anlage N, Anlage KAP
- 🇵🇹 Portugal - IRS Modelo 3, Anexo A, Anexo E
- 🇪🇸 Spain - Modelo 100, D-100, 720
- 🇸🇪 Sweden - INK1, K4, K10
- 🇬🇧 UK - SA100, SA108, SA109
- 🇺🇸 USA - Form 1040, Schedule D, Form 8949, Schedule C
- 🇨🇦 Canada - T1 General, Schedule 3, T5008
- 🇺🇦 Українська
- 🇬🇧 English
- 🇫🇷 Français
- 🇵🇱 Polski
- 🇪🇸 Español
- 🇵🇹 Português
- 🇩🇪 Deutsch
The application uses locale-based routing: /{language}-{country}
Examples:
/en-us- English interface, US tax forms/uk-ua- Ukrainian interface, Ukraine tax forms/pl-pl- Polish interface, Poland tax forms/fr-fr- French interface, France tax forms
- PWA.md - ⭐ Progressive Web App implementation
- LOCALE_ROUTING.md - Locale-based routing implementation details
- TAX_FORMS.md - Complete tax forms reference for all countries
- DEPLOYMENT.md - Deployment and infrastructure guide
- SETUP.md - Development setup instructions
- GITHUB_ACTIONS_STATUS.md - ⭐ Current setup status and quick start
- QUICKSTART_GITHUB_ACTIONS.md - 5-minute setup guide
- GITHUB_ACTIONS_SETUP.md - Detailed configuration guide
Push to GitHub and let GitHub Actions handle everything automatically.
Requirements:
- GitHub repository
- GCP project with billing enabled
- GitHub secrets configured (see DEPLOYMENT.md)
Steps:
- Follow setup in
DEPLOYMENT.md - Push to
mainbranch - GitHub Actions will deploy automatically
Test the Docker container locally before deploying.
Quick commands:
# Full build and run
./scripts/deploy-local.sh run
# Or use the interactive menu
./scripts/deploy-local.sh
# Stop container
./scripts/deploy-local.sh stop
# View logs
./scripts/deploy-local.sh logsDeploy directly to Google Cloud Run.
# One-time setup
gcloud auth login
gcloud config set project YOUR_PROJECT_ID
# Deploy
gcloud run deploy tax-declaration-app \
--source . \
--region us-central1 \
--allow-unauthenticated.github/workflows/deploy.yml- GitHub Actions CI/CD pipelineterraform/- Infrastructure as Code for GCPDockerfile- Container configurationDEPLOYMENT.md- Detailed setup guidescripts/deploy-local.sh- Local testing helper
Set these in your GitHub repository:
GCP_PROJECT_ID- Your Google Cloud project IDGCP_SA_KEY- Service account JSON key
Edit terraform/terraform.tfvars:
project_id = "your-gcp-project-id"
region = "us-central1"# Install dependencies
pnpm install
# Run dev server
pnpm dev
# Build for production
pnpm build
# Run production build
pnpm startFor detailed instructions, see DEPLOYMENT.md
With default settings (min_instances=0):
- Low traffic: $0-5/month
- Moderate traffic: $10-30/month
- High traffic: Scale as needed
You only pay for actual usage with Cloud Run.
If you see errors like:
WARN Ignoring not compatible lockfile
ERR_PNPM_NO_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is absent
Solution: The lockfile version must match the pnpm version in GitHub Actions.
- This project uses pnpm 9.x (lockfileVersion: '9.0')
- Check
.github/workflows/*.ymlfiles haveversion: 9in the pnpm setup - The
packageManagerfield inpackage.jsonshould specify the correct pnpm version
If you see:
ERROR: failed to build: failed to solve: no build stage in current context
Solution: The Dockerfile structure must follow proper multi-stage build order:
- Base stage with Node.js
- Dependencies stage (install packages)
- Builder stage (build application)
- Runner stage (production image)
Ensure your Next.js config has output: 'standalone' for Docker builds.
- Docker build fails: Ensure all dependencies are in package.json
- GCP authentication fails: Verify
GCP_SA_KEYsecret is correctly configured - Terraform errors: Check that your service account has necessary permissions
- Check DEPLOYMENT.md for detailed setup
- Review GitHub Actions logs for CI/CD issues
- Check Cloud Run logs in GCP Console
- Run
./scripts/deploy-local.shto test locally