Meta tags:
description= Breaking changes and migration steps when upgrading to Rybbit v1.0;
author= Rybbit Team;
keywords= web analytics,privacy analytics,open source analytics,Google Analytics alternative,website tracking,self-hosted analytics;
Headings (most frequently used words):
migration, to, if, you, re, using, this, v1, api, path, changes, steps, need, help, the, built, in, caddy, server, custom, reverse, proxy, on, page, what, remove, why, change,
Text of the page (most frequently used words):
api (22), the (16), remove (12), proxy (12), configuration (12), this (10), #reverse (10), your (10), migration (9), rybbit (9), you (8), and (8), http (8), 3001 (8), using (7), update (7), custom (6), path (6), changes (6), settings (6), setup (6), localhost (6), need (5), with (5), location (5), steps (4), change (4), self (4), for (4), rewriting (4), any (4), proxy_pass (4), rewrite (4), rules (4), proxy_set_header (4), when (4), guides (4), built (3), caddy (3), server (3), account (3), backend (3), prefix (3), correct (3), these (3), upgrading (3), documentation (3), help (2), why (2), what (2), pangolin (2), hosted (2), that (2), script (2), making (2), eliminates (2), common (2), rybbit_backend (2), break (2), proxypassreverse (2), proxypass (2), type (2), apache (2), patterns (2), forwarded (2), host (2), trailing (2), slash (2), nginx (2), requests (2), guide (2), breaking (2), users (2), hosting (2), troubleshooting (2), feature (2), traffic (2), 689 (2), github (2), page, manage, personal, including, profile, security, keys, set, newt, encounter, issues, during, assistance, specific, feel, free, join, our, discord, community, support, checking, instance, accessible, functioning, correctly, verify, applicable, before, backup, current, simplifies, source, errors, now, handles, internally, more, straightforward, consistent, across, different, solutions, like, docker, compose, proto, scheme, proxy_add_x_forwarded_for, real, remote_addr, line, strips, rewrites, forwarding, examples, include, were, etc, endpoint, must, important, from, has, been, automatically, updated, will, work, without, part, action, required, simplified, having, expect, configurations, covers, open, copy, markdown, definitions, other, data, import, site, inviting, billing, teams, organization, managing, installation, quick, start, embeds, funnels, goals, bot, detection, filter, hiding, own, sdks, integration, tagging, identify, autocapture, track, events, tracking, usage, cloud, architecture, comparison, introduction, reference, search,
Text of the page (random words):
migration to v1 0 rybbit search k github rybbit io rybbit 12 4k 689 documentation api reference documentation guides setup and feature documentation github rybbit io rybbit 12 4k 689 introduction comparison architecture self hosted vs cloud usage tracking script troubleshooting track events autocapture identify users tagging integration guides proxy guide sdks hiding your own traffic filter traffic bot detection goals funnels embeds feature guides self hosting quick start managing your installation troubleshooting self hosting guides migration to v1 0 settings account settings organization settings teams billing inviting users site settings data import other definitions migration to v1 0 migration to v1 0 breaking changes and migration steps when upgrading to rybbit v1 0 copy markdown open this guide covers the breaking changes and migration steps when upgrading to rybbit v1 0 api path changes in v1 0 we ve simplified the reverse proxy configuration by having the backend expect requests with the api prefix this eliminates the need for custom path rewriting in reverse proxy configurations if you re using the built in caddy server no action required the built in caddy server configuration has been automatically updated and will work without any changes on your part if you re using a custom reverse proxy you need to remove any custom api path rewriting from your reverse proxy configuration important if you were using a custom reverse proxy nginx apache etc with path rewriting rules for the api endpoint you must remove these rules when upgrading to v1 0 what to remove remove any configuration that strips or rewrites the api prefix when forwarding requests to the backend common examples include nginx remove these patterns remove this type of configuration location api rewrite api 1 break remove this line proxy_pass http localhost 3001 change trailing slash update to correct v1 0 configuration location api proxy_pass http localhost 3001 no trailing slash no rewrite proxy_set_header host host proxy_set_header x real ip remote_addr proxy_set_header x forwarded for proxy_add_x_forwarded_for proxy_set_header x forwarded proto scheme apache remove these patterns remove this type of configuration proxypass api http localhost 3001 proxypassreverse api http localhost 3001 update to correct v1 0 configuration proxypass api http localhost 3001 api proxypassreverse api http localhost 3001 api docker compose with custom location rules remove rewrite rules like this location api rewrite api 1 break proxy_pass http rybbit_backend 3001 update to correct v1 0 configuration location api proxy_pass http rybbit_backend 3001 why this change this change simplifies the reverse proxy setup and eliminates a common source of configuration errors the backend now handles the api prefix internally making the setup more straightforward and consistent across different proxy solutions migration steps backup your current configuration before making any changes update your reverse proxy configuration to remove api path rewriting if applicable update to v1 0 using the update script update sh verify your setup by checking that your rybbit instance is accessible and functioning correctly need help if you encounter issues during migration or need assistance with your specific reverse proxy setup feel free to join our discord community for support pangolin setup set up rybbit with pangolin as a self hosted reverse proxy using newt account settings manage your personal account settings including profile security and api keys on this page api path changes if you re using the built in caddy server if you re using a custom reverse proxy what to remove why this change migration steps need help
|
