From aa725bf76fe66f8839ab72afa2af1bc288be9037 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 11:16:34 -0400 Subject: [PATCH 01/10] docs base url --- docusaurus.config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus.config.js b/docusaurus.config.js index c4446b8dd..dc9e362da 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -8,7 +8,7 @@ const config = { title: "Stellar Documentation", tagline: "Stellar is a self-serve distributed ledger that you can use as a backend to power all kinds of apps and services", url: "https://developers.stellar.org", - baseUrl: "/", + baseUrl: "/docs/", onBrokenLinks: "warn", onBrokenMarkdownLinks: "warn", favicon: "img/favicon-96x96.png", From 4c3b3c77d4321c25c9a607822298d9ccaac356e1 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 11:53:44 -0400 Subject: [PATCH 02/10] maybe? --- nginx.conf | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/nginx.conf b/nginx.conf index 94c33796b..8f6701c93 100644 --- a/nginx.conf +++ b/nginx.conf @@ -11,6 +11,10 @@ server { # location = / { # return 307 /docs/; # } + location /docs { + # rewrite "^/docs$" $scheme://$http_host/docs/ permanent; + rewrite "^/docs/(.*)$" /$1 last; + } location / { try_files $uri $uri/ /index.html =404; } From ef668ad8d8116b3d42b10c71033e768ab79bd416 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 11:57:52 -0400 Subject: [PATCH 03/10] pew pew --- nginx.conf | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/nginx.conf b/nginx.conf index 8f6701c93..90b6757e8 100644 --- a/nginx.conf +++ b/nginx.conf @@ -6,13 +6,10 @@ server { index index.html; error_page 404 /404.html; - server_name _; # all hostnames + server_name _; - # location = / { - # return 307 /docs/; - # } location /docs { - # rewrite "^/docs$" $scheme://$http_host/docs/ permanent; + rewrite "^/docs$" $scheme://$http_host/docs/ permanent; rewrite "^/docs/(.*)$" /$1 last; } location / { From 563e131dc3bf2f7be95245d74d1347c1dd08eff4 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 12:16:11 -0400 Subject: [PATCH 04/10] Update nginx.conf --- nginx.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 90b6757e8..381b77d10 100644 --- a/nginx.conf +++ b/nginx.conf @@ -13,7 +13,7 @@ server { rewrite "^/docs/(.*)$" /$1 last; } location / { - try_files $uri $uri/ /index.html =404; + try_files $uri $uri/ $uri/index.html /index.html =404; } location /index.html { add_header 'Cache-Control' 'no-store' always; From 422086f51c7f6afa810b1023ce60e372be0d9c10 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 13:46:50 -0400 Subject: [PATCH 05/10] hard code all /api links to developers.stellar.org --- .../setting-up-test-server.mdx | 2 +- docs/glossary/fee-bumps.mdx | 2 +- docs/glossary/fees.mdx | 2 +- docs/glossary/muxed-accounts.mdx | 2 +- docs/glossary/operations.mdx | 2 +- docs/glossary/transactions.mdx | 2 +- docs/run-core-node/index.mdx | 2 +- docs/software-and-sdks/index.mdx | 2 +- docs/start/introduction.mdx | 2 +- docs/start/stellar-stack.mdx | 2 +- docs/tutorials/follow-received-payments.mdx | 4 ++-- docs/tutorials/handling-errors.mdx | 8 ++++---- docs/tutorials/send-and-receive-payments.mdx | 2 +- 13 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx b/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx index 1961f8120..c28bfb7b2 100644 --- a/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx +++ b/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx @@ -314,4 +314,4 @@ Receving anchors (**RA**s) must be able to detect and match incoming Stellar pat - Polling: this option consists of periodically fetching the transactions submitted _after_ an already-seen transaction's `paging_id` that should be updated after each iteration. - Streaming: this option consists of maintaining a persistent process that streams incoming transactions from the anchored asset's distribution account, which allows detection and transaction matching in close to real time. -For more information on path payment transactions, checkout the [operation definition](https://developers.stellar.org/api/resources/operations/object/path-payment-strict-receive/). +For more information on path payment transactions, checkout the [operation definition](https://developers.stellar.org/api/resources/operations/object/path-payment-strict-receive/). \ No newline at end of file diff --git a/docs/glossary/fee-bumps.mdx b/docs/glossary/fee-bumps.mdx index ca29df78b..c2358a04e 100644 --- a/docs/glossary/fee-bumps.mdx +++ b/docs/glossary/fee-bumps.mdx @@ -2,7 +2,7 @@ title: Fee-Bump Transactions --- -A fee-bump transaction enables any account to pay the fee for an existing [transaction](./transactions.mdx) without the need to re-sign the existing transaction or manage sequence numbers. They're useful if you need to increase the fee on a pre-signed transaction, or if you want to build a service that covers user fees. Like a regular transaction, these are submitted to the [`/transactions` endpoint](/api/resources/transactions/). _Unlike_ a regular transaction, however, which contains 1-100 [operations](./operations.mdx), a fee-bump transaction contains a single [transaction envelope](./transactions.mdx/#transaction-envelopes). +A fee-bump transaction enables any account to pay the fee for an existing [transaction](./transactions.mdx) without the need to re-sign the existing transaction or manage sequence numbers. They're useful if you need to increase the fee on a pre-signed transaction, or if you want to build a service that covers user fees. Like a regular transaction, these are submitted to the [`/transactions` endpoint](https://developers.stellar.org/api/resources/transactions/). _Unlike_ a regular transaction, however, which contains 1-100 [operations](./operations.mdx), a fee-bump transaction contains a single [transaction envelope](./transactions.mdx/#transaction-envelopes). ## Fee-Bump Transaction Attributes diff --git a/docs/glossary/fees.mdx b/docs/glossary/fees.mdx index e65fb027d..a77d67bb6 100644 --- a/docs/glossary/fees.mdx +++ b/docs/glossary/fees.mdx @@ -37,7 +37,7 @@ When network activity is below capacity, you pay the network minimum, which is c When the number of operations submitted to a ledger exceeds network capacity (**currently 1,000 ops/ledger**), the network enters surge pricing mode, which uses market dynamics to decide which submissions are included. Essentially, submissions that offer a higher fee per operation make it onto the ledger first. -If there’s a tie — in other words multiple transactions that offer the same base fee are competing for the same limited space in the ledger — the transactions are (pseudo-randomly) shuffled, and transactions at the top of the heap make the ledger. The rest of the transactions, the ones that didn’t make the cut, are pushed on to the next ledger, or discarded if they’ve been waiting for too long. If your transaction is discarded, Horizon will return a [timeout error](/api/errors/http-status-codes/horizon-specific/). For more information, see [transaction life cycle](./transactions.mdx#life-cycle-of-a-transaction). +If there’s a tie — in other words multiple transactions that offer the same base fee are competing for the same limited space in the ledger — the transactions are (pseudo-randomly) shuffled, and transactions at the top of the heap make the ledger. The rest of the transactions, the ones that didn’t make the cut, are pushed on to the next ledger, or discarded if they’ve been waiting for too long. If your transaction is discarded, Horizon will return a [timeout error](https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/). For more information, see [transaction life cycle](./transactions.mdx#life-cycle-of-a-transaction). The goal of the transaction pricing specification, which you can read in full [here](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md), is to maximize network throughput while minimizing transaction fees. diff --git a/docs/glossary/muxed-accounts.mdx b/docs/glossary/muxed-accounts.mdx index 0b9562c54..35dd6b7c5 100644 --- a/docs/glossary/muxed-accounts.mdx +++ b/docs/glossary/muxed-accounts.mdx @@ -36,7 +36,7 @@ There are many other benefits to embedding this abstraction into the protocol: It's crucial to understand that this feature is intended to be a high-level abstraction, merely embedded into the protocol for convenience and standardization. There's no validation on IDs: **as far as the Stellar Network is concerned, all of the [supported operations][supported-ops] operate exactly as if you did _not_ used a muxed account**. For example, if you make two payments from two muxed accounts that share an underlying Stellar account (i.e. muxed accounts with the same underlying `G...` account but two different IDs), this is _exactly the same_ as that single Stellar account sending two payments, as far as the ledger is concerned. -Even though only the underlying `G...` account _truly_ exists in the Stellar ledger, the [Horizon API](/api/introduction/) will make some effort to interpret and track the muxed accounts responsible for certain actions. +Even though only the underlying `G...` account _truly_ exists in the Stellar ledger, the [Horizon API](https://developers.stellar.org/api/introduction/) will make some effort to interpret and track the muxed accounts responsible for certain actions. Muxed account support is embedded into the SDKs. This means that you may see muxed addresses appear when parsing any of the fields that support them, so you should be ready to handle them. Refer to your SDK's documentation for details; for example, [v7.0.0](https://github.com/stellar/js-stellar-base/releases/tag/v7.0.0) of the JavaScript SDK library `stellar-base` describes all of the fields and functions that relate to muxed accounts. diff --git a/docs/glossary/operations.mdx b/docs/glossary/operations.mdx index deac200fa..18c87e752 100644 --- a/docs/glossary/operations.mdx +++ b/docs/glossary/operations.mdx @@ -42,4 +42,4 @@ For more details on this process, see the [lifecycle of a transaction](./transac For each operation, there is a matching result type. In the case of success, this result allows users to gather information about the effects of the operation. In the case of failure, it allows users to learn more about the error. -There are some generic errors associated with operations. For example, any operation that creates a subentry, such as `ChangeTrust` and `ManageData`, can fail with `opTOO_MANY_SUBENTRIES`. See [operations](/api/errors/result-codes/operations/) in the API reference for more information. +There are some generic errors associated with operations. For example, any operation that creates a subentry, such as `ChangeTrust` and `ManageData`, can fail with `opTOO_MANY_SUBENTRIES`. See [operations](https://developers.stellar.org/api/errors/result-codes/operations/) in the API reference for more information. diff --git a/docs/glossary/transactions.mdx b/docs/glossary/transactions.mdx index 721347859..3fadf7a8d 100644 --- a/docs/glossary/transactions.mdx +++ b/docs/glossary/transactions.mdx @@ -114,7 +114,7 @@ To determine if a transaction is valid, many checks take place over the course o 1. **Signing (Transaction Signers)**: Once the transaction is completely filled out, the transaction is formed into a transaction envelope, which contains the transaction itself and a list of signers. All the required signatures must be collected and added to the transaction envelope's list of signers. Commonly it's just the signature of the account doing the transaction, but more complicated setups can require collecting [signatures from multiple parties](./multisig.mdx). -1. **Submitting (Transaction Submitter)**: After signing, the transaction must be valid and can now be submitted to the Stellar network. If the transaction is invalid, it will be immediately rejected by stellar-core based on [the validity rules of a transaction](#validity-of-a-transaction), the account's sequence number will not be incremented, and no fee will be consumed from the source account. Multiple transactions for the same account can be submitted, provided each of their sequence numbers are off by one. If they are all valid, Stellar Core will craft a transaction set with each of those transactions applied in sequence number order. Transactions are typically submitted using [Horizon](/api/introduction/), but you can also submit the transaction directly to an instance of [Stellar Core](..//run-core-node/index.mdx). +1. **Submitting (Transaction Submitter)**: After signing, the transaction must be valid and can now be submitted to the Stellar network. If the transaction is invalid, it will be immediately rejected by stellar-core based on [the validity rules of a transaction](#validity-of-a-transaction), the account's sequence number will not be incremented, and no fee will be consumed from the source account. Multiple transactions for the same account can be submitted, provided each of their sequence numbers are off by one. If they are all valid, Stellar Core will craft a transaction set with each of those transactions applied in sequence number order. Transactions are typically submitted using [Horizon](https://developers.stellar.org/api/introduction/), but you can also submit the transaction directly to an instance of [Stellar Core](..//run-core-node/index.mdx). 1. **Propagating (Validator)**: Once Stellar Core has determined that a transaction is valid, it will then propagate the transaction to all of the other servers to which it's connected. In this way, a valid transaction is flooded to the entire Stellar network. diff --git a/docs/run-core-node/index.mdx b/docs/run-core-node/index.mdx index 6ccfa9275..449c0cbd3 100644 --- a/docs/run-core-node/index.mdx +++ b/docs/run-core-node/index.mdx @@ -7,7 +7,7 @@ import { Alert } from "@site/src/components/Alert"; Stellar is a peer-to-peer network made up of nodes, which are computers that keep a common distributed [ledger](../glossary/ledger.mdx), and that communicate to validate and add [transactions](../glossary/transactions.mdx) to it. Nodes use a program called Stellar Core — an implementation of the [Stellar Consensus Protocol](../glossary/scp.mdx) — to stay in sync as they work to agree on the validity of transaction sets and to apply them to the ledger. Generally, nodes reach consensus, apply a transaction set, and update the ledger every 3-5 seconds. -You don’t need to run a node to build on Stellar: you can start developing with your [SDK of choice](../software-and-sdks/index.mdx), and use public instances of Horizon to query the ledger and submit transactions right away. In fact, the Stellar Development Foundation offers two public instances of Horizon — one for the public network and one for the testnet — which you can read more about in our [API reference docs](/api/introduction/). [Lobstr](https://horizon.stellar.lobstr.co), [Public Node](https://horizon.publicnode.org/), and [Coinqvest](https://horizon.stellar.coinqvest.com) also offer public Horizon instances. +You don’t need to run a node to build on Stellar: you can start developing with your [SDK of choice](../software-and-sdks/index.mdx), and use public instances of Horizon to query the ledger and submit transactions right away. In fact, the Stellar Development Foundation offers two public instances of Horizon — one for the public network and one for the testnet — which you can read more about in our [API reference docs](https://developers.stellar.org/api/introduction/). [Lobstr](https://horizon.stellar.lobstr.co), [Public Node](https://horizon.publicnode.org/), and [Coinqvest](https://horizon.stellar.coinqvest.com) also offer public Horizon instances. Even if you _do_ want to run your [own instance of Horizon](../run-api-server/index.mdx), it bundles its own version of Core and manages its lifetime entirely, so there's no need to run a standalone instance. diff --git a/docs/software-and-sdks/index.mdx b/docs/software-and-sdks/index.mdx index c6558c694..4b66cd582 100644 --- a/docs/software-and-sdks/index.mdx +++ b/docs/software-and-sdks/index.mdx @@ -7,7 +7,7 @@ sidebar_position: 0 There are two key pieces of network software: Stellar Core, which tracks and adds transaction sets to the ledger, and Horizon, an API that allows programmatic access to submit transactions and query network data. To find out more about how they work together, visit the description of the [Stellar Stack](../start/stellar-stack.mdx). -You do not have to run a Stellar Core node or Horizon instance to build on Stellar: you can start developing in your language of choice by installing one of the [Stellar SDKs](#sdks) below, and interacting with a public Horizon instance. To find out more about how to interact with Horizon, check out the [API Reference](/api/introduction/) section, which chronicles every Horizon endpoint, resource, aggregation, and error. +You do not have to run a Stellar Core node or Horizon instance to build on Stellar: you can start developing in your language of choice by installing one of the [Stellar SDKs](#sdks) below, and interacting with a public Horizon instance. To find out more about how to interact with Horizon, check out the [API Reference](https://developers.stellar.org/api/introduction/) section, which chronicles every Horizon endpoint, resource, aggregation, and error. ### Stellar Core diff --git a/docs/start/introduction.mdx b/docs/start/introduction.mdx index c04dd1929..0316f2702 100644 --- a/docs/start/introduction.mdx +++ b/docs/start/introduction.mdx @@ -29,7 +29,7 @@ If you're new to Stellar, you may want to start by getting a high-level understa Once you have a high-level understanding of Stellar, you can start building right away, and the subsequent sections of these docs will focus on how to do that. You don't have to run your own Stellar Core node to develop on Stellar — several organizations including the Stellar Development Foundation offer public-access API endpoints that allow you to submit transactions and query the ledger — so you can focus on building your product before committing to setting up network infrastructure. -If you are new, you may want to start with the early [Tutorials](../tutorials/create-account.mdx) to familiarize yourself with some of the building blocks of Stellar. You should also investigate the [SDKs](../software-and-sdks/index.mdx) designed to make developing in your language of choice easy, and familiarize yourself with the canonical [List of Operations](../start/list-of-operations.mdx), which documents everything you can do with Stellar — along with parameters and error codes — and links to the relevant documentation for key SDKs. Finally, you may want to explore the [API Reference](/api/introduction/) documentation, which details every resource, aggregation, and error provided by Horizon, the Stellar API. +If you are new, you may want to start with the early [Tutorials](../tutorials/create-account.mdx) to familiarize yourself with some of the building blocks of Stellar. You should also investigate the [SDKs](../software-and-sdks/index.mdx) designed to make developing in your language of choice easy, and familiarize yourself with the canonical [List of Operations](../start/list-of-operations.mdx), which documents everything you can do with Stellar — along with parameters and error codes — and links to the relevant documentation for key SDKs. Finally, you may want to explore the [API Reference](https://developers.stellar.org/api/introduction/) documentation, which details every resource, aggregation, and error provided by Horizon, the Stellar API. ## Developer Channels diff --git a/docs/start/stellar-stack.mdx b/docs/start/stellar-stack.mdx index c55039505..87e207b8a 100644 --- a/docs/start/stellar-stack.mdx +++ b/docs/start/stellar-stack.mdx @@ -15,7 +15,7 @@ SDKs make it easy to craft code and handle network queries and transaction submi ## API: Horizon -[Horizon](../run-api-server/index.mdx) is a RESTful HTTP API server that provides a straightforward way to submit transactions, check accounts, and subscribe to events. Because it’s HTTP, you can communicate with Horizon using an SDK, but you can also use your web browser, or simple command line tools like cURL. Everything there is to know about Horizon is documented in the [API Reference](/api/introduction/) section of the docs. +[Horizon](../run-api-server/index.mdx) is a RESTful HTTP API server that provides a straightforward way to submit transactions, check accounts, and subscribe to events. Because it’s HTTP, you can communicate with Horizon using an SDK, but you can also use your web browser, or simple command line tools like cURL. Everything there is to know about Horizon is documented in the [API Reference](https://developers.stellar.org/api/introduction/) section of the docs. At the moment, Horizon requires access to Stellar Core's database to function properly — so every Horizon instance connects to a Stellar Core node — but we are increasing its independence from Stellar Core, and soon developers will be able deploy the API without having to run their own node. diff --git a/docs/tutorials/follow-received-payments.mdx b/docs/tutorials/follow-received-payments.mdx index ddd65c86c..34bd2562a 100644 --- a/docs/tutorials/follow-received-payments.mdx +++ b/docs/tutorials/follow-received-payments.mdx @@ -111,7 +111,7 @@ After a few seconds, the Stellar network will perform consensus, close the ledge ## Following payments using `curl` -To follow new payments connected to your account you simply need to send the `Accept: text/event-stream` header to the [/payments](/api/resources/operations/object/payment/) endpoint. +To follow new payments connected to your account you simply need to send the `Accept: text/event-stream` header to the [/payments](https://developers.stellar.org/api/resources/operations/object/payment/) endpoint. @@ -147,7 +147,7 @@ data: {"_links":{"effects":{"href":"/operations/713226564145153/effects/{?cursor -Every time you receive a new payment you will get a new row of data. Payments is not the only endpoint that supports streaming. You can also stream transactions [/transactions](/api/resources/transactions/) and operations [/operations](/api/resources/operations/). +Every time you receive a new payment you will get a new row of data. Payments is not the only endpoint that supports streaming. You can also stream transactions [/transactions](https://developers.stellar.org/api/resources/transactions/) and operations [/operations](https://developers.stellar.org/api/resources/operations/). ## Following payments using `EventStream` diff --git a/docs/tutorials/handling-errors.mdx b/docs/tutorials/handling-errors.mdx index f5bae5bef..48a8e78d0 100644 --- a/docs/tutorials/handling-errors.mdx +++ b/docs/tutorials/handling-errors.mdx @@ -29,7 +29,7 @@ Some errors cannot be overcome without changes to the request itself. #### Queries -Many of the `GET` requests have specific parameter requirements, and while the [SDKs](../software-and-sdks/) can help enforce them, you can still pass invalid arguments (e.g. an asset string that isn't [SEP-11 conformant](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md#asset)) that error out every time. In this scenario, there's nothing you can do aside from following the [API specification](/api) precisely. The `extras` field of the error response will often clue you in on where to look and what to look for: +Many of the `GET` requests have specific parameter requirements, and while the [SDKs](../software-and-sdks/) can help enforce them, you can still pass invalid arguments (e.g. an asset string that isn't [SEP-11 conformant](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md#asset)) that error out every time. In this scenario, there's nothing you can do aside from following the [API specification](https://developers.stellar.org/api) precisely. The `extras` field of the error response will often clue you in on where to look and what to look for: @@ -47,7 +47,7 @@ Note that the SDKs make it a point to distinguish an **invalid request** (as abo #### Transaction Submissions -Certain transaction submission failures also need adjustments to succeed. If the XDR is malformed or the transaction is somehow otherwise invalid, you'll encounter a `400 Bad Request` (for example, when excluding a source account as seen in the [API reference example](/api/errors/response/)). Both transactions and their requisite operations can easily be malformed: look at the `extras.result_codes` field for details and cross-reference them with the appropriate [Result Codes documentation](/api/errors/result-codes/) to determine specifics. +Certain transaction submission failures also need adjustments to succeed. If the XDR is malformed or the transaction is somehow otherwise invalid, you'll encounter a `400 Bad Request` (for example, when excluding a source account as seen in the [API reference example](https://developers.stellar.org/api/errors/response/)). Both transactions and their requisite operations can easily be malformed: look at the `extras.result_codes` field for details and cross-reference them with the appropriate [Result Codes documentation](https://developers.stellar.org/api/errors/result-codes/) to determine specifics. Another class of safe adjustments involves transaction fees: if you get a `tx_insufficient_fee` error, it's worth reading the [later section](#insufficient-fees-and-surge-pricing) to adjust your fee-paying strategy. @@ -240,8 +240,8 @@ Note an [important stipulation](https://developers.stellar.org/docs/glossary/fee > If you submit two distinct transactions with the same source account and sequence number, and the second transaction is a fee-bump transaction, the second transaction will be included in the transaction queue in place of the first transaction if and only if **the fee bid of the second transaction is at least 10x the fee bid of the first transaction**. -This value can typically be found in the `fee_charged` field of the [transaction response](/api/resources/transactions/object/) under the `tx_insufficient_fee` error case. +This value can typically be found in the `fee_charged` field of the [transaction response](https://developers.stellar.org/api/resources/transactions/object/) under the `tx_insufficient_fee` error case. ### Rate Limiting -If you're using the SDF's public Horizon instance, you may get a `429 Too Many Requests` error when exceeding the [rate limits](/api/introduction/rate-limiting/). If you're encountering this frequently, it may be time to [deploy your own](../run-api-server/) Horizon instance! +If you're using the SDF's public Horizon instance, you may get a `429 Too Many Requests` error when exceeding the [rate limits](https://developers.stellar.org/api/introduction/rate-limiting/). If you're encountering this frequently, it may be time to [deploy your own](../run-api-server/) Horizon instance! diff --git a/docs/tutorials/send-and-receive-payments.mdx b/docs/tutorials/send-and-receive-payments.mdx index 8fdf31dfa..625be54c1 100644 --- a/docs/tutorials/send-and-receive-payments.mdx +++ b/docs/tutorials/send-and-receive-payments.mdx @@ -24,7 +24,7 @@ In the following code samples, proper error checking is omitted for brevity. How ## Send a Payment -Stellar stores and communicates transaction data in a binary format called [XDR](../glossary/xdr.mdx), which is optimized for network performance but unreadable to the human eye. Luckily, [Horizon](/api/introduction/), the Stellar API, and the [Stellar SDKs](../software-and-sdks/index.mdx) convert XDRs into friendlier formats. Here’s how you might send 10 lumens to an account: +Stellar stores and communicates transaction data in a binary format called [XDR](../glossary/xdr.mdx), which is optimized for network performance but unreadable to the human eye. Luckily, [Horizon](https://developers.stellar.org/api/introduction/), the Stellar API, and the [Stellar SDKs](../software-and-sdks/index.mdx) convert XDRs into friendlier formats. Here’s how you might send 10 lumens to an account: From e84a6a97345252873a416a100fc6ec6df2067ef2 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 13:55:30 -0400 Subject: [PATCH 06/10] Update nginx.conf --- nginx.conf | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 381b77d10..4f0a86e20 100644 --- a/nginx.conf +++ b/nginx.conf @@ -9,7 +9,6 @@ server { server_name _; location /docs { - rewrite "^/docs$" $scheme://$http_host/docs/ permanent; rewrite "^/docs/(.*)$" /$1 last; } location / { @@ -21,6 +20,9 @@ server { location /assets/ { try_files $uri $uri/ =404; } + location /img/ { + try_files $uri $uri/ =404; + } location /404.html { add_header 'Cache-Control' 'no-store' always; } From 21b954233e57d0d1e21ecacbae8d797ca9d995c9 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 13:58:10 -0400 Subject: [PATCH 07/10] tiny lint tweak --- .../setting-up-test-server.mdx | 2 +- nginx.conf | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx b/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx index c28bfb7b2..1961f8120 100644 --- a/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx +++ b/docs/anchoring-assets/enabling-cross-border-payments/setting-up-test-server.mdx @@ -314,4 +314,4 @@ Receving anchors (**RA**s) must be able to detect and match incoming Stellar pat - Polling: this option consists of periodically fetching the transactions submitted _after_ an already-seen transaction's `paging_id` that should be updated after each iteration. - Streaming: this option consists of maintaining a persistent process that streams incoming transactions from the anchored asset's distribution account, which allows detection and transaction matching in close to real time. -For more information on path payment transactions, checkout the [operation definition](https://developers.stellar.org/api/resources/operations/object/path-payment-strict-receive/). \ No newline at end of file +For more information on path payment transactions, checkout the [operation definition](https://developers.stellar.org/api/resources/operations/object/path-payment-strict-receive/). diff --git a/nginx.conf b/nginx.conf index 4f0a86e20..548bbc302 100644 --- a/nginx.conf +++ b/nginx.conf @@ -14,15 +14,15 @@ server { location / { try_files $uri $uri/ $uri/index.html /index.html =404; } - location /index.html { - add_header 'Cache-Control' 'no-store' always; - } location /assets/ { try_files $uri $uri/ =404; } location /img/ { try_files $uri $uri/ =404; } + location /index.html { + add_header 'Cache-Control' 'no-store' always; + } location /404.html { add_header 'Cache-Control' 'no-store' always; } From d53742e9679866dd8440f7cc6bdc0a26b912d148 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 14:10:29 -0400 Subject: [PATCH 08/10] not really sure but maybe --- nginx.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 548bbc302..7882e9f0f 100644 --- a/nginx.conf +++ b/nginx.conf @@ -12,7 +12,7 @@ server { rewrite "^/docs/(.*)$" /$1 last; } location / { - try_files $uri $uri/ $uri/index.html /index.html =404; + try_files $uri $uri/ =404; } location /assets/ { try_files $uri $uri/ =404; From 8307ebde05788f3dabc3799586d0ae2d39194dd5 Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 15:44:39 -0400 Subject: [PATCH 09/10] Update nginx.conf --- nginx.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nginx.conf b/nginx.conf index 7882e9f0f..6f02e19e1 100644 --- a/nginx.conf +++ b/nginx.conf @@ -9,10 +9,10 @@ server { server_name _; location /docs { - rewrite "^/docs/(.*)$" /$1 last; + rewrite ^/docs/(.*)$ /$1 last; } location / { - try_files $uri $uri/ =404; + try_files $uri $uri/ $uri/index.html /index.html =404; } location /assets/ { try_files $uri $uri/ =404; From 167e9ce35ba4c50f60f9f7722dbb1abdd613402f Mon Sep 17 00:00:00 2001 From: Tyler van der Hoeven Date: Thu, 11 Aug 2022 15:51:33 -0400 Subject: [PATCH 10/10] Update nginx.conf --- nginx.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nginx.conf b/nginx.conf index 6f02e19e1..d2eda4dc2 100644 --- a/nginx.conf +++ b/nginx.conf @@ -12,7 +12,7 @@ server { rewrite ^/docs/(.*)$ /$1 last; } location / { - try_files $uri $uri/ $uri/index.html /index.html =404; + try_files $uri $uri/index.html $uri/ =404; } location /assets/ { try_files $uri $uri/ =404;