Platforms

Platforms 25–48 of 57

• Platform

  Cloudflare for a small business: separate the DNS record, the proxy, the encryption mode and the cache

  Cloudflare faults are usually in one of four layers. Learn what proxied and DNS-only mean, why mail records stay DNS-only, and which fixed-price jobs fit which layer.

• Platform

  cPanel-style hosting: what lives in the account, where mail routing is decided and what a backup restores

  On cPanel hosting a website, its database, its mail and its DNS zone sit in one account. Learn how mail routing is detected, what the backup tools can restore, and where our jobs fit.

• Platform

  Microsoft 365 email for a small business: the DNS records, the switch-over and the forwarding setting

  Exchange Online needs a short list of DNS records, one SPF record and a careful MX switch. Learn what Microsoft documents, how forwarding is controlled and where our email jobs fit.

• Platform

  Google Workspace email for a small business: the MX record, labels, forwarding and sender rules

  Google Workspace uses one MX record, treats labels as folders over IMAP, separates forwarding from redirecting and sets sender rules for mail to Gmail. Learn what Google documents and where our jobs fit.

• Platform

  Playwright: test the flows that matter in a real browser, and only what you control

  What a browser smoke suite is for, which failure patterns come from timing, shared data and the CI environment, and which guide or paid outcome fits each.

• Platform

  Sentry: see production errors with readable traces, safe payloads and one alert you can trust

  What an error tracker needs before it is useful: readable stack traces, release and environment, filtered sensitive data and a quiet alert, with the guide that covers each and the paid setup job.

• Platform

  pytest: fixtures, patching and markers, and where test suites quietly go wrong

  How pytest's fixture scopes, monkeypatch, temporary directories and skip or xfail markers shape test reliability, with the guide for each pattern and the bounded jobs that fit.

• Platform

  Rails upgrades: keep the Ruby, framework and JavaScript decisions apart

  A Rails upgrade is three separate moving parts. Name which one is blocking you, and what each vendor still supports, before choosing a job.

• Platform

  Node.js upgrades: the runtime line, the framework major and native modules are different jobs

  Choose the Node.js line from the project's own schedule, then handle a web-framework major version and compiled modules as separate, testable steps.

• Platform

  Python upgrades: choose the interpreter, then deal with removed modules and compiled packages

  Use the Python developer guide's support dates, then separate standard-library removals, dependency wheels and framework majors so each can be tested.

• Platform

  Leaving Heroku: list everything the app depends on before choosing the new host

  A Heroku app is its code plus a Procfile, a release command, config variables, add-ons, scheduled jobs and a database. List them before picking where to go.

• Platform

  Next.js app problems: which fault to check first, and which bounded job fits

  For a product owner with a working Next.js app that fails in one specific way (sign-in, webhooks, speed, rendering or errors), a map of the usual faults with the checks that separate them.

• Platform

  React app problems: blank screens, mismatched text, forms and layout, and the job that fits each

  For a product owner with a React front end that misbehaves in a specific way, a map from symptom to cause and to a bounded, checkable repair.

• Platform

  Supabase app problems: empty results, permission errors and where each key belongs

  For a product owner whose app is built on Supabase and returns nothing, refuses a write or leaks data, a map of the access-rule faults and the bounded repair that fits.

• Platform

  Google Analytics 4 measurement problems: prove collection first, then read the reports

  Where GA4 data goes wrong between the site and the report, with the quick checks, the documented limits and the bounded repairs that fit each fault.

• Platform

  Google Tag Manager: containers, previews and versions for safe tracking changes

  How Tag Manager separates a container into workspaces, versions and preview, how the data layer feeds it, and which tracking repairs depend on each part.

• Platform

  Meta Pixel conversion events: check one test event before you trust the counts

  What the Meta Pixel needs for Purchase events, how to see a test event arrive, when deduplication applies and where the Conversions API is a different job.

• Platform

  MySQL performance and locking: read the plan, the slow log and the lock waits before changing anything

  For teams on MySQL 8.x: where to look for slow statements, how InnoDB handles schema changes and deadlocks, and which bounded jobs fit.

• Platform

  Redis as a cache: expiry, eviction and invalidation decide whether users see fresh data

  For teams using Redis in front of a database: how expiry is cleared by overwrites, what the memory limit does, why persistence is optional for a cache, and which bounded job fits.

• Platform

  SQLite in a growing app: loose types, optional foreign keys and one writer at a time

  What SQLite does differently from PostgreSQL or MySQL, how to check a SQLite database for integrity problems, and when an app has outgrown it.

• Platform

  SendGrid in your app: authenticated sending, then what the delivery events tell you

  Understand what SendGrid's domain authentication proves, what its event feed reports and which parts of a transactional email connection are yours to build and test.

• Platform

  Twilio SMS in your app: sending is one call, knowing what happened is the work

  Understand message statuses, out-of-order delivery callbacks, request signatures and sender registration before connecting an app to Twilio messaging.

• Platform

  Slack API in your app: posting alerts and receiving events are two different jobs

  Understand when to use an incoming webhook or a bot token, how Slack rate limits posts, and the signing, timing and retry rules for events it sends to your app.

• Platform

  Terraform: write the resources as code, review the plan, and keep state safe

  What a Terraform module job covers, what a monthly drift review does, and the acceptance evidence for each: a reviewed plan, a clean post-apply plan and a state you can protect.