Found 251 results for "images quickstart folder"
The search executed in 0.002160481 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.85Upgrade to Cloud CMS 3.2.85 with ARM-64 support, enhanced performance, and Redis 6.x compatibility. Access detailed release and upgrade notes.
Score: 2.3462288
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.86Upgrade to Cloud CMS 3.2.86 for ARM-64 support, improved performance, and compatibility with Redis 6.x. Follow release notes and upgrade tools for guidance.
Score: 2.3462288
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.87Upgrade to Cloud CMS 3.2.87 for enhanced ARM-64 support, requiring MongoDB 4.0+ and Redis 6.x+. Optimize deployments with AWS Graviton.
Score: 2.3237348
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.88Upgrade to Cloud CMS 3.2.88! Enjoy ARM aarch64 support with better performance and lower costs. Requires MongoDB 4.0+ and Redis 6.x+.
Score: 2.3237348
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / Tags / @resourceCreate browser-ready URIs with @resource, auto-updating for cache sensitivity when file contents change, ensuring efficient web caching.
Score: 2.3057485
|
![]() |
Gitana 4.0 / Developers / Application Server / Tags / @resourceCreate a cache-sensitive URI using @resource to ensure efficient loading and accurate file updates with automatic cache control.
Score: 2.3057485
|
![]() |
Gitana 3.2 / Guide / Guide / Recognition / Recognition Providers / AWS RekognitionAWS Rekognition: Analyze and recognize images effortlessly. Set up with accessKey, secretKey, region, and bucketName for secure S3 operations.
Score: 2.2952232
|
![]() |
Gitana 4.0 / Content Engine / Services / Recognition / Recognition Providers / AWS RekognitionAWS Rekognition: Analyze and recognize images effortlessly. Set up with accessKey, secretKey, region, and bucketName for secure S3 operations.
Score: 2.2952232
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.79Upgrade to Cloud CMS 3.2.79 with support for ARM-64, enhanced ElasticSearch integration, and Redis 6.x compatibility for improved performance.
Score: 2.2587688
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.80Upgrade to Cloud CMS 3.2.80 for enhanced ARM-64 support, improved ElasticSearch integration, and Redis 6.x compatibility. Optimize your deployment now.
Score: 2.2587688
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.81Upgrade to Cloud CMS 3.2.81 for ARM aarch64 support, new ElasticSearch client, Redis 6.x upgrade, and improved performance. Explore release notes now!
Score: 2.2587688
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.82Upgrade to Cloud CMS 3.2.82 for ARM-64 support and enhanced performance. Optimize ElasticSearch connections with the Condor client and update Redis to 6.x+.
Score: 2.2587688
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.83Upgrade to Cloud CMS 3.2.83 with improved ARM aarch64 support, ElasticSearch connection via condor, and Redis updates for better performance.
Score: 2.2587688
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / Actions / new_folderEasily create new folders with customizable content types in your current directory using our intuitive wizard. Adjust settings via configuration service.
Score: 2.2104363
|
![]() |
Gitana 4.0 / Developers / User Interface Customization / Actions / new_folderEasily create new folders with customizable content types in your current directory using our intuitive wizard. Adjust settings via configuration service.
Score: 2.2104363
|
![]() |
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: 2.2074385
|
![]() |
How we use Docker at Cloud CMSAt Cloud CMS, we use Docker to provision our cloud infrastructure servers on top of Amazon Web Services. Our stack consists of five different clusters: Cloud CMS API Cloud CMS UI Cloud CMS App Server for Dynamic Hosting Elastic Search MongoDB With the exception of MongoDB, all of these clusters are allocated using elastic load balancing and are architected in such a way that we can spin up new servers and tear down old ones with elastic demand. That is to say, they are fully elastic in design. T
Score: 2.1642294
|
![]() |
UI feature - Folder Navigation TreeCloud CMS now provides a left-hand Folder Tree in the Folders view. Although a relatively simple feature, the left-hand Folder Tree makes navigation between folders much easier and is a familiar way to view and navigate content. The left-hand Folder tree can be enabled or disabled from the Project Settings page (set to disabled by default). After the left-hand Folder Tree is enabled, it can then be seen under Browse By Folder. If a folder contains one or more folders within it, then there is an
Score: 2.152629
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Security Notices / CVE-2022-22965Secure your Cloud CMS instance against CVE-2022-22965 by upgrading to 3.2.76 or applying our recommended workaround.
Score: 2.0753744
|
![]() |
Content definition - JSON Schema v4 document1. A content definition is a JSON Schema v4 document. As such, the valid property types are those supported by JSON Schema itself, described more thoroughly here: http://json-schema.org/latest/json-schema-core.html (Specifically, look under section 4.2.1 Instance Data Model) 2. The default path capability is frequently used to make sure that content of a given type is stored into a predictable "folder" structure. You're right to be inquisitive about what this means since everything in Cloud CMS
Score: 2.0752666
|
![]() |
Limiting Folder Access to Specific UsersWhen you create a Project in Cloud CMS, the Project is automatically configured with a Project Users team that grants the Consumer role to any project members. As a result, any members of the Project will have the ability to see all content within the Project. For many, this works just fine. However, there may be cases where you want to limit certain Folders to only be accessible by specific Users. Let's walk through some steps on how to do this. Change the Project Users team security policy Fir
Score: 2.0638666
|
![]() |
Gitana 3.2 / Guide / Guide / Workflow / Workflow Handlers / Copy NodeCopy nodes within workflow payloads efficiently to target folders or projects using node IDs or paths, supporting branches and repositories.
Score: 2.0544825
|
![]() |
Gitana 4.0 / Content Engine / Workflow / Workflow Handlers / Copy NodeCopy nodes within workflow payloads efficiently to target folders or projects using node IDs or paths, supporting branches and repositories.
Score: 2.0544825
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / Actions / create_documentGuide users effortlessly through creating documents with the intuitive wizard, customizing content types via configuration for seamless content management.
Score: 2.0438712
|
![]() |
Gitana 4.0 / Developers / User Interface Customization / Actions / create_documentGuide users effortlessly through creating documents with the intuitive wizard, customizing content types via configuration for seamless content management.
Score: 2.0438712
|