Skip to content

Commit

Permalink
[automated commit] Bump docs to version 1.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
leorossi authored and github-actions[bot] committed Oct 6, 2023
1 parent c144bda commit 08a9ec2
Show file tree
Hide file tree
Showing 140 changed files with 2,559 additions and 17 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,8 @@ The base services are:

These micro-services can be developed and deployed independently or aggregated into a single API using [Platformatic Composer](#platformatic-composer) or deployed as a single unit using [Platformatic Runtime](#platformatic-runtime).

Finally, platformatic components can be reused with [stackables](#platformatic-stackbles)
All platformatic components can be reused with [Stackables](#platformatic-stackbles).
And finally, all Platformatic components can be deployed on [Platformatic Cloud](#platformatic-cloud).

## Platformatic Service

Expand Down Expand Up @@ -70,10 +71,18 @@ Platformatic Stackables are reusable components that can be used to build Platfo

This is useful to publish the application on the public npm registry (or a private one!), including building your own CLI, or to create a specialized template for your organization to allow for centralized bugfixes and updates.

## Platformatic Cloud
[Platformatic Cloud](https://platformatic.cloud) allows to deploy Platformatic Applications on our cloud for both static deployments and PR reviews.
The deployment on the cloud can be done:
- Automatically using the GitHub actions created with `create-platformatic`
- Using the Platformatic CLI (see https://docs.platformatic.dev/docs/reference/cli#deploy)

If you configure the GitHub actions, you can deploy your application on the cloud by simply pushing to the main branch or creating a PR. For a guide about how to do a deploy on Platformatic Cloud, please check the [Platformatic Cloud Quick Start Guide](https://docs.platformatic.dev/docs/platformatic-cloud/quick-start-guide).




:::info
If you create a PR, we calculate automatically the "risk score" for that PR. For more info about this,
see [Calculate the risk of a pull request](https://docs.platformatic.dev/docs/platformatic-cloud/quick-start-guide/#calculate-the-risk-of-a-pull-request).
:::


Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This process is the same one we use to maintain Platformatic DB and Platformatic

## Creating a custom Service

We are creating the module `foo.js` as follows:
We are creating the stackable `foo.js` as follows:

```js
const { schema, platformaticService } = require('@platformatic/service')
Expand Down Expand Up @@ -51,7 +51,7 @@ foo.schema = {
$schema: {
type: 'string'
},
module: {
extends: {
type: 'string'
},
foo: {
Expand Down Expand Up @@ -102,7 +102,7 @@ Consuming `foo.js` is simple. We can create a `platformatic.json` file as follow
```json
{
"$schema": "https://example.com/schemas/foo.json",
"module": "./foo",
"extends": "./foo",
"server": {
"port": 0,
"hostname": "127.0.0.1"
Expand All @@ -113,11 +113,12 @@ Consuming `foo.js` is simple. We can create a `platformatic.json` file as follow
}
```

Note that we __must__ specify both the `$schema` property and `module`.
Module can also be any modules published on npm and installed via your package manager.
Note that we __must__ specify both the `$schema` property and `extends`.
The module specified with `extends` can also be any modules published on npm and installed via your package manager.

:::note
The `module` is the name of the module we are actually "stacking" on top of.
`extends` is the name of the module we are actually "stacking" (extending) on top of.
The property `module` can also be used, but it is deprecated. In both cases, be sure that the property is allowed in the stackable schema (in this example in `foo.schema`)
:::

## Building your own CLI
Expand Down
Loading

0 comments on commit 08a9ec2

Please sign in to comment.