Skip to content

Avoid just/simply #139

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Dec 6, 2024
Merged

Avoid just/simply #139

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e4bd5d7
Avoid just/simply
lionello Dec 5, 2024
e7a9e5a
Merge branch 'main' into lio/just-simply
lionello Dec 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/2024-03-28-slackbot-sample.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Now that we have everything set up, let's dive into the deployment process. Foll
2. **Deploy the Slackbot:** Use the Defang CLI's `defang compose up` command to deploy.

## Usage
With your Slackbot up and running, let's explore how to make the most of it. Simply send a POST request to the `/` endpoint with a JSON body containing the message you want to post to the Slack channel. Popular tools like cURL or Postman can help you send the request:
With your Slackbot up and running, let's explore how to make the most of it. Let's send a POST request to the `/` endpoint with a JSON body containing the message you want to post to the Slack channel. Popular tools like cURL or Postman can help you send the request:

```bash
curl 'https://raphaeltm-bot--8080.prod1.defang.dev/' \
Expand Down
2 changes: 1 addition & 1 deletion blog/2024-05-01-may-product-updates.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Hey folks! There is a lot going on at Defang and we're excited to share our late

## npx defang

We know a lot of you are using Defang for the first time. To make it easier to get started, we've added a new way to install the Defang CLI. Now you can use npx to run the CLI without installing it globally. Just run:
We know a lot of you are using Defang for the first time. To make it easier to get started, we've added a new way to install the Defang CLI. Now you can use npx to run the CLI without installing it globally by running:

```bash
npx defang@latest
Expand Down
2 changes: 1 addition & 1 deletion docs/concepts/accounts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Eventually, billing and payment information will be associated with your account

## Creating an Account

To create an account, simply login to Defang and accept the [terms of service](https://defang.io/terms-service.html) using the [CLI](/docs/concepts/authentication.md).
To create an account, login to Defang and accept the [terms of service](https://defang.io/terms-service.html) using the [CLI](/docs/concepts/authentication.md).

At the moment, the only way to authenticate with Defang is through GitHub. We plan to offer other authentication providers in the future.

Expand Down
2 changes: 1 addition & 1 deletion docs/concepts/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ You can find a sample of how to set environment variables with Pulumi [here](htt

# Sensitive Config aka Secrets

The Defang CLI allows you to securely store sensitive information such as API keys, passwords, and other credentials. To do so just run:
The Defang CLI allows you to securely store sensitive information such as API keys, passwords, and other credentials. To do so, run:

```bash
# Set a configuration value called API_KEY
Expand Down
6 changes: 3 additions & 3 deletions docs/concepts/managed-storage/managed-postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ To use managed Postgres, in your `compose.yaml` file, use the `x-defang-postgres

### Required Configuration

When using managed Postgres, you **must** set a password for the database using `defang config set POSTGRES_PASSWORD`. If you do not provide the password, the deployment will fail.
When using managed Postgres, you **must** set a password for the database using `defang config set POSTGRES_PASSWORD`. If you do not provide the password, the deployment will fail.

- `POSTGRES_PASSWORD`: You can can assign the password in the service's environment variables. To learn more about how this works, read about [configuration](../configuration.md).

Expand All @@ -38,7 +38,7 @@ You can also set the following optional environment variables to configure the m
You can connect to the managed Postgres instance using the name of your service as the hostname, `POSTGRES_USER`, `POSTGRES_DB`, and `POSTGRES_PASSWORD` environment variables.

### Example
:::info
:::info
For a smoother experience with Defang, we recommend using Postgres 14 for your container images. This version provides easier access and improved usability.
:::

Expand Down Expand Up @@ -85,7 +85,7 @@ The AWS Console can be used to restore a snapshop into a new instance of postgre
<!--
### Major Version Updating of Engine

To update the database engine you can simply update the image to a later version in your compose file and apply it via ```defang compose up --provider=aws```. In the example below, we change from Postgres 15 to 16.
To update the database engine you can update the image to a later version in your compose file and apply it via ```defang compose up --provider=aws```. In the example below, we change from Postgres 15 to 16.

Please note the upgrading will occur immediately and may result in the database being unavailable for some time.

Expand Down
Loading