enter-services

Name: enter-services
Author: pollinations

github.com/pollinationsCloud & DevOps5.3k68 installsUpdated today

About enter-services

A repository skill for working with the Pollinations enter and generation services. It documents their environments, staging tests, deployment procedures, and token-management safeguards for engineers.

Key features

01Document production and staging architecture
02Guide staging deployment and testing
03Explain Worker secrets and token rotation
04Describe production deployment safeguards

Use cases

01Testing service changes in staging
02Deploying the staging Worker
03Reviewing environment configuration and secrets

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pollinations/pollinations --skill enter-services

After installing, type/enter-servicesin Claude Code to confirm it loaded.

Bundled files.gitignoretoken-rotation.md

Details

From the project README

Requirements

Before using this skill, ensure you have:

sops: brew install sops (for decrypting secrets)
Wrangler: npm install -g wrangler
Node.js: brew install node

Must run from the pollinations repo root.

Architecture Overview

Environment	Gateway (Cloudflare Worker)	Generation
Production	`enter.pollinations.ai`	`gen.pollinations.ai` Worker
Staging	`staging.enter.pollinations.ai`	`staging.gen.pollinations.ai` Worker

The former enter-services / enter-services-staging EC2 boxes (text-pollinations.service, image-pollinations.service) are decommissioned; text and image generation run inside the gen.pollinations.ai Worker. The Discord bots that lived on enter-services now run on the monitoring-agents EC2 box — see apps/discord-bot-family/README.md and operations/infrastructure/gpu/GPU_INSTANCES.md.

Deploy Cloudflare Worker (enter.pollinations.ai)

Production deploys only through GitHub Actions (Deploy / Cloudflare production, dispatched from the production branch) — never wrangler deploy --env production from a local machine. See AGENTS.md "Cloudflare Production Deployment Safety".

Staging deploys through the Deploy / Cloudflare staging workflow (workflow_dispatch: pick the branch and the service). It runs migrate:staging first, then deploy:staging. Tick push_secrets to also push secrets/staging.vars.json to the Workers; a new or changed value needs Secret Mutation Safety approval (AGENTS.md) before it is merged. The same npm scripts also work locally per service:

cd enter.pollinations.ai
npm run deploy:staging   # staging only

Check what a Worker has with wrangler secret list --env staging. Details: token-rotation.md.

Testing on Staging

Test token: ENTER_API_TOKEN_STAGING in enter.pollinations.ai/.testingtokens. If auth fails, run npm run check-tokens in enter.pollinations.ai before blaming the deploy; tokens expire without the file changing.
Agents are called by owner/name model id on staging, same as production.
Cheap read-only checks: wrangler d1 migrations list DB --remote --env staging, wrangler secret list --env staging, and the dispatch namespace list.

Wrangler Configuration

The wrangler.toml contains environment configs:

Environment	Route	Service URLs
`production`	`enter.pollinations.ai`	`gen.pollinations.ai`
`staging`	`staging.enter.pollinations.ai`	`staging.gen.pollinations.ai`
`local`	`localhost:3000`	Local dev

Token Rotation

Internal trust-boundary tokens (PLN_ENTER_TOKEN, PLN_GPU_TOKEN, Tinybird tokens, SOPS recipients): see token-rotation.md for the inventory, rotation mechanisms, deploy path, and rollback.

OAuth Client Notes

Dated notes from building third-party OAuth clients against enter. Check current source before relying on them.

Open WebUI 0.11.x (2026-09): refreshes its token only within 5 minutes of expires_at, never in response to a 401 from a model call. A failed refresh deletes its oauth_session row but keeps the user logged in, so a failed refresh and a revoked API key look the same to the user (401 on the next model call). For self-healing: issue a short expires_in so the refresh fires, and return 200 from the refresh endpoint for every live account.
apikey table: in shared/db/better-auth.ts the owner field is referenceId, not userId. row.userId compiles in loosely typed code and fails at runtime with a misleading "Unauthorized or invalid session" from createApiKey. Run tsc on new files touching this table before testing live.

Notes

Production deploys on push to production branch
Staging deploys via the Deploy / Cloudflare staging workflow (manual dispatch), or per service with npm run deploy:staging
Always test on staging before merging to production
enter.pollinations.ai handles auth/billing; generation requests are served by the gen.pollinations.ai Worker

Comments

Markdown supported

Details

Author: pollinations
Repository: pollinations/pollinations
Category: Cloud & DevOps
Installs: 68
GitHub stars: 5,253

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.