chore(brand): rename the product to ReplyPier
The upstream project name is gone from code, assets, docs and build
output: brand strings, domains (replypier.site and its app/api/docs/help
subdomains), env prefixes, image and network names, the widget's public
JS API (window.ReplyPier, replypierId/BaseUrl/Config/Token), CSS tokens
(--rp-*), file and directory names, and the WordPress plugin package.
- widget loader is now webclient/replypier.min.js; both bundles rebuilt
from source (backend/assets/widget.{js,css}, frontend/public/webclient)
- NOTICE, llms.txt, CONTRIBUTING, HELP_CENTER_INFRA and config.dev.js
rewritten rather than string-swapped; the demo config no longer ships
the previous vendor's Firebase/Razorpay/Google keys
- new migration replypier_ai_model_001 adds REPLYPIER to the managed
AIModelType and rewrites pre-rename rows
- local compose project, database, role and volume renamed; LOCAL_DEPLOY
documents carrying the old local data over
This commit is contained in:
1 parent
ff0a09f0e5
commit
54b949b392
1156 files changed
+7292
-7147
No files matched your search
@@ -1,5 +1,5 @@
|
||||
"""
|
||||
Copyright 2024-2026 ChatterMate
|
||||
Copyright 2024-2026 ReplyPier
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
@@ -154,7 +154,7 @@ def _widget_runtime_config(request: Optional[Request] = None) -> dict:
|
||||
|
||||
Derived from ``BACKEND_URL`` so a self-hosted widget talks to the configured
|
||||
backend instead of the vendor cloud. On the hosted deployment BACKEND_URL is
|
||||
``https://api.chattermate.chat``, which yields exactly the widget's baked-in
|
||||
``https://api.replypier.site``, which yields exactly the widget's baked-in
|
||||
defaults, so injecting this is a no-op there.
|
||||
"""
|
||||
global _warned_about_loopback_backend_url
|
||||
|
||||
Reference in new issue
Block a user