6

Changing file(s) in vendor directly is not a best practice. It's better if you create a patch for the changes, and apply the patch in your Magento Cloud. To better understanding on how to create and apply patch, see this link.


4

Install magento-cloud cli https://devdocs.magento.com/cloud/reference/cli-ref-topic.html Get a project and environment with the magento-cloud cli Run command to go into the current environment, dump the file, and then download it to your local computer magento-cloud db:dump


3

I think you should using magento-cloud ssh and ssh to Magento Cloud Node such as production, staging Using CURL to check Elasticsearch result Elastic search document << here, example: I want to get all product are belongs to Category 3 curl -X GET 'ip:port/[index]/_search?pretty' -H 'Content-Type: application/json' -d '{ "query": { "bool": {...


3

Magento 2 Enterprise Cloud comes with 3 envoirnments setup by detault Integration , Staging and Production. In integration environment you only have 2 caching option available Bulit-in and Varnish, however in staging and production you have one more caching option Fastly CDN available. So for staging and production ( live ) you will only be using Fastly CDN ...


3

If your goal is to access it using some type of GUI client, you could accomplish this by opening an ssh tunnel using the magento-cloud utility, similar to the above answer: magento-cloud tunnel:open --project=<PROJECT_ID> --environment=staging Then run the command magento-cloud tunnel:info to get the appropriate credentials to input into whatever ...


2

Currently, you can add the next code to env.php file only manually: return [ ... 'static_content_on_demand_in_production' => 1, ... ];


2

As MSA has noted, you can ssh into the machine and use ece-tools db-dump and then rsync the database dump down locally.Here is the rsync command rsync -avzh <SSH URL>:/tmp/<BACKUP NAME> ./ Another option is to utilize the magento-cloud CLI utility. You can download the CLI utility with these instructions: https://devdocs.magento.com/guides/v2....


2

It seems the addAttribute method does not install this pagebuilder property. The solution for me was to add the attribute and then immediatly run the updateAttribute method as defined by @Dave $eavSetup = $this->eavSetupFactory->create(['setup' => $this->moduleDataSetup]); $eavSetup->addAttribute( Product::ENTITY, self::...


2

Most Magento 2 stores get hacked via Adminer or the March '19 SQL injection flaw. A smaller portion get breached via insecure extensions, brute force password guessing or spearphishing attacks against staff members. The only way to say for sure, is to analyze the log files and event log tables. My Magento Malware Scanner (as referenced in the other answer) ...


2

you must have some monitoring enabled. you can use all these tools, or some of them, configure some options and settings. csf firewall fast software firewall with easy to use config + cli: https://configserver.com/cp/csf.html WAZUH (OSSEC mod) + ELK stack you can configure it to monitor and run some actions. Kibana dashboard + email reports. remote and ...


2

ece-tools is available in magneto 2 . You can just refer link https://devdocs.magento.com/cloud/reference/ece-tools-reference.html


1

I'm guessing you're confusing things. If you're using Magento free version it means that it is Magento Open Source, which should not show in Cloud account. And I'm guessing again, error you're seeing is required authorization when you're trying to do 'composer install' to download magento from repo. You can get this credentials by following steps described ...


1

502 error nginx upstream not available. you need to check nginx proxy / php block in configuration. nginx php upstream wrong port defined, socket permissions, upstream not running, firewall blocking, error log you can see in nginx config: https://docs.nginx.com/nginx/admin-guide/monitoring/logging/#error_log https://nginx.org/en/docs/ngx_core_module.html?...


1

During development, you can use own external DB. The .magento.env.yaml.dist file contains an example of how to configure DB connections. Just find the description of DATABASE_CONFIGURATION Unfortunately, each push triggers rebuilding and redeploy. To decrease deploy time during development you can enable the generation of static on-demand. Just find the ...


1

Understanding Package Management First off, any answers that suggest removing or editing the composer.lock file directly are wrong. Deleting composer.lock and regenerating will effectively upgrade every package to the latest version as specified by your composer.json file, and you should never edit the lock file directly. magento/magento-cloud-metapackage ...


1

I think you should check the official Magento Docs to add a new field to checkout. Follow the docs to add the field so you can handle the data submission as well. https://devdocs.magento.com/guides/v2.3/howdoi/checkout/checkout_new_field.html The code you posted adds the field to checkout but you can't do much with it, it just renders it to the view.


1

I would recommend running the php bin/magento module:disable command in a local checkout of your code to ensure that the proper module name is used as it is possible it is not matching approrpiately. This will add the MyCompany_MyModule => 0 to the config.php. After that, git add/commit the updated config.php and it should be disabled!


1

There are several options to decrease the time of deployment: Move SCD on build phase Build phase Enable SCD on demand SCD_ON_DEMAND Use SCD matrix SCD_MATRIX


1

Try: SSH to the Integration environment. magento-cloud ssh Connect to the database. mysql -h <db-host> -P <db-port> -p -u <db-user> <db-name>


1

I have applied patch (CE-MAGETWO-93036-2018-07-02-07-06-53.patch) to Magento Cloud, Magento version 2.2.5. The steps I followed were: Created a folder on root "m2-hotfixes" (see if it already exists) Put the patch file here Now, git add, git commit and push I found that the changes were applied. You may give it a try if it works for you as well.


1

Magento has talked about all environment variables in the link whichever you have shared. I hope, you want to save the API token and fetch it on controller to trigger web service call right. If so, you can create simple store configuration option in your module system.xml file which will allow store admin to set the token whenever you want and you can ...


1

Im afraid you cant do that on cloud. The deployment is automatic by ece-tools package . [Cloud Info] ece-tools package The ece-tools package is a scalable deployment tool that simplifies the Cloud upgrade process. In 2018, we deprecated the magento-cloud-configuration and ece-patches packages in favor of providing a single package. We encourage all ...


1

Enterprise unlocks additional features of the platform via additional modules that are installed. The core Magento team do not have access to your installation, unless you ask them for support. Andy pointed out that there is also a built-in backup system that could be utilized to provide a snapshot of your system to Magento for support. Utilizing this tool ...


1

Well, I send a ticket to Magento, and they answered me this: Hello, What you are seeing is the normal workflow for Magento cloud. For any code change, you will need to push and the deployment process will take the site down. Here are the articles explaining this: https://devdocs.magento.com/guides/v2.2/cloud/basic-information/starter-develop-...


1

I guess the answers from Extensions charging more for enterprise? are still valid. For the second question - "How to verify ..." I think there is no right answer. If the vendor offers great support, it may be worth the money. If they produce good code (in quality) it may be also worth. If I need to buy an extension, I only buy from bigger extension ...


1

If you can SSH into the machine, use vendor/bin/ece-tools cron:kill If that produces an error or doesn't resolve the issue, then creating a ticket is the best way. Usually picked up and resolved pretty quickly if filed as (Stuck Deployment)


1

You can copy your files on build phase during composer install from your module to some destination. Just create a mapping in composer.json of your module. More information https://github.com/magento/magento-composer-installer


Only top voted, non community-wiki answers of a minimum length are eligible