Found 246 results for "images quickstart folder"

The search executed in 0.001505603 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.85

Upgrade 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.3537526

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.86

Upgrade 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.3537526

Gitana / 3.2 / Guide / Guide / Recognition / Recognition Providers / AWS Rekognition

AWS Rekognition: Analyze and recognize images effortlessly. Set up with accessKey, secretKey, region, and bucketName for secure S3 operations.

Score: 2.3488464

Gitana / 4.0 / Content Engine / Services / Recognition / Recognition Providers / AWS Rekognition

AWS Rekognition: Analyze and recognize images effortlessly. Set up with accessKey, secretKey, region, and bucketName for secure S3 operations.

Score: 2.3488464

Gitana / 3.2 / Guide / Guide / Application Server / Tags / @resource

Create cache-sensitive, browser-ready URIs with @resource, automating hash changes for updated resources while ensuring effective caching.

Score: 2.313878

Gitana / 4.0 / Developers / Application Server / Tags / @resource

Create cache-sensitive, browser-ready URIs with @resource, automating hash changes for updated resources while ensuring effective caching.

Score: 2.313878

My UI modules aren't deploying. What should I check?

If you're running an on-premise installation of Cloud CMS and are unable to deploy UI modules via the main user interface, here are a few tips and pointers. Things to consider: 1. When you click on the "Deploy Module" option, your a URL connection is made from the UI server back to the API server. Specifically, it invokes a POST to the route: /oneteam/modules/deploy Check your API side logs or any firewalls or proxies along the way to make sure that an API server receives this call. For example,

Score: 2.2822905

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.79

Upgrade to Cloud CMS 3.2.79 for ARM-64 support, enhanced performance, and improved Elastic Search integration. Utilize our tools for seamless upgrades.

Score: 2.2656066

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.80

Upgrade to Cloud CMS 3.2.80 for ARM aarch64 support, enhanced Elastic Search, and Redis updates, unlocking better performance and cost-effectiveness.

Score: 2.2656066

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.81

Upgrade to Cloud CMS 3.2.81 with ARM aarch64 support, Elastic Search and Redis enhancements. Use our CLI for seamless upgrades.

Score: 2.2656066

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.82

Cloud CMS 3.2.82: Upgrade notes, ARM-64 support, Elastic Search client update, Redis upgrade, and CLI upgrade tool information.

Score: 2.2656066

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.83

Upgrade to Cloud CMS 3.2.83 for ARM64 support, Elastic Search improvements, and Redis 6.x compatibility with easy deployment options.

Score: 2.2656066

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / new_folder

Easily create new folders with customizable content types in your current directory using our intuitive wizard. Adjust settings via configuration service.

Score: 2.228449

Gitana / 4.0 / Developers / User Interface Customization / Actions / new_folder

Easily create new folders with customizable content types in your current directory using our intuitive wizard. Adjust settings via configuration service.

Score: 2.228449

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.2178636

How we use Docker at Cloud CMS

At 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.1702707

UI feature - Folder Navigation Tree

Cloud 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.1700878

Content definition - JSON Schema v4 document

1. 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.0917559

Limiting Folder Access to Specific Users

When 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.0800762

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Copy Node

Copy nodes within workflow payloads efficiently to target folders or projects using node IDs or paths, supporting branches and repositories.

Score: 2.070873

Gitana / 4.0 / Content Engine / Workflow / Workflow Handlers / Copy Node

Copy nodes within workflow payloads efficiently to target folders or projects using node IDs or paths, supporting branches and repositories.

Score: 2.070873

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / create_document

Guide users effortlessly through creating documents with the intuitive wizard, customizing content types via configuration for seamless content management.

Score: 2.060122

Gitana / 4.0 / Developers / User Interface Customization / Actions / create_document

Guide users effortlessly through creating documents with the intuitive wizard, customizing content types via configuration for seamless content management.

Score: 2.060122

Gitana / 3.2 / Guide / Guide / Actions / Unzip Node

Unzip Node effortlessly extracts ZIP attachments from a node to a target folder, enhancing file management and repository organization.

Score: 2.0595992

Gitana / 4.0 / Content Engine / Behaviors / Actions / Unzip Node

Unzip Node effortlessly extracts ZIP attachments from a node to a target folder, enhancing file management and repository organization.

Score: 2.0595992