Rename onpremise to self-hosted

[chadwhitacre]

In the docs we're using "self-hosted" to name what we're doing here. For branding purposes I would like to standardize on that and stop referring to "onpremise."

(Short URL, fwiw: https://git.io/JSDlX)

Todo

• rename repo
• code
  • easy
    • sentry.io—archived repo
    • sentry-release—moribund repo, don't care
    • getsentry/labels@9d35acc
    • getsentry/deps@5962f6b
    • https://github.com/getsentry/demo/pull/11
    • Rename onpremise to self-hosted develop#469
    • Rename onpremise to self-hosted eng-pipes#273
    • https://github.com/getsentry/etl/pull/671
    • https://github.com/getsentry/lookml/pull/318
    • Rename onpremise to self-hosted publish#670
    • Rename onpremise to self-hosted relay#1136
    • Rename onpremise to self-hosted #1169
    • sentry
      • Start renaming onpremise to self-hosted sentry#30482
      • Continue self-hosted rename in build-related files sentry#30483
      • Remove RemoteNewsletter (unused for 4 years) sentry#30486
    • Rename onpremise to self-hosted sentry-dart#642
    • Rename onpremise to self-hosted sentry-docs#4437
    • Rename onpremise to self-hosted snuba#2240
    • https://github.com/getsentry/static-sites/pull/773
  • hard
    • backend
      • https://github.com/getsentry/getsentry/pull/6841
      • https://github.com/getsentry/single-tenant/pull/429
      • Switch from ONPREMISE to SELF_HOSTED on backend sentry#30973
      • Comment sweep for onprem → self-hosted sentry#31066
    • frontend
      • add isSelfHosted in sentry (done in #30973)
      • Flip to isSelfHosted on the frontend sentry#31065
    • trust it
      • https://github.com/getsentry/getsentry/pull/6866
      • remove SENTRY_ONPREMISE in single-tenant
        • punting for "months" ... documented in https://github.com/getsentry/single-tenant/pull/432
        • https://github.com/getsentry/getsentry/pull/10950
    • remove SENTRY_ONPREMISE and isOnPremise in sentry (kill backcompat) – do this, like, waaaaay later
• forums—Deprecate forum in favor of GitHub Issues #1151
• blog—Rename onpremise to self-hosted #796 (comment)
• Repair triage stats post-rename eng-pipes#274
• Audit to make sure monthly CalVer release will work.

[BYK]

I'm not sure if the effort is worth the benefits.

[chadwhitacre]

GitHub handles renames gracefully. The one lingering question I've had is forks, but it seems from testing (not seeing docs) that there's no issue with a fork of a renamed repo. The fork keeps the old name, and its connection to the renamed parent. If anyone with a fork has the upstream set as a remote, GitHub redirection/aliasing ensures that they are unaffected—as long as we never break the redirect by creating a new onpremise repo.

tl;dr I think the effort is trivial.

Fork Test

[BYK]

Alright, you know what, let's try this :)

[chadwhitacre]

@ingria Do you foresee problems with this? Why are you 😕?

[ingria]

Technically - no, not at all. I just didn't understand what the benefits of renaming would be. That's why I was a little 😕

Anyway, there are also some other places that might need to be edited:

• Help articles (example)
• Community forums
• Blog articles (example)

[chadwhitacre]

benefits

Less confusion. Right now we use two names—"on-premise," "self-hosted"—for the same thing. May not be worth it. Need to stew on this some more ... 🤔

[chadwhitacre]

The more I think about it, the more I don't like either name—onpremise or self-hosted—for this repo. I think a better name would be single-node, because it better captures our intention here: to package up all of Sentry for deployment on a single node, in order to support a) proofs of concept for people evaluating SaaS, and b) small deployments for students, hobbyists, and small orgs. "Self-hosted" is broader as it really encompasses multi-node setups, too, which we don't officially support and never will (SaaS! SaaS!). Moreover, work that is relevant to self-hosters of any scale quite often (almost always?) impacts our other "primary" repos, e.g. #863 and #857 should really be against sentry, imo. We have a label in that repo to flag issues of particular (exclusive?) relevance to self-hosters.

[ingria]

This name may better reflect how it's supposed to work, but it doesn't describe what is this project for.

I mean, imagine you've just heard about some cool project called Gentry. And you'd like to know whether it's possible to use it on your own servers. How would you google it: "gentry self hosted" or "gentry single node"?

In other words, "single-node" is ok for a repo name, but not ok for a product name. Just my opinion, of course.