Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4221 improvements to dedicated docs #4249

Open
wants to merge 68 commits into
base: main
Choose a base branch
from

Conversation

Kemi-Elizabeth
Copy link
Collaborator

Why

Closes #4221

What's changed

Added more pages and diagrams, and also changed the set up of the Dedicated Environments section.

Where are changes

The changes are all the Dedicated Environments section.

Updates are for:
[] platform (sites/platform templates)
[] upsun (sites/upsun templates)

Kemi-Elizabeth and others added 8 commits November 5, 2024 03:57
Very rough draft to help with debugging local preview generation issue
* updates /anchors/dns.html to the correct final location

* updates /anchors/import-data/mysql.html to the correct final location

* updates /anchors/crons/paused.html to the correct final location

* updates /anchors/import-data/postgresql.html to the correct final location

* corrects landing link for timezone and backup

* corrects landing link for flexible resources

* corrects landing link for backups because my initial assumption was incorrect

* corrects landing link for anchors/observability/metrics/grid
added images, changed titles etc
still need edit other tables
made edits to tables on page
corrected link and removed row from table
@Kemi-Elizabeth Kemi-Elizabeth linked an issue Nov 7, 2024 that may be closed by this pull request
@Kemi-Elizabeth Kemi-Elizabeth requested review from gilzow and chadwcarlson and removed request for gilzow November 7, 2024 14:37
added description to index
Updated table with enterprise or elite
Copy link
Collaborator

@gilzow gilzow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see my other generalized comments in the PR directly: #4221

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since we've moved this doc location, should we add a redirect for it in routes.yaml?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

similar: since we've moved this doc location, should we add a redirect for it in routes.yaml?

sidebarTitle: "Differences in development"
description: See the differences between your Production/Staging environments (which are {{% names/dedicated-gen-2 %}}) and your Development environments (which are Grid environments).
sidebarTitle: "Environment differences"
description: See the differences between your Production/Staging environments (which are Dedicated Gen 2) and your Development environments (which are Grid environments).
---

With {{% names/dedicated-gen-2 %}} plans, your Production and Staging environments are dedicated virtual machines,
while your Development environments run on the Grid, meaning shared redundant infrastructure.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we add a link on "grid" to https://docs.platform.sh/glossary.html#grid ?

sidebarTitle: "Differences in development"
description: See the differences between your Production/Staging environments (which are {{% names/dedicated-gen-2 %}}) and your Development environments (which are Grid environments).
sidebarTitle: "Environment differences"
description: See the differences between your Production/Staging environments (which are Dedicated Gen 2) and your Development environments (which are Grid environments).
---

With {{% names/dedicated-gen-2 %}} plans, your Production and Staging environments are dedicated virtual machines,
while your Development environments run on the Grid, meaning shared redundant infrastructure.
This difference means a few configuration options and tools function differently in the different environments.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we have docs on the specific configuration options/tools that are different between the environments? if so, we should link to them here.

| **Environment clone** | Yes on all branches | Only on Development environments |
| **MySQL Replication** | None: standalone service container | Yes: 3 services nodes cluster |
| **Redis Replication** | None: standalone service container | Yes: 3 services nodes cluster |
| **MongoDB** | Standalone service container | Yes |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have "yes" under Dedicated but in the DG2 overview for MongoDB we have "Not supported" and it's not listed at all on the DG3 overview.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to verify this one

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just clarified with the mega spreadsheet I was working from. It had "in progress" in some places and "not supported in others". I've put it down as a no in all cases as now :)

| **Routes management** | Autonomous | Autonomous |
| **Crons management** | Autonomous | Autonomous |
| **Crons tasks interrupted by deploys** | No: a running cron task will block a deployment until it is complete | Yes: a deploy will terminate a running cron task |
| **Mounts management** | Autonomous | Either autonomous or manual |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for dedicated we have "Either autonomous or manual" but I think what we mean here is autonomous or requires a support ticket" since the DG2 page states

Storage: Storage allocation between mounts, DB and services is done through Platform.sh once a ticket is raised. Storage management is not self-service.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we make it

Managed by Platform.sh (Dedicated Gen 2 only)

?


### Encryption 

| AWS | GCP | Azure |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the GCP and Azure headers are flipped? The description below GCP seems like it is the description for Azure.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this section and linked to https://platform.sh/trust-center/security/encryption/ instead!

@@ -0,0 +1 @@
NAMES/DEDICATED TBD
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're still using this shortcode, we need to agree on something here or remove.

Kemi-Elizabeth and others added 11 commits November 14, 2024 12:13
Kemi-Elizabeth and others added 23 commits November 14, 2024 12:35
made suggested changes
made changes
made changes suggested by Paul and Chad.
added glossary terms and made changes based on Jonas clarification
made more changes
made last bits of changes
More changes
Corrected inconsistencies with capitals
changed shortcode - not sure if we reference it though?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improvements to Dedicated docs
4 participants