Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/corporate/urls.py

295 lines
11 KiB
Python
Raw Normal View History

billing: Move billing-related views and urls to corporate.
2018-09-25 12:24:11 +02:00
from typing import Any
urls: Migrate corporate urls to use modern django pattern.
2020-05-05 12:25:47 +02:00
from django.conf.urls import include
from django.urls import path
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
from django.views.generic import RedirectView, TemplateView
billing: Move billing-related views and urls to corporate.
2018-09-25 12:24:11 +02:00
billing_page: Successfully render for remote realms and server.
2023-12-01 10:43:04 +01:00
from corporate.views.billing_page import (
billing_page,
remote_realm_billing_page,
remote_server_billing_page,
remote_billing: Add endpoint and a helper to make deactivation links. This is a general link for logging into the billing system on behalf of a server, but it's tied to the .contact_email and takes the user straight to the /deactivate/ page via the next_page mechanism.
2023-12-12 19:35:16 +01:00
remote_server_deactivate_page,
billing_page: Successfully render for remote realms and server.
2023-12-01 10:43:04 +01:00
update_plan,
billing: Make various buttons on billing page work. We pass billing_base_url to the template and use it to construct session specific URLs. Also, add corresponding function on server to support them.
2023-12-02 09:09:43 +01:00
update_plan_for_remote_realm,
update_plan_for_remote_server,
billing_page: Successfully render for remote realms and server.
2023-12-01 10:43:04 +01:00
)
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
from corporate.views.event_status import (
event_status,
event_status_page,
remote_realm_event_status,
remote_realm_event_status_page,
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
remote_server_event_status,
event_status: Pass billing_base_url to calculate realm specific URLs.
2023-12-01 04:45:05 +01:00
remote_server_event_status_page,
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
)
portico: Move to corporate folder. Since the URLs that use these function are present in corporate/urls, this file belongs in the corporate folder.
2022-08-17 19:24:10 +02:00
from corporate.views.portico import (
app_download_link_redirect,
apps_view,
portico: Add page to list open organizations. Fixes #22020
2022-08-30 07:47:43 +02:00
communities_view,
portico: Move to corporate folder. Since the URLs that use these function are present in corporate/urls, this file belongs in the corporate folder.
2022-08-17 19:24:10 +02:00
hello_view,
landing_view,
plans_view,
plans: Show buttons as per current context. Also show correct tab based on remote / cloud user.
2023-12-05 07:42:52 +01:00
remote_realm_plans_page,
remote_server_plans_page,
portico: Move to corporate folder. Since the URLs that use these function are present in corporate/urls, this file belongs in the corporate folder.
2022-08-17 19:24:10 +02:00
team_view,
)
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
from corporate.views.remote_billing_page import (
remote_billing: Implement confirmation flow for legacy servers. For the last form (with Full Name and ToS consent field), this pretty shamelessly re-uses and directly renders the corporate/remote_realm_billing_finalize_login_confirmation.html template. That's probably good in terms of re-use, but calls for a clean-up commit that will generalize the name of this template and the classes/ids in the HTML.
2023-12-08 19:00:04 +01:00
remote_billing_legacy_server_confirm_login,
remote_billing_legacy_server_from_login_confirmation_link,
remote_billing: Add flow for legacy servers.
2023-11-29 21:30:46 +01:00
remote_billing_legacy_server_login,
remote_billing: Implement confirmation flow for RemoteRealm auth. The way the flow goes now is this: 1. The user initiaties login via "Billing" in the gear menu. 2. That takes them to `/self-hosted-billing/` (possibly with a `next_page` param if we use that for some gear menu options). 3. The server queries the bouncer to give the user a link with a signed access token. 4. The user is redirected to that link (on `selfhosting.zulipchat.com`). Now we have two cases, either the user is logging in for the first time and already did in the past. If this is the first time, we have: 5. The user is asked to fill in their email in a form that's shown, pre-filled with the value provided inside the signed access token. They POST this to the next endpoint. 6. The next endpoint sends a confirmation email to that address and asks the user to go check their email. 7. The user clicks the link in their email is taken to the from_confirmation endpoint. 8. Their initial RemoteBillingUser is created, a new signed link like in (3) is generated and they're transparently taken back to (4), where now that they have a RemoteBillingUser, they're handled just like a user who already logged in before: If the user already logged in before, they go straight here: 9. "Confirm login" page - they're shown their information (email and full_name), can update their full name in the form if they want. They also accept ToS here if necessary. They POST this form back to the endpoint and finally have a logged in session. 10. They're redirected to billing (or `next_page`) now that they have access.
2023-12-10 17:10:56 +01:00
remote_realm_billing_confirm_email,
remote_billing: Rename the _billing_entry and _finalize_login functions. These names were picked when I still thought these endpoints would serve both the RemoteRealm and RemoteZulipServer based flows. Now that it's known these are RemoteRealm-only endpoints, the _server in the names no longer makes sense.
2023-12-04 00:20:53 +01:00
remote_realm_billing_finalize_login,
remote_billing: Implement confirmation flow for RemoteRealm auth. The way the flow goes now is this: 1. The user initiaties login via "Billing" in the gear menu. 2. That takes them to `/self-hosted-billing/` (possibly with a `next_page` param if we use that for some gear menu options). 3. The server queries the bouncer to give the user a link with a signed access token. 4. The user is redirected to that link (on `selfhosting.zulipchat.com`). Now we have two cases, either the user is logging in for the first time and already did in the past. If this is the first time, we have: 5. The user is asked to fill in their email in a form that's shown, pre-filled with the value provided inside the signed access token. They POST this to the next endpoint. 6. The next endpoint sends a confirmation email to that address and asks the user to go check their email. 7. The user clicks the link in their email is taken to the from_confirmation endpoint. 8. Their initial RemoteBillingUser is created, a new signed link like in (3) is generated and they're transparently taken back to (4), where now that they have a RemoteBillingUser, they're handled just like a user who already logged in before: If the user already logged in before, they go straight here: 9. "Confirm login" page - they're shown their information (email and full_name), can update their full name in the form if they want. They also accept ToS here if necessary. They POST this form back to the endpoint and finally have a logged in session. 10. They're redirected to billing (or `next_page`) now that they have access.
2023-12-10 17:10:56 +01:00
remote_realm_billing_from_login_confirmation_link,
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
)
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
from corporate.views.session import (
start_card_update_stripe_session,
upgrade: Separate add card and purchase upgrade flow. We now let user add / update card in a separate session and then charge users after clicking on the purchase button.
2023-11-18 11:29:04 +01:00
start_card_update_stripe_session_for_realm_upgrade,
billing: Make various buttons on billing page work. We pass billing_base_url to the template and use it to construct session specific URLs. Also, add corresponding function on server to support them.
2023-12-02 09:09:43 +01:00
start_card_update_stripe_session_for_remote_realm,
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
start_card_update_stripe_session_for_remote_realm_upgrade,
billing: Make various buttons on billing page work. We pass billing_base_url to the template and use it to construct session specific URLs. Also, add corresponding function on server to support them.
2023-12-02 09:09:43 +01:00
start_card_update_stripe_session_for_remote_server,
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
start_card_update_stripe_session_for_remote_server_upgrade,
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
)
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
from corporate.views.sponsorship import (
remote_realm_sponsorship,
remote_realm_sponsorship_page,
remote_server_sponsorship,
remote_server_sponsorship_page,
sponsorship,
sponsorship_page,
)
corporate: Add contact support page.
2021-09-29 19:51:55 +02:00
from corporate.views.support import support_request
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
from corporate.views.upgrade import (
upgrade: Make purchase upgrade work for remove servers and realms. We are upgrading them to cloud standard right now, we can easily change tiers in future while adding pricing and configuration for them.
2023-12-01 07:14:12 +01:00
remote_realm_upgrade,
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
remote_realm_upgrade_page,
upgrade: Make purchase upgrade work for remove servers and realms. We are upgrading them to cloud standard right now, we can easily change tiers in future while adding pricing and configuration for them.
2023-12-01 07:14:12 +01:00
remote_server_upgrade,
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
remote_server_upgrade_page,
upgrade,
upgrade_page,
)
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
from corporate.views.webhook import stripe_webhook
rest: Add rest_path shortcut for path with rest_dispatch. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2020-09-22 06:04:45 +02:00
from zerver.lib.rest import rest_path
urls: Extend documentation URL redirects system to corporate landing pages. Extends the URL redirect system used for documentation pages to corporate landing pages. This makes it easier and consistent for contributors who work on both areas to create new URL redirects when needed.
2022-08-23 11:57:47 +02:00
from zerver.lib.url_redirects import LANDING_PAGE_REDIRECTS
Create non-localserver "corporate" app with jobs pages. The corporate "app" is not a full-fledged Django app, but it has a urls.py and a templates directory. This commit creates the app and moves the jobs pages into it. Localserver deployments will not see any of the corporate code. (imported from commit 35889c3cf92329258c30741fdfa564769a4fac1a)
2013-11-05 23:50:19 +01:00
python: Convert assignment type annotations to Python 3.6 style. This commit was split by tabbott; this piece covers the vast majority of files in Zulip, but excludes scripts/, tools/, and puppet/ to help ensure we at least show the right error messages for Xenial systems. We can likely further refine the remaining pieces with some testing. Generated by com2ann, with whitespace fixes and various manual fixes for runtime issues: - invoiced_through: Optional[LicenseLedger] = models.ForeignKey( + invoiced_through: Optional["LicenseLedger"] = models.ForeignKey( -_apns_client: Optional[APNsClient] = None +_apns_client: Optional["APNsClient"] = None - notifications_stream: Optional[Stream] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) - signup_notifications_stream: Optional[Stream] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) + notifications_stream: Optional["Stream"] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) + signup_notifications_stream: Optional["Stream"] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) - author: Optional[UserProfile] = models.ForeignKey('UserProfile', blank=True, null=True, on_delete=CASCADE) + author: Optional["UserProfile"] = models.ForeignKey('UserProfile', blank=True, null=True, on_delete=CASCADE) - bot_owner: Optional[UserProfile] = models.ForeignKey('self', null=True, on_delete=models.SET_NULL) + bot_owner: Optional["UserProfile"] = models.ForeignKey('self', null=True, on_delete=models.SET_NULL) - default_sending_stream: Optional[Stream] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) - default_events_register_stream: Optional[Stream] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) + default_sending_stream: Optional["Stream"] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) + default_events_register_stream: Optional["Stream"] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) -descriptors_by_handler_id: Dict[int, ClientDescriptor] = {} +descriptors_by_handler_id: Dict[int, "ClientDescriptor"] = {} -worker_classes: Dict[str, Type[QueueProcessingWorker]] = {} -queues: Dict[str, Dict[str, Type[QueueProcessingWorker]]] = {} +worker_classes: Dict[str, Type["QueueProcessingWorker"]] = {} +queues: Dict[str, Dict[str, Type["QueueProcessingWorker"]]] = {} -AUTH_LDAP_REVERSE_EMAIL_SEARCH: Optional[LDAPSearch] = None +AUTH_LDAP_REVERSE_EMAIL_SEARCH: Optional["LDAPSearch"] = None Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2020-04-22 01:09:50 +02:00
i18n_urlpatterns: Any = [
Move static MIT-related pages to corporate app. (imported from commit e2c5f72d3f3e4d8f8fa888326b2ba455beb9156c)
2013-11-06 12:50:13 +01:00
# Zephyr/MIT
python: Normalize quotes with Black. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-02-12 08:20:45 +01:00
path("zephyr/", TemplateView.as_view(template_name="corporate/zephyr.html")),
path("zephyr-mirror/", TemplateView.as_view(template_name="corporate/zephyr-mirror.html")),
path("jobs/", TemplateView.as_view(template_name="corporate/jobs.html")),
billing: Move billing-related views and urls to corporate.
2018-09-25 12:24:11 +02:00
# Billing
billing: Rename billing_home to billing_page.
2023-12-01 07:39:05 +01:00
path("billing/", billing_page, name="billing_page"),
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
path("sponsorship/", sponsorship_page, name="sponsorship_request"),
initial_upgrade: Rename to upgrade_page. Replaced for "(initial_upgrade)", " initial_upgrade" `'initial_upgrade'` and `"initial_upgrade"`.
2023-11-23 09:31:46 +01:00
path("upgrade/", upgrade_page, name="upgrade_page"),
corporate: Add contact support page.
2021-09-29 19:51:55 +02:00
path("support/", support_request),
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
path("billing/event_status/", event_status_page, name="event_status_page"),
path("stripe/webhook/", stripe_webhook, name="stripe_webhook"),
python: Convert assignment type annotations to Python 3.6 style. This commit was split by tabbott; this piece covers the vast majority of files in Zulip, but excludes scripts/, tools/, and puppet/ to help ensure we at least show the right error messages for Xenial systems. We can likely further refine the remaining pieces with some testing. Generated by com2ann, with whitespace fixes and various manual fixes for runtime issues: - invoiced_through: Optional[LicenseLedger] = models.ForeignKey( + invoiced_through: Optional["LicenseLedger"] = models.ForeignKey( -_apns_client: Optional[APNsClient] = None +_apns_client: Optional["APNsClient"] = None - notifications_stream: Optional[Stream] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) - signup_notifications_stream: Optional[Stream] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) + notifications_stream: Optional["Stream"] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) + signup_notifications_stream: Optional["Stream"] = models.ForeignKey('Stream', related_name='+', null=True, blank=True, on_delete=CASCADE) - author: Optional[UserProfile] = models.ForeignKey('UserProfile', blank=True, null=True, on_delete=CASCADE) + author: Optional["UserProfile"] = models.ForeignKey('UserProfile', blank=True, null=True, on_delete=CASCADE) - bot_owner: Optional[UserProfile] = models.ForeignKey('self', null=True, on_delete=models.SET_NULL) + bot_owner: Optional["UserProfile"] = models.ForeignKey('self', null=True, on_delete=models.SET_NULL) - default_sending_stream: Optional[Stream] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) - default_events_register_stream: Optional[Stream] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) + default_sending_stream: Optional["Stream"] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) + default_events_register_stream: Optional["Stream"] = models.ForeignKey('zerver.Stream', null=True, related_name='+', on_delete=CASCADE) -descriptors_by_handler_id: Dict[int, ClientDescriptor] = {} +descriptors_by_handler_id: Dict[int, "ClientDescriptor"] = {} -worker_classes: Dict[str, Type[QueueProcessingWorker]] = {} -queues: Dict[str, Dict[str, Type[QueueProcessingWorker]]] = {} +worker_classes: Dict[str, Type["QueueProcessingWorker"]] = {} +queues: Dict[str, Dict[str, Type["QueueProcessingWorker"]]] = {} -AUTH_LDAP_REVERSE_EMAIL_SEARCH: Optional[LDAPSearch] = None +AUTH_LDAP_REVERSE_EMAIL_SEARCH: Optional["LDAPSearch"] = None Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2020-04-22 01:09:50 +02:00
]
billing: Move billing-related views and urls to corporate.
2018-09-25 12:24:11 +02:00
v1_api_and_json_patterns = [
python: Normalize quotes with Black. Signed-off-by: Anders Kaseorg <anders@zulip.com>
2021-02-12 08:20:45 +01:00
rest_path("billing/upgrade", POST=upgrade),
rest_path("billing/sponsorship", POST=sponsorship),
billing: Use PATCH request for changing plan status. I think it's much more cleaner to use PATCH request on /json/billing/plan than using a POST request on /json/billing/plan/change to update the plan.
2020-12-10 18:15:09 +01:00
rest_path("billing/plan", PATCH=update_plan),
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
rest_path("billing/session/start_card_update_session", POST=start_card_update_stripe_session),
rest_path(
upgrade: Separate add card and purchase upgrade flow. We now let user add / update card in a separate session and then charge users after clicking on the purchase button.
2023-11-18 11:29:04 +01:00
"upgrade/session/start_card_update_session",
POST=start_card_update_stripe_session_for_realm_upgrade,
billing: Migrate to Stripe hosted checkout page.
2021-08-29 15:33:29 +02:00
),
rest_path("billing/event/status", GET=event_status),
Enable i18n support in URL configuration. This supports i18n using all of the following: - I18N urls - Session - Cookie - HTTP header
2016-05-19 17:33:30 +02:00
]
Don't show Zulip.com terms on other sites While we already don't link to /terms anywhere on the site, they can still be accessed if you navigate to /terms directly. Now, those routes will only be exported on the Zulip.com service. We should ideally provide a mechanism for deployments to specify their own terms without modifying source code; in the interim, sites that have already customised the provided Zulip.com terms can simply carry a patch reverting this commit.
2016-03-21 03:13:38 +01:00
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
landing_page_urls = [
# Landing page, features pages, signup form, etc.
path("hello/", hello_view),
urls: Move /features files to corporate folder.
2022-08-16 12:21:47 +02:00
path("features/", landing_view, {"template_name": "corporate/features.html"}),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
path("plans/", plans_view, name="plans"),
path("apps/", apps_view),
path("apps/download/<platform>", app_download_link_redirect),
path("apps/<platform>", apps_view),
path(
"development-community/",
landing_view,
urls: Move /development-community files to corporate folder.
2022-08-16 12:34:43 +02:00
{"template_name": "corporate/development-community.html"},
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
),
urls: Move /attribution files to the corporate folder.
2022-08-16 13:08:32 +02:00
path("attribution/", landing_view, {"template_name": "corporate/attribution.html"}),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
path("team/", team_view),
urls: Move /history files to the corporate folder.
2022-08-16 13:11:48 +02:00
path("history/", landing_view, {"template_name": "corporate/history.html"}),
portico: Add a page about our values.
2022-10-07 19:24:59 +02:00
path("values/", landing_view, {"template_name": "corporate/values.html"}),
urls: Move /why-zulip pages to the corporate folder.
2022-08-16 13:20:04 +02:00
path("why-zulip/", landing_view, {"template_name": "corporate/why-zulip.html"}),
url: Move /self-hosting pages to the corporate folder.
2022-08-16 13:22:16 +02:00
path("self-hosting/", landing_view, {"template_name": "corporate/self-hosting.html"}),
urls: Move /security files to the corporate folder.
2022-08-16 13:24:56 +02:00
path("security/", landing_view, {"template_name": "corporate/security.html"}),
portico: Add landing page about trying Zulip by visiting chat.zulip.org.
2023-03-07 00:09:24 +01:00
path("try-zulip/", landing_view, {"template_name": "corporate/try-zulip.html"}),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
# /for pages
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
path("use-cases/", landing_view, {"template_name": "corporate/for/use-cases.html"}),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
path(
"for/communities/",
landing_view,
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
{"template_name": "corporate/for/communities.html"},
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
),
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
path("for/education/", landing_view, {"template_name": "corporate/for/education.html"}),
path("for/events/", landing_view, {"template_name": "corporate/for/events.html"}),
path("for/open-source/", landing_view, {"template_name": "corporate/for/open-source.html"}),
path("for/research/", landing_view, {"template_name": "corporate/for/research.html"}),
path("for/business/", landing_view, {"template_name": "corporate/for/business.html"}),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
# case-studies
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
path(
"case-studies/idrift/",
landing_view,
{"template_name": "corporate/case-studies/idrift-case-study.html"},
),
portico: Add End Point Dev case study page.
2023-03-21 22:52:04 +01:00
path(
"case-studies/end-point/",
landing_view,
{"template_name": "corporate/case-studies/end-point-case-study.html"},
),
portico: Add Atolio case study.
2023-04-26 21:53:36 +02:00
path(
"case-studies/atolio/",
landing_view,
{"template_name": "corporate/case-studies/atolio-case-study.html"},
),
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
path(
"case-studies/tum/",
landing_view,
{"template_name": "corporate/case-studies/tum-case-study.html"},
),
path(
"case-studies/ucsd/",
landing_view,
{"template_name": "corporate/case-studies/ucsd-case-study.html"},
),
path(
"case-studies/rust/",
landing_view,
{"template_name": "corporate/case-studies/rust-case-study.html"},
),
path(
"case-studies/lean/",
landing_view,
{"template_name": "corporate/case-studies/lean-case-study.html"},
),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
path(
"case-studies/asciidoctor/",
landing_view,
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
{"template_name": "corporate/case-studies/asciidoctor-case-study.html"},
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
),
path(
"case-studies/recurse-center/",
landing_view,
templates: Move case-studies and /for pages to corporate folder. Since these pages don't belong in a self-hosted server.
2022-07-26 06:12:33 +02:00
{"template_name": "corporate/case-studies/recurse-center-case-study.html"},
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
),
portico: Add page to list open organizations. Fixes #22020
2022-08-30 07:47:43 +02:00
path("communities/", communities_view),
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
]
urls: Extend documentation URL redirects system to corporate landing pages. Extends the URL redirect system used for documentation pages to corporate landing pages. This makes it easier and consistent for contributors who work on both areas to create new URL redirects when needed.
2022-08-23 11:57:47 +02:00
# Redirects due to us having moved or combined landing pages:
for redirect in LANDING_PAGE_REDIRECTS:
old_url = redirect.old_url.lstrip("/")
landing_page_urls += [path(old_url, RedirectView.as_view(url=redirect.new_url, permanent=True))]
urls: Move URLs that don't belong on self-hosted servers to corporate URLs. Use absolute URLs for these links in files which will be served to self-hosted servers.
2022-08-16 09:39:36 +02:00
i18n_urlpatterns += landing_page_urls
billing: Move billing-related views and urls to corporate.
2018-09-25 12:24:11 +02:00
# Make a copy of i18n_urlpatterns so that they appear without prefix for English
urlpatterns = list(i18n_urlpatterns)
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
urlpatterns += [
remote_billing: Rename the _billing_entry and _finalize_login functions. These names were picked when I still thought these endpoints would serve both the RemoteRealm and RemoteZulipServer based flows. Now that it's known these are RemoteRealm-only endpoints, the _server in the names no longer makes sense.
2023-12-04 00:20:53 +01:00
path("remote-billing-login/<signed_billing_access_token>", remote_realm_billing_finalize_login),
remote_billing: Implement confirmation flow for RemoteRealm auth. The way the flow goes now is this: 1. The user initiaties login via "Billing" in the gear menu. 2. That takes them to `/self-hosted-billing/` (possibly with a `next_page` param if we use that for some gear menu options). 3. The server queries the bouncer to give the user a link with a signed access token. 4. The user is redirected to that link (on `selfhosting.zulipchat.com`). Now we have two cases, either the user is logging in for the first time and already did in the past. If this is the first time, we have: 5. The user is asked to fill in their email in a form that's shown, pre-filled with the value provided inside the signed access token. They POST this to the next endpoint. 6. The next endpoint sends a confirmation email to that address and asks the user to go check their email. 7. The user clicks the link in their email is taken to the from_confirmation endpoint. 8. Their initial RemoteBillingUser is created, a new signed link like in (3) is generated and they're transparently taken back to (4), where now that they have a RemoteBillingUser, they're handled just like a user who already logged in before: If the user already logged in before, they go straight here: 9. "Confirm login" page - they're shown their information (email and full_name), can update their full name in the form if they want. They also accept ToS here if necessary. They POST this form back to the endpoint and finally have a logged in session. 10. They're redirected to billing (or `next_page`) now that they have access.
2023-12-10 17:10:56 +01:00
path(
"remote-billing-login/<signed_billing_access_token>/confirm/",
remote_realm_billing_confirm_email,
),
path(
"remote-billing-login/do_confirm/<confirmation_key>",
remote_realm_billing_from_login_confirmation_link,
name="remote_realm_billing_from_login_confirmation_link",
),
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
# Remote server billing endpoints.
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
path("realm/<realm_uuid>/plans/", remote_realm_plans_page, name="remote_realm_plans_page"),
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"server/<server_uuid>/plans/",
urls: Rename function names to match naming syntax of remote pages.
2023-12-01 07:23:39 +01:00
remote_server_plans_page,
name="remote_server_plans_page",
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
),
billing_page: Successfully render for remote realms and server.
2023-12-01 10:43:04 +01:00
path(
"realm/<realm_uuid>/billing/", remote_realm_billing_page, name="remote_realm_billing_page"
),
path(
"server/<server_uuid>/billing/",
remote_server_billing_page,
name="remote_server_billing_page",
),
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"realm/<realm_uuid>/upgrade/", remote_realm_upgrade_page, name="remote_realm_upgrade_page"
),
path(
"server/<server_uuid>/upgrade/",
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
remote_server_upgrade_page,
name="remote_server_upgrade_page",
),
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"realm/<realm_uuid>/sponsorship/",
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
remote_realm_sponsorship_page,
name="remote_realm_sponsorship_page",
),
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"server/<server_uuid>/sponsorship/",
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
remote_server_sponsorship_page,
name="remote_server_sponsorship_page",
),
remote_billing: Add endpoint and a helper to make deactivation links. This is a general link for logging into the billing system on behalf of a server, but it's tied to the .contact_email and takes the user straight to the /deactivate/ page via the next_page mechanism.
2023-12-12 19:35:16 +01:00
path(
"server/<server_uuid>/deactivate/",
remote_server_deactivate_page,
name="remote_server_deactivate_page",
),
remote_billing: Add flow for legacy servers.
2023-11-29 21:30:46 +01:00
path(
"serverlogin/",
remote_billing_legacy_server_login,
name="remote_billing_legacy_server_login",
),
remote_billing: Implement confirmation flow for legacy servers. For the last form (with Full Name and ToS consent field), this pretty shamelessly re-uses and directly renders the corporate/remote_realm_billing_finalize_login_confirmation.html template. That's probably good in terms of re-use, but calls for a clean-up commit that will generalize the name of this template and the classes/ids in the HTML.
2023-12-08 19:00:04 +01:00
path(
"serverlogin/<server_uuid>/confirm/",
remote_billing_legacy_server_confirm_login,
name="remote_billing_legacy_server_confirm_login",
),
path(
"serverlogin/do_confirm/<confirmation_key>",
remote_billing_legacy_server_from_login_confirmation_link,
name="remote_billing_legacy_server_from_login_confirmation_link",
),
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"realm/<realm_uuid>/billing/event_status/",
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
remote_realm_event_status_page,
name="remote_realm_event_status_page",
),
event_status: Pass billing_base_url to calculate realm specific URLs.
2023-12-01 04:45:05 +01:00
path(
urls: Add `/` to `_page` URLs to avoid redirects.
2023-12-04 18:16:42 +01:00
"server/<server_uuid>/billing/event_status/",
event_status: Pass billing_base_url to calculate realm specific URLs.
2023-12-01 04:45:05 +01:00
remote_server_event_status_page,
name="remote_server_event_status_page",
),
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
# Remote variants of above API endpoints.
sponsorship: Populate sponsorship page with correct context. Fixes sponsorship page to work for remote realm and server.
2023-12-05 07:41:34 +01:00
path("json/realm/<realm_uuid>/billing/sponsorship", remote_realm_sponsorship),
path("json/server/<server_uuid>/billing/sponsorship", remote_server_sponsorship),
billing: Make various buttons on billing page work. We pass billing_base_url to the template and use it to construct session specific URLs. Also, add corresponding function on server to support them.
2023-12-02 09:09:43 +01:00
path(
"json/realm/<realm_uuid>/billing/session/start_card_update_session",
start_card_update_stripe_session_for_remote_realm,
),
path(
"json/server/<server_uuid>/billing/session/start_card_update_session",
start_card_update_stripe_session_for_remote_server,
),
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
path(
"json/realm/<realm_uuid>/upgrade/session/start_card_update_session",
start_card_update_stripe_session_for_remote_realm_upgrade,
),
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
path(
"json/server/<server_uuid>/upgrade/session/start_card_update_session",
start_card_update_stripe_session_for_remote_server_upgrade,
),
upgrade: Make add card workflow functional. Add / update card for remote realms on /upgrade page works now.
2023-11-30 14:06:41 +01:00
path("json/realm/<realm_uuid>/billing/event/status", remote_realm_event_status),
upgrade: Make card add / update work for remote servers.
2023-12-01 06:44:59 +01:00
path("json/server/<server_uuid>/billing/event/status", remote_server_event_status),
upgrade: Make purchase upgrade work for remove servers and realms. We are upgrading them to cloud standard right now, we can easily change tiers in future while adding pricing and configuration for them.
2023-12-01 07:14:12 +01:00
path("json/realm/<realm_uuid>/billing/upgrade", remote_realm_upgrade),
path("json/server/<server_uuid>/billing/upgrade", remote_server_upgrade),
billing: Make various buttons on billing page work. We pass billing_base_url to the template and use it to construct session specific URLs. Also, add corresponding function on server to support them.
2023-12-02 09:09:43 +01:00
path("json/realm/<realm_uuid>/billing/plan", update_plan_for_remote_realm),
path("json/server/<server_uuid>/billing/plan", update_plan_for_remote_server),
billing: Add BillingSession support for requesting sponsorship.
2023-11-30 01:48:46 +01:00
]
urlpatterns += [
path("api/v1/", include(v1_api_and_json_patterns)),
path("json/", include(v1_api_and_json_patterns)),
corporate: Add prototype authentication system for self-hosters. This makes it possible for a self-hosted realm administrator to directly access a logged-page on the push notifications bouncer service, enabling billing, support contacts, and other administrator for enterprise customers to be managed without manual setup.
2023-11-15 22:44:24 +01:00
]