Found 179 results for "branches indexes"
The search executed in 0.001609027 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / BranchesBranches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t
Score: 16.636898
|
![]() |
Gitana / 3.2 / Guide / Guide / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 11.409703
|
![]() |
Gitana / 4.0 / Data Engine / Branches / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 11.409703
|
![]() |
Gitana / 4.0 / User Interface / User Interface / Version ControlVersion Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w
Score: 10.253407
|
![]() |
Gitana / 4.0 / Data Engine / Branches / OverviewBranches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t
Score: 9.39864
|
![]() |
Gitana / 3.2 / Guide / Guide / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 9.393915
|
![]() |
Gitana / 4.0 / Data Engine / Branches / Custom IndexesCustom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha
Score: 9.393915
|
![]() |
Gitana / 4.0 / Getting Started / Working with Content / BranchesBranches Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was creat
Score: 8.962898
|
![]() |
Gitana / 3.2 / Guide / Guide / ReleasesReleases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab
Score: 6.196822
|
![]() |
Gitana / 4.0 / Data Engine / Releases / OverviewReleases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab
Score: 6.196822
|
![]() |
Gitana / 3.2 / Guide / Guide / User Interface / Version ControlVersion Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w
Score: 5.0555778
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-manage-contextproject-manage-context [ { "evaluator": "context-project", "config": { "project-manage-context": { "items": [ { "key": "project/manage/header", "title": "Manage", "order": 10000, "header": true, "allowAuthority": [ "collaborator", "manager" ], "items": [ { "key": "project/settings", "title": "Project Settin
Score: 4.1823816
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / project-manage-contextproject-manage-context [ { "evaluator": "context-project", "config": { "project-manage-context": { "items": [ { "key": "project/manage/header", "title": "Manage", "order": 10000, "header": true, "allowAuthority": [ "collaborator", "manager" ], "items": [ { "key": "project/settings", "title": "Project Settin
Score: 4.1823816
|
![]() |
Gitana / 3.2 / Guide / Guide / Features / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 4.097693
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / IndexableIndexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc
Score: 4.097693
|
![]() |
Gitana / 3.2 / Guide / Guide / SearchSearch Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations
Score: 3.758802
|
![]() |
Gitana / 4.0 / Data Engine / Discovery / SearchSearch Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations
Score: 3.758802
|
![]() |
Query PerformanceApplication queries Application code which consumes Cloud CMS content typically runs query API calls. These queries can be optimized in the following ways: Request only the properties needed When an application requires only a few properties from a set of nodes you should use “_fields” to limit the properties returned. This can drastically reduce the size of the payload and therefore the response time. In this example, we only need “_doc”, “title” and “_type” so these are the only fields that wi
Score: 3.3559723
|
![]() |
Gitana / 3.2 / Guide / Guide / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 3.2200496
|
![]() |
Gitana / 4.0 / Data Engine / Discovery / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 3.2200496
|
![]() |
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 2.867273
|
![]() |
Gitana / 4.0 / Self Managed / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 2.867273
|
![]() |
Gitana / 3.2 / Guide / Guide / Command LineCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get
Score: 2.7302353
|
![]() |
Gitana / 4.0 / Developers / Command Line Interface / OverviewCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started To get
Score: 2.7302353
|
![]() |
Documentation: Developers - Overview - GitanaDocumentation: Developers - Overview - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, distribute and utilize your data operations, all integrated seamlessly and managed via single point of access. Automate Automate your content creation and approval flows while taking advantage of AI s
Score: 2.5837388
|