Documents languagepack uses cases
Change-Id: I4197774cc88be40f3b9664806ff5f226fd9a0511 Closes-Bug: #1325590
This commit is contained in:
parent
7bf6d13389
commit
1ae2aa3c80
|
@ -17,6 +17,17 @@ Overview
|
||||||
$ solum app show <UUID/Name>
|
$ solum app show <UUID/Name>
|
||||||
$ curl <application_uri>
|
$ curl <application_uri>
|
||||||
|
|
||||||
|
Use Cases
|
||||||
|
~~~~~~~~~
|
||||||
|
A languagepack must exist in Solum, as every application deployed
|
||||||
|
with Solum requires an association to a languagepack to run (even
|
||||||
|
if the languagepack only implements a no-op). Languagepacks can be
|
||||||
|
added to Solum in the following ways:
|
||||||
|
|
||||||
|
1. Solum comes with pre-existing languagepacks
|
||||||
|
2. Solum System Operator creates and adds languagepack(s) available for all users
|
||||||
|
3. Solum User creates and adds languagepack(s) available only to that user
|
||||||
|
|
||||||
Vagrant Demo Environment
|
Vagrant Demo Environment
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue