Found 744 results for "docker configuration support"
The search executed in 0.003676584 seconds. That's fast.
Gitana / 4.0 / Data Engine / Aspects / Auto NarrateAuto Narrate This section describes features that are coming in 4.0 QName: f:auto-narrate With this feature in place, a content instance will automatically have the text from either an attachment or a property narrated using text-to-speech. The generated audio file will be stored back onto the node as an audio attachment (typically in MP3 format). To use this service, you will first need to set up a Narration Service. The service can either be configured as the default Narration Service for your
Score: 0.798027
|
|
Gitana / 4.0 / Forms / Fields / Editor FieldEditor Field The editor field. The editor field uses the Cloud 9 ACE Editor plugin to render an inline editor that supports a wide array of textual content types. The editor provides a number of very powerful features and allows for the creation and modification of markup and code such as HTML, JavaScript, Java and other languages. Properties Title Editor Description Provides an automatically formatted and configurable input for entering currency amounts. Field Type editor Base Field Type text S
Score: 0.798027
|
|
Enterprise Access Policies in Gitana 4.0 (Part 2)In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can
Score: 0.7978413
|
|
Gitana / 3.2 / Guide / Guide / Features / RelatorRelator QName: f:relator This feature is applied internally to relator associations within the content graph that connect two nodes via a relator property. There is no need to apply this feature manually. For information on relator properties, please see relator properties. Configuration
Score: 0.7958412
|
|
Gitana / 3.2 / Guide / Guide / Features / RenditionRendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }
Score: 0.7958412
|
|
Gitana / 4.0 / Data Engine / Aspects / RelatorRelator QName: f:relator This feature is applied internally to relator associations within the content graph that connect two nodes via a relator property. There is no need to apply this feature manually. For information on relator properties, please see relator properties. Configuration
Score: 0.7958412
|
|
Gitana / 4.0 / Data Engine / Aspects / RenditionRendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }
Score: 0.7958412
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / ApplicationApplication An application is a data store where you can store configuration related to your mobile, touch or web application. Applications are general purpose for your data store and you can use them as you would like. Cloud CMS provides a few foundation objects for your applications including objects to manage user registration (sign up, confirmation emails, etc), general email dispatching and settings for page layout and module configuration. ## Configuration As with all data stores, this dat
Score: 0.7953086
|
|
Gitana / 4.0 / Data Engine / API / Data Types / ApplicationApplication An application is a data store where you can store configuration related to your mobile, touch or web application. Applications are general purpose for your data store and you can use them as you would like. Cloud CMS provides a few foundation objects for your applications including objects to manage user registration (sign up, confirmation emails, etc), general email dispatching and settings for page layout and module configuration. ## Configuration As with all data stores, this dat
Score: 0.7953086
|
|
Gitana / 3.2 / Guide / Guide / Features / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 0.793496
|
|
Gitana / 4.0 / Data Engine / Aspects / BehaviorBehavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }
Score: 0.793496
|
|
Gitana / 3.2 / Guide / Guide / Application Server / URL Addressability / Login and LogoutLogin and Logout The Application Server provides login and logout support for development teams that wish to store their users and user account information inside of Cloud CMS Domains. Cloud CMS Domains are LDAP-like storage facilities for users, groups, group memberships and more. They're not required, technically, since the Application Server can accommodate other storage facilities (such as LDAP itself), but they're incredibly useful if you can use them since they let you take advantage of us
Score: 0.79280865
|
|
Gitana / 4.0 / Developers / Application Server / URL Addressability / Login and LogoutLogin and Logout The Application Server provides login and logout support for development teams that wish to store their users and user account information inside of Cloud CMS Domains. Cloud CMS Domains are LDAP-like storage facilities for users, groups, group memberships and more. They're not required, technically, since the Application Server can accommodate other storage facilities (such as LDAP itself), but they're incredibly useful if you can use them since they let you take advantage of us
Score: 0.79280865
|
|
Automatic Extraction from AttachmentsWhen you upload files into Cloud CMS all kinds of interesting things happen. For example, Cloud CMS automatically indexes your files for full-text search. All of the textual content is discovered and made available so your editorial teams can instantly search and find things after uploading. Did you know that Cloud CMS can also automatically extract metadata about uploaded files and make that information available? This is done via the Cloud CMS f:extractable feature. When you upload files, Clou
Score: 0.79280865
|
|
Bulk ImportWhy is there a need for Bulk Import for existing content into a CMS? Content is extremely valuable and expensive to recreate. It’s too valuable to lose and recreating it manually can be a daunting prospect. Your existing content is an important concern at the start of any CMS project – how to migrate content and the related costs is a very important consideration. If there is content that does need to be imported into the CMS then you will need to have a robust repeatable automated process such
Score: 0.79280865
|
|
Gitana / 3.2 / Guide / Guide / Actions / Lock NodeLock Node ID: lockNode Locks a node as the current user. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the node. branchId text true The ID of the branch of the node. nodeId text true The ID of the node.
Score: 0.78884697
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Lock NodeLock Node ID: lockNode Locks a node as the current user. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the node. branchId text true The ID of the branch of the node. nodeId text true The ID of the node.
Score: 0.78884697
|
|
Gitana / 3.2 / Guide / Guide / Features / Auto RecognizeAuto Recognize This section describes features that are coming in 4.0 QName: f:auto-recognize With this feature in place, a content instance will automatically have its default binary attachment processed through recognition services to detect and discover meaning contained in the underlying image. The recognition process will detect the following kinds of elements: Faces Celebrities Labels Text Moderation Labels (bad language, adult content) To use this service, you will first need to set up a
Score: 0.78767115
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Projects / Configure SearchConfigure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"
Score: 0.78767115
|
|
Gitana / 4.0 / Data Engine / Aspects / Auto RecognizeAuto Recognize This section describes features that are coming in 4.0 QName: f:auto-recognize With this feature in place, a content instance will automatically have its default binary attachment processed through recognition services to detect and discover meaning contained in the underlying image. The recognition process will detect the following kinds of elements: Faces Celebrities Labels Text Moderation Labels (bad language, adult content) To use this service, you will first need to set up a
Score: 0.78767115
|
|
Gitana / 4.0 / User Interface / Projects / Configure SearchConfigure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"
Score: 0.78767115
|
|
Gitana / 3.2 / Guide / Guide / Actions / Start WorkflowStart Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica
Score: 0.7856657
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / EvaluatorsEvaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators
Score: 0.7856657
|
|
Gitana / 4.0 / Developers / User Interface Customization / EvaluatorsEvaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators
Score: 0.7856657
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Start WorkflowStart Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica
Score: 0.7856657
|