Found 247 results for "release download node.js"

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

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.84

Upgrade to Cloud CMS 3.2.84 for ARM-64 support, enhanced performance, and Redis 6.x compatibility. Access release and upgrade notes for more details.

Score: 3.3775733

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: 3.3775733

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: 3.3775733

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.88

Upgrade 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: 3.3182821

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.89

Upgrade to Cloud CMS 3.2.89 with ARM-64 support, MongoDB 4.4+ requirements, and Redis 6.x configuration for improved performance and deployment flexibility.

Score: 3.3182821

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

Upgrade to Cloud CMS 3.2.79 with support for ARM-64, enhanced ElasticSearch integration, and Redis 6.x compatibility for improved performance.

Score: 3.1544182

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

Upgrade to Cloud CMS 3.2.80 for enhanced ARM-64 support, improved ElasticSearch integration, and Redis 6.x compatibility. Optimize your deployment now.

Score: 3.1544182

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

Upgrade 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: 3.1544182

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

Upgrade 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: 3.1544182

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

Upgrade to Cloud CMS 3.2.83 with improved ARM aarch64 support, ElasticSearch connection via condor, and Redis updates for better performance.

Score: 3.1544182

Gitana 4.0 Developers Guide | Overview

Gitana 4.0 Developers Guide | Overview Status Releases Registry Blog Cloud CMS Platform Platform Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Automation Automate your content creation and approval flows while taking advantage of AI services to enhance and

Score: 3.0106792

Product Releases - Gitana

Product Releases - Gitana Status Releases Registry Blog Cloud CMS Platform Platform Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Automation Automate your content creation and approval flows while taking advantage of AI services to enhance and curate conten

Score: 2.9186773

Node Lifecycle Events

First, you configure your tenant with the AWS credentials of an IAM user and a SNS topic ARN that you wish to publish notification events to. This can be on your own AWS account so that you can work with these notifications any way you'd like. The notifications are for a variety of node lifecycle events. The primary one is "node_invalidation" which happens whenever a node's state changes. It's an indication that anyone caching anything downstream might want to reconsider their cache state. In te

Score: 2.7839568

Proxy API calls

Whenever a resulting URL looks something like: https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes//attachments/thumb.jpg It works great as an API URL but not necessarily as one that can be resolved by the end user's browser. In a typical Node.js-based architecture, you have the User’s browser Node.js application server Cloud CMS backend API The URL generated above is the URL directly to the resource in the backend API. What you really would pre

Score: 2.6200724

Cloud CMS Architecture

Cloud CMS has two clusters that we run for customers who host apps with us. One cluster is for the "app server" tier (*.cloudcms.net) and the other is the "API" tier (api.cloudcms.com). The app server cluster consists of Node.js servers, and the API is a Java-backend that is stateless and implements the full REST API: As such, the API doesn't manage connections directly. Any invocation to it is a one-shot where each request contains everything needed to assert the user's identity and proceed wit

Score: 2.6200724

Gitana 3.2 / Guide / Guide / Docker / Kits

Download pre-built Cloud CMS Docker kits for common scenarios, ideal for quick setup or as a configuration reference. Explore our resources now.

Score: 2.6010008

Gitana 4.0 / Self Managed / Kits

Explore Cloud CMS Docker Kits for pre-built, user-friendly configurations to quickly deploy APIs, UI, and more with ease using Docker and Docker Compose.

Score: 2.6010008

Connecting via a Corporate Proxy

The Cloud CMS drivers support connectivity through a corporate proxy. The means of doing so are slightly different depending on which driver you're using. Node.js The Cloud CMS Node.js driver detects the following environment variable: HTTP_PROXY If this environment variable is specified, all API calls with be routed through the proxy server at that location. This proxy server may support either HTTP or HTTPS. For example, you may set the environment variable like this: HTTP_PROXY=http://127.0.0

Score: 2.5825558

Gitana 3.2 / Guide / Guide / UI Developers Guide / Contexts / messages

Manage and resolve release conflicts efficiently with tools to schedule, finalize, and review changes in your projects.

Score: 2.5456626

Gitana 4.0 / Developers / User Interface Customization / Contexts / messages

Manage and resolve release conflicts efficiently with tools to schedule, finalize, and review changes in your projects.

Score: 2.5456626

Gitana 3.2 / Guide / Guide / Releases / Actions

Configure and execute release actions with Gitana; supports email, Slack, and web hooks. Customize with JSON for optimal workflow integration.

Score: 2.538498

Gitana 4.0 / Content Engine / Branch Overview / Releases / Actions

Configure actions like sending emails, Slack messages, or firing web hooks on release events. Utilize variables like releaseId for custom setups.

Score: 2.538498

Access Cloud CMS content anonymously or as a guest user

This question often comes up from folks who are building HTML applications that run in a browser. They'd like the browser to connect to Cloud CMS to download content and display it. Usually this consists of things like images but also may consist of other types of content in Cloud CMS such as raw nodes, PDF files, video assets or more. OAuth 2.0 and Access Tokens Fundamentally, everything in Cloud CMS is secured from an access perspective using OAuth 2.0. This means that an OAuth 2.0 access toke

Score: 2.5096412

Gitana 3.2 / Guide / Guide / User Interface / Releases

Manage content effortlessly with Cloud CMS Releases, enabling collaborative workspaces, scheduled publishing, and conflict resolution for seamless content management.

Score: 2.4934509

Gitana 3.2 / Guide / Guide / Branches / Actions

Configure automated actions for release events with JSON settings. Supports Send Email and Web Hook with variables like releaseId and branchId.

Score: 2.4906588