taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

updating docs

Browse Source
This commit is contained in:
ainsley
2019-05-30 12:43:58 -05:00
parent 0ce229b29d
commit 7765f4b86a
162 changed files with 426 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/nats_server/accounts.html
View File

@@ -2354,14 +2354,14 @@
<p>While the name <em>account</em> implies one or more users, it is much simpler and enlightening to think of one account as a messaging container for one application. Users in the account are simply the minimum number of services that must work together to provide some functionality.
In simpler terms, more accounts with few (even one) clients is a better design topology than a large account with many users with complex authorization configuration.</p>
</blockquote>
<h2 id="exporting-and-importing"><a name="exporting-and-importing" class="plugin-anchor" href="#exporting-and-importing"><i class="fa fa-link" aria-hidden="true"></i></a>Exporting and Importing</h2>
<h3 id="exporting-and-importing"><a name="exporting-and-importing" class="plugin-anchor" href="#exporting-and-importing"><i class="fa fa-link" aria-hidden="true"></i></a>Exporting and Importing</h3>
<p>Messaging exchange between different accounts is enabled by <em>exporting</em> streams and services from one account and <em>importing</em> them into another. Each account controls what is exported and imported.</p>
<p>The <code>exports</code> configuration list enable you to define the services and streams that others can import. Services and streams are expressed as an <a href="#export-configuration-map">Export configuration map</a>.</p>
<h3 id="streams"><a name="streams" class="plugin-anchor" href="#streams"><i class="fa fa-link" aria-hidden="true"></i></a>Streams</h3>
<p>Streams are messages your application publishes. Importing applications won&apos;t be able to make requests from your applications but will be able to consume messages you generate.</p>
<h3 id="services"><a name="services" class="plugin-anchor" href="#services"><i class="fa fa-link" aria-hidden="true"></i></a>Services</h3>
<p>Services are messages your application can consume and act on, enabling other accounts to make requests that are fulfilled by your account.</p>
<h2 id="export-configuration-map"><a name="export-configuration-map" class="plugin-anchor" href="#export-configuration-map"><i class="fa fa-link" aria-hidden="true"></i></a>Export Configuration Map</h2>
<h3 id="export-configuration-map"><a name="export-configuration-map" class="plugin-anchor" href="#export-configuration-map"><i class="fa fa-link" aria-hidden="true"></i></a>Export Configuration Map</h3>
<p>The export configuration map binds a subject for use as a <code>service</code> or <code>stream</code> and optionally defines specific accounts that can import the stream or service. Here are the supported configuration properties:</p>
<table>
<thead>
@@ -2427,7 +2427,7 @@ In simpler terms, more accounts with few (even one) clients is a better design t
</tr>
</tbody>
</table>
<h2 id="import-configuration-map"><a name="import-configuration-map" class="plugin-anchor" href="#import-configuration-map"><i class="fa fa-link" aria-hidden="true"></i></a>Import Configuration Map</h2>
<h3 id="import-configuration-map"><a name="import-configuration-map" class="plugin-anchor" href="#import-configuration-map"><i class="fa fa-link" aria-hidden="true"></i></a>Import Configuration Map</h3>
<p>An import enables an account to consume streams published by another account or make requests to services implemented by another account. All imports require a corresponding export on the exporting account. Accounts cannot do self-imports.</p>
<table>
<thead>
@@ -2548,7 +2548,7 @@ In simpler terms, more accounts with few (even one) clients is a better design t
<script>
var gitbook = gitbook || [];
gitbook.push(function() {
gitbook.page.hasChanged({"page":{"title":"Accounts","level":"4.5.1.2.5","depth":4,"next":{"title":"JWTs","level":"4.5.1.2.6","depth":4,"path":"nats_server/jwt_auth.md","ref":"nats_server/jwt_auth.md","articles":[]},"previous":{"title":"NKeys","level":"4.5.1.2.4","depth":4,"path":"nats_server/nkey_auth.md","ref":"nats_server/nkey_auth.md","articles":[]},"dir":"ltr"},"config":{"plugins":["prism","-highlight","include-html","toggle-chapters","anchors"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"prism":{"lang":{"ascii":"markup","text":"markup"}},"search":{},"lunr":{"maxIndexSize":1000000,"ignoreSpecialCharacters":false},"include-html":{},"fontsettings":{"theme":"white","family":"sans","size":2},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false},"anchors":{},"toggle-chapters":{}},"theme":"default","author":"The NATS Maintainers","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{},"title":"NATS","gitbook":"*","description":"Administrative, developer and conceptual documentation for the NATS messaging system."},"file":{"path":"nats_server/accounts.md","mtime":"2019-05-29T16:43:54.846Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2019-05-29T16:45:48.381Z"},"basePath":"..","book":{"language":""}});
gitbook.page.hasChanged({"page":{"title":"Accounts","level":"4.5.1.2.5","depth":4,"next":{"title":"JWTs","level":"4.5.1.2.6","depth":4,"path":"nats_server/jwt_auth.md","ref":"nats_server/jwt_auth.md","articles":[]},"previous":{"title":"NKeys","level":"4.5.1.2.4","depth":4,"path":"nats_server/nkey_auth.md","ref":"nats_server/nkey_auth.md","articles":[]},"dir":"ltr"},"config":{"plugins":["prism","-highlight","include-html","toggle-chapters","anchors"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"prism":{"lang":{"ascii":"markup","text":"markup"}},"search":{},"lunr":{"maxIndexSize":1000000,"ignoreSpecialCharacters":false},"include-html":{},"fontsettings":{"theme":"white","family":"sans","size":2},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false},"anchors":{},"toggle-chapters":{}},"theme":"default","author":"The NATS Maintainers","pdf":{"pageNumbers":true,"fontSize":12,"fontFamily":"Arial","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":56,"bottom":56}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{},"title":"NATS","gitbook":"*","description":"Administrative, developer and conceptual documentation for the NATS messaging system."},"file":{"path":"nats_server/accounts.md","mtime":"2019-05-30T17:42:13.286Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2019-05-30T17:42:48.393Z"},"basePath":"..","book":{"language":""}});
});
</script>
</div>