-
Notifications
You must be signed in to change notification settings - Fork 76
[FWF Docs]: Fix typos, grammar, and snippets & fix broken links in all developer.fermyon.com #1529
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Thorsten Hans <[email protected]>
Signed-off-by: Thorsten Hans <[email protected]>
Signed-off-by: Thorsten Hans <[email protected]>
Signed-off-by: Thorsten Hans <[email protected]>
Signed-off-by: Thorsten Hans <[email protected]>
Signed-off-by: Thorsten Hans <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the https://x.com/lrz/status/1250453967957561344?s=20
url needs to be added to the ignore-list (per the 403) in the broken-links script, otherwise LGTM!
@@ -16,7 +16,7 @@ url = "https://github.com/fermyon/developer/blob/main/content/cloud/data-postgre | |||
|
|||
## PostgreSQL | |||
|
|||
[PostgreSQL](https://www.postgresql.org/), is a powerful, open-source object-relational database system that has earned a strong reputation for reliability, robustness and performance. This tutorial will implement a persistent storage solution for Fermyon Cloud, using PostgreSQL. In this tutorial, we will be using [ElephantSQL](https://www.elephantsql.com/plans.html)'s free PostgreSQL service. | |||
[PostgreSQL](https://www.postgresql.org/), is a powerful, open-source object-relational database system that has earned a strong reputation for reliability, robustness and performance. This tutorial will implement a persistent storage solution for Fermyon Cloud, using PostgreSQL. In this tutorial, we will be using ElephantSQL's free PostgreSQL service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ElephantSQL is discontinued, and we shouldn't refer to it. (I thought I had addressed this somewhere but I can't find a PR so... I guess I didn't.) I realise this turns the edit into a rather bigger research and conversion exercise, though, so feel free to raise a separate issue and punt on it.
@@ -72,8 +72,10 @@ $ spin aka apps info --name hello-fermyon-wasm-functions | |||
<!-- @nocpy --> | |||
|
|||
```console | |||
Name: hello-fermyon-wasm-functions | |||
Name: hello-fermyon-wasm-functions (25a5fd1e-d476-40fd-bc54-6cee0e846540) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No action for now, but I've raised an issue for ID to be a separate field like it is in the JSON
@@ -437,8 +442,9 @@ If the build fails, check: | |||
|
|||
* Are you in the `hello-spin` directory? | |||
* Did you successfully [install TinyGo](#install-language-specific-tooling)? | |||
* Are your versions of Go and TinyGo up to date? The Spin SDK needs TinyGo 0.27 or above. | |||
* Are your versions of Go and TinyGo up to date? The Spin SDK needs TinyGo 0.27 or above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adamreese Is this version requirement still correct? Spin docs says TinyGo 0.35 and Go 1.22. https://spinframework.dev/v3/quickstart#build-your-application
This PR consists of multiple commits:
wasm-functions/index
wasm-functions/quickstart
wasm-functions/deploy
wasm-functions/list-and-inspect
wasm-functions/delete
Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:
title
,template
, anddate
are all settemplates/*.hbs
files) that points to a document.md
that is set to publish in the future? If so please only publish the.md
and.hbs
changes in real-time (otherwise there will be a menu item pointing to a.md
file that does not exist)cat -ve <filename> | grep $'\r' | wc -l
and expect 0 as a result)bart check
PREVIEW_MODE=1
and runnpm run styles
to update styling)npm run test
and resolved all errors