Skip to content

Conversation

@gmoigneu
Copy link

πŸ”— Linked issue

None

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Platform.sh has been renamed to Upsun. This PR renames the documentation as well as the preset.

The documentation has also been improved with a working configuration and an example.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@gmoigneu gmoigneu requested a review from pi0 as a code owner November 18, 2025 16:06
@vercel
Copy link

vercel bot commented Nov 18, 2025

@gmoigneu is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

@@ -1,37 +0,0 @@
# Platform.sh
Copy link

Choose a reason for hiding this comment

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

Do we want to keep it and redirect people to the Upsun page?

Copy link
Member

Choose a reason for hiding this comment

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

We can add it to docs redircts. BTW this PR is targeting new v3.nitro.build domain.

Copy link
Author

Choose a reason for hiding this comment

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

Yes we can keep the redirect. I can open another PR on the v2 if needed.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 18, 2025

Open in StackBlitz

npm i https://pkg.pr.new/nitrojs/nitro@3803

commit: 6425475

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants