Вячеслав Докукин (Все сообщения пользователя)

let form = $('form[name=quick-order]')[0];

let formData = BX.ajax.prepareForm(form).data; // object

BX.ajax({
    url: '<?=$APPLICATION->GetCurPage()?>',
    data: formData,
    method: 'POST',
    dataType: 'json',
    timeout: 30,
    async: true,
    processData: true,
    scriptsRunFirst: true,
    emulateOnload: true,
    start: true,
    cache: false,
      onsuccess: function(data){
         if(data.STATUS == 'OK') {
         
         }
         
         console.log(data.MESSAGE);   
            
      },
      onfailure: function(){
         console.log(data.MESSAGE);            
      }
}); 

$ composer require bitrix24/b24phpsdk
Cannot use bitrix24/b24phpsdk's latest version 1.3.0 as it requires ext-intl * which is missing from your platform.

In PackageDiscoveryTrait.php line 325:
                                                                                                                        
  Package bitrix24/b24phpsdk has requirements incompatible with your PHP version, PHP extensions and Composer version:  
    - bitrix24/b24phpsdk 1.3.0 requires ext-intl * but it is not present.   

dnf install php-intl.x86_64

Last metadata expiration check: 2:36:48 ago on Wed 28 May 2025 08:04:05 PM MSK.

Error:  
 Problem: cannot install both php-common-8.0.30-3.el9.x86_64 from appstream and php-common-8.2.28-1.el9.remi.x86_64 from @System

  - package php-intl-8.0.30-3.el9.x86_64 from appstream requires php-common(x86-64) = 8.0.30-3.el9, but none of the providers can be installed

  - package php-pecl-geoip-1.1.1-16.el9.remi.8.2.x86_64 from @System requires php(api) = 20220829-64, but none of the providers can be installed

  - package php-pecl-geoip-1.1.1-16.el9.remi.8.2.x86_64 from @System requires php(zend-abi) = 20220829-64, but none of the providers can be installed

  - cannot install the best candidate for the job

  - problem with installed package php-pecl-geoip-1.1.1-16.el9.remi.8.2.x86_64

  - package php-common-8.2.13-1.module_el9+766+427f1f3d.x86_64 from appstream is filtered out by modular filtering

  - package php-common-8.2.28-1.module_el9+1229+58548675.x86_64 from appstream is filtered out by modular filtering

  - package php-common-8.2.27-1.el9.remi.x86_64 from remi-modular is filtered out by modular filtering

  - package php-common-8.2.28-1.el9.remi.x86_64 from remi-modular is filtered out by modular filtering

[root@vm1 ~]# cat /opt/webdir/temp/pushserver_5681310086/status     
 [WARNING]: Consider using the get_url or uri module rather than running

'curl'.  If you need to use command because get_url or uri is insufficient you

can add 'warn: false' to this command task or set 'command_warnings=False' in

ansible.cfg to get rid of this message.

 [WARNING]: Consider using the yum, dnf or zypper module rather than running

'rpm'.  If you need to use command because yum, dnf or zypper is insufficient

you can add 'warn: false' to this command task or set 'command_warnings=False'

in ansible.cfg to get rid of this message.

 [WARNING]: Consider using the yum module rather than running 'yum'.  If you

need to use command because yum is insufficient you can add 'warn: false' to

this command task or set 'command_warnings=False' in ansible.cfg to get rid of

this message.

*************************************************

ok: [vm4] => (item=/etc/yum.repos.d/nodesource-el.repo)

ok: [vm4] => (item=/etc/yum.repos.d/nodesource-el6.repo)



TASK [push-server : configure nodejs repository] *******************************

changed: [vm4]



TASK [push-server : delete old nodejs-packages] ********************************

failed: [vm4] (item=nodejs) => {"changed": true, "cmd": "rpm -e --nodeps \"nodejs\"", "delta": "0:00:00.053947", "end": "2024-07-08 23:33:27.352412", "item": "nodejs",
 "msg": "non-zero return code", "rc": 1, "start": "2024-07-08 23:33:27.298465", "stderr": "error: package nodejs is not installed", "stderr_lines": ["error: package no
dejs is not installed"], "stdout": "", "stdout_lines": []}

failed: [vm4] (item=npm) => {"changed": true, "cmd": "rpm -e --nodeps \"npm\"", "delta": "0:00:00.039297", "end": "2024-07-08 23:33:27.703592", "item": "npm", "msg": "
non-zero return code", "rc": 1, "start": "2024-07-08 23:33:27.664295", "stderr": "error: package npm is not installed", "stderr_lines": ["error: package npm is not ins
talled"], "stdout": "", "stdout_lines": []}

...ignoring



TASK [push-server : shell] *****************************************************

changed: [vm4]



TASK [push-server : install packages] ******************************************

fatal: [vm4]: FAILED! => {"changed": false, "msg": "Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was\n14
: curl#6 - \"Could not resolve host: mirrorlist.centos.org; Unknown error\"\n\n\n One of the configured repositories failed (Unknown),\n and yum doesn't have enough ca
ched data to continue. At this point the only\n safe thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n     1. Contact the upstream for the repos
itory and get them to fix the problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to point to a working\n        upstream. This is most often useful i
f you are using a newer\n        distribution release than is supported by the repository (and the\n        packages for the previous distribution release still work).
\n\n     3. Run the command with the repository temporarily disabled\n            yum --disablerepo=<repoid> ...\n\n     4. Disable the repository permanently, so yum 
won't use it by default. Yum\n        will then just ignore the repository until you permanently enable it\n        again or use --enablerepo for temporary usage:\n\n 
           yum-config-manager --disable <repoid>\n        or\n            subscription-manager repos --disable=<repoid>\n\n     5. Configure the failing repository to 
be skipped, if it is unavailable.\n        Note that yum will try to contact the repo. when it runs most commands,\n        so will have to try and fail each time (and
 thus. yum will be be much\n        slower). If it is a very temporary problem though, this is often a nice\n        compromise:\n\n            yum-config-manager --sa
ve --setopt=<repoid>.skip_if_unavailable=true\n\nCannot find a valid baseurl for repo: base/7/x86_64\n", "rc": 1, "results": []}

        to retry, use: --limit @/etc/ansible/push-server.retry



PLAY RECAP *********************************************************************

vm4                        : ok=10   changed=3    unreachable=0    failed=1   

# Bitrix ЧПУ
if ($request_uri ~ ^(.*)/index.(html|php)) { return 301 $1/$is_args$args; }
location / { try_files $uri $uri/ /bitrix/urlrewrite.php$is_args$args; }
location ~* @.*\.html$ { internal; }

# PHP

short_open_tag = On

log_errors = On

error_log = /var/log/php_errors.log

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

max_input_vars = 10000

<MODULES><CANGZIP VALUE="Y"/><ERROR TYPE="LICENSE_KEY_REQUIRED">License key is required</ERROR></MODULES>

stages:
 - deploy

variables:
 host_remote: 82.146.34.161
 port_remote: 22
 GIT_STRATEGY: none
 deploy_path: /home/deploy/site-name.ru/
 stage_remote: /home/bitrix/ext_www/stage.site-name.ru/
 prod_remote: /home/bitrix/www/

copy-files-to-stage:
 stage: deploy
 tags:
   - deploy
 before_script:
   - eval $(ssh-agent -s)
   - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
   - mkdir -p ~/.ssh
   - chmod 700 ~/.ssh
 script:
   - echo "Deploying application..."
   - ssh -o StrictHostKeyChecking=no bitrix@$host_remote -p $port_remote -v "cd ${deploy_path}; git checkout stage; git fetch && git reset --hard origin/stage; pwd; rsync -atv --exclude .git --exclude .gitlab-ci.yml --exclude .gitignore ${deploy_path} ${stage_remote}"
   - hostname
   - pwd
   - whoami
   - echo "Application successfully deployed!"
 only:
   - stage

copy-files-to-prod:
 stage: deploy
 tags:
   - deploy
 before_script:
   - eval $(ssh-agent -s)
   - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
   - mkdir -p ~/.ssh
   - chmod 700 ~/.ssh
 script:
   - echo "Deploying application..."
   - ssh -o StrictHostKeyChecking=no bitrix@$host_remote -p $port_remote -v "cd ${deploy_path}; git checkout main; git fetch && git reset --hard origin/main; pwd; rsync -atv --exclude .git --exclude .gitlab-ci.yml --exclude .gitignore ${deploy_path} ${prod_remote}"
   - hostname
   - pwd
   - whoami
   - echo "Application successfully deployed!"
 only:
   - main

git fetch && git reset --hard origin/main

fatal: git fetch-pack: expected shallow list
fatal: The remote end hung up unexpectedly

sudo yum remove git

wget https://repo.bitrix.info/yum/bitrix-env.sh && chmod +x bitrix-env.sh && ./bitrix-env.sh

stages:
  - deploy

variables:
  host_remote: 82.176.77.132
  port_remote: 22
  dev_remote: /home/bitrix/ext_www/stage.site-name.ru/
  prod_remote: /home/bitrix/www/

copy-files-to-dev:
  stage: deploy
  tags:
    - deploy
  before_script:
    - eval $(ssh-agent -s)
    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
    - mkdir -p ~/.ssh
    - chmod 700 ~/.ssh
  script:
    - echo "Deploying application..."
    - ssh -o StrictHostKeyChecking=no bitrix@$host_remote -p $port_remote -v "cd ${dev_remote}; date;"
    - rsync -atv -e 'ssh -p '${port_remote} --exclude .git --exclude .gitlab-ci.yml --exclude .gitignore ./ bitrix@$host_remote:$dev_remote
    - hostname
    - pwd
    - whoami
    - echo "Application successfully deployed!"
  only:
    - stage

copy-files-to-prod:
  stage: deploy
  tags:
    - deploy
  before_script:
    - eval $(ssh-agent -s)
    - echo "$SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
    - mkdir -p ~/.ssh
    - chmod 700 ~/.ssh
  script:
    - echo "Deploying application..."
    - ssh -o StrictHostKeyChecking=no bitrix@$host_remote -p $port_remote -v "cd ${dev_remote}; date;"
    - rsync -atv -e 'ssh -p '${port_remote} --exclude .git --exclude .gitlab-ci.yml --exclude .gitignore ./ bitrix@$host_remote:$prod_remote
    - hostname
    - pwd
    - whoami
    - echo "Application successfully deployed!"
  only:
    - main

location ~* ^/bx_tmp_download/ {

    internal;

    rewrite /bx_tmp_download/(.+) /.bx_temp/sitemanager/$1 last;

}



location ~* ^/.bx_temp/sitemanager/ {

    internal;

    root /home/bitrix;

}



location ^~ ^/upload/(.*)$ {

    proxy_method GET;

    proxy_set_header X-Real-IP $remote_addr;

    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_set_header X-Forwarded-Server $host;

    proxy_pass https://blissinhome.com/upload/$1;

}

location ~ ^/upload/(.*)$ {
    proxy_method GET;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Server $host;
    proxy_pass https://blissinhome.com/upload/$1;
}

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} \.(gif|jpe?g|png|ico)$
RewriteRule ^(.*)$ http://example.com/$1 [R,NC,L]

RewriteRule ^(.*)$ /bitrix/urlrewrite.php [L]

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} \.(gif|jpe?g|png|ico)$
RewriteRule ^(.*)$ http://example.com/$1 [R,NC,L]

RewriteRule ^(.*)$ /bitrix/urlrewrite.php [L]

ps -lax | grep cron_events.php | grep -v grep | awk '{print $3}' | while read PID ; do kill -9 $PID ; done