Capability

Cloud

Liferay Cloud Platform provides the infrastructure and tooling necessary to simplify, secure, and deliver applications on Liferay DXP when using the SaaS or PaaS deployment approaches. Using Liferay’s Cloud infrastructure provides a secure, reliable, and scalable platform for building Liferay solutions.

The Liferay Cloud Platform includes DevOps CI/CD tools, automated backups, real-time logs, and much more.

カテゴリ
カテゴリ
ファイルとフォルダを無視する
Ignoring Files and Folders Liferay Cloud allows subscribers to determine which files and folders should be ignored before deploying a service. This is done by creating a .lcpignore file and placed...
Jenkinsステージの再起動
Restarting Jenkins Stages The CI service can be configured to preserve Jenkins stashes. You can then use the stashes to restart specific stages in a Jenkins build. Preserving Jenkins Stashes Use...
デプロイメント戦略について
Understanding Deployment Strategies The deployment strategy of a service determines how new versions will be initialized. Liferay PaaS provides two deployment strategies for its services:...
配布タイプについて
Understanding Deployment Types The deployment type of a service determines many different facets of how it functions, including performance, memory usage, and access to files or volumes. Liferay...
クラウドネットワークの構成
Configuring the Cloud Network Every environment has its own private network, so services from the same environment can communicate through secure protocols without interacting with the public...
VPNサーバーの設定
Configuring a VPN Server The following scenario walks through how to set up an IPsec or OpenVPN VPN server. Once a VPN server is configured, a secure connection can be established between an...
カスタムドメイン
Custom Domains With Liferay Cloud, you can connect custom domains to environment services with a DNS provider. First, register your custom domain with your environment's Load Balancer IP address....
ロードバランサー
Load Balancer The Ingress Load Balancer gives internet access to your environment's services via proxied HTTP(S) connections using TLS (1.2 or 1.3) protocol. Each load balancer has a static IP that...