Hello {process.env.SOME_ENV_VAR}
; } ``` --- ### .env The same thing works if you have a `.env` file in your project root. ```bash title=".env" SOME_ENV_VAR=FOO ``` It'll be loaded into `process.env` in your `sst.config.ts`. ```ts title="sst.config.ts" async run() { console.log(process.env.SOME_ENV_VAR); // FOO } ``` Or if you have a stage specific `.env.dev` file. ```bash title=".env.dev" SOME_ENV_VAR=BAR ``` And you run `sst deploy --stage dev`, it'll be loaded into `process.env` in your `sst.config.ts`. ```ts title="sst.config.ts" async run() { console.log(process.env.SOME_ENV_VAR); // BAR } ``` While the traditional approach works, we do not recommend it because it's both cumbersome and not secure. --- ### Www Src Content Docs Docs Iam Credentials (`www/src/content/docs/docs/iam-credentials.mdx`) --- title: IAM Credentials description: Configure the IAM credentials that's used to deploy your app. --- SST deploys your AWS resources using your AWS credentials. In this guide we'll look at how to set these credentials, the basic set of permissions it needs, and how to customize it. --- ## Credentials There are a couple of different ways to set the credentials that your app will use. The simplest is using a credentials file. However, if you're still figuring out how to configure your AWS account, we recommend [following our guide on it](/docs/aws-accounts). --- #### From a file By default, your AWS credentials are in a file: - `~/.aws/credentials` on Linux, Unix, macOS - `C:\Users\USER_NAME\.aws\credentials` on Windows If the credentials file does not exist on your machine. 1. Follow this to [create an IAM user](https://sst.dev/chapters/create-an-iam-user.html) 2. And then use this to [configure the credentials](https://sst.dev/chapters/configure-the-aws-cli.html) Below we'll look at how to customize the permissions that are granted to this user. --- Your credentials file might look like: ```bash title="~/.aws/credentials" [default] aws_access_key_id =Line secondary text color.
Line dimmed text color.
Normal secondary dimmed ## Code Let's test some code. ### Inline You can specify lines of code inline, `var a = "some variable name";`. And it can be a part of a paragraph as well. If `every` other `word` is `an` inline `code` block `what` does `that` do `for` us. Let's **`bold`** **some** words. Also add some links; a [`short`](/) and [`a long one`](/) and a [**`bold`**](/) one. ### Line ```js dateformat.i18n = require('./lang/' + l); ``` ### Blocks Let's add one line above. Let's add another line above. ```js // Javascript code with syntax highlighting. var fun = function lang(l) { dateformat.i18n = require('./lang/' + l); return true; }; ``` Let's add one line below. Let's add another line below. ### Frame Code blocks can be rendered inside a window-like frame. ```js title="my-test-file.js" console.log('Hello World!'); ``` #### Bash ```bash title="Create a new project" npm create sst ``` #### Bash Without Title ```bash npm create sst ``` ### Code Markers #### Lines Mark entire lines & line ranges using the `{ }` marker. ```js {3-4} function demo() { // This line is not highlighted // This line (#2) and the next one are highlighted return 'This is line #3 of this snippet'; } ``` #### Selections Mark selections of text using the `" "` marker or regular expressions. ```js "Individual terms" /Even.*supported/ // Individual terms can be highlighted, too function demo() { return 'Even regular expressions are supported'; } ``` #### Insert Deletes Mark text or lines as inserted or deleted with `ins` or `del`. ```js "return true;" ins="inserted" del="deleted" function demo() { console.log('These are inserted and deleted marker types'); // The return statement uses the default marker type return true; } ``` #### Diffs Combine syntax highlighting with `diff`-like syntax. ```diff lang="js" function thisIsJavaScript() { // This entire block gets highlighted as JavaScript, // and we can still add diff markers to it! - console.log('Old code to be removed') + console.log('New and shiny code!') } ``` ## Tabs You can display a tabbed interface using the `specifier [FormatSpecifierObject](#FormatSpecifierObject)
addend? number | string & boolean
FormatSpecifier](#FormatSpecifier)[] | null
isTrue boolean
isFalse? boolean
isAny? boolean
Object
prop1? boolean
true
prop2? “x86_64” | “arm_64”
prop3? [FormatSpecifier](#FormatSpecifier)[] | null
true
FormatSpecifier](#FormatSpecifier)[] | null
“x86_64” | “arm_64”
Object
resource1 string
resource2 [FormatSpecifier](#FormatSpecifier)
Object
[resource1](#) Output<Object>
[objectKey1](#) Object
[objectKey11](#) Object[]
[key111](#) boolean
[objectKey112](#) Object
[key1111](#) string
[key1112](#) string
[key2](#) boolean
[resource2](#) [FormatSpecifier](#FormatSpecifier)
Output<Object>
Object
Object[]
Object
string
“x86_64” | “arm_64”
Object
isTrue boolean
isFalse? boolean
isAny? boolean
undefined
Object
prop1? boolean
true
prop2? “x86_64” | “arm_64”
prop3? [FormatSpecifier](#FormatSpecifier)[] | null
true
undefined
Object
resource1? [FormatSpecifier](#FormatSpecifier) | (args: [FormatSpecifier](#FormatSpecifier) => [FormatSpecifier](#FormatSpecifier) | void)
resource1? [FormatSpecifier](#FormatSpecifier) | (args: [FormatSpecifier](#FormatSpecifier) => [FormatSpecifier](#FormatSpecifier) | void)
undefined
{subject.properties.id}.
app/page.tsx.
app/page.tsx.
Hit counter: {{ counter }}
``` --- #### Test your app Let's head over to `http://localhost:3000` in your browser and it'll show the current hit counter. You should see it increment every time you **refresh the page**. --- ### 5. Deploy your app To deploy our app we'll add a `Dockerfile`.