Alex Kuklofonov kuklofon

## bitrix:news.sections.elements.md

      
              1 file
            
          
              6 forks
            
          
              2 comments
            
          
              6 stars
            
          
                if0rest
                / bitrix:news.sections.elements.md
            
            
              Last active
              April 1, 2024 17:36
            
              
                Совместный вывод разделов и элементов в bitrix:news.list.
              
          
    ВЫВОД РАЗДЕЛОВ И ЭЛЕМЕНТОВ В bitrix:news.list

Часто возникает необходимость вывести разделы инфоблока с элементами на одной странице. Для этой цели подойдет связка catalog.sections + news.list. Или можно обойтись одним bitrix:news.list, немного кастомизировав шаблон компонента. Пойдем вторым путем.
Итак.

Размещаем компонент bitrix:news.list на целевой странице.
Копируем шаблон компонента в текущий шаблон сайта.
Создаем в нем файл result_modifier.php с таким содержимым.


## proxmox-proxy
I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.

What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.

Network configuration

Here’s how it’s done:

Create a virtual interface that serves as the gateway for your VMs:

## proxmox_lxc_pct_provisioner.sh
pct create <id> /var/lib/vz/template/cache/centos-7-default_20170504_amd64.tar.xz \
    -arch amd64 \
    -ostype <centos|ubuntu|etc> \
    -hostname <hostname> \
    -cores <cores> \
    -memory <memory(MB)> \
    -swap <swap(MB)> \
    -storage local-lvm \
    -password \
    -net0 name=eth0,bridge=<bridge>,gw=<gateway>,ip=<cidr>,type=veth  &&\
	I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.

	What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.

	Network configuration

	Here’s how it’s done:

	Create a virtual interface that serves as the gateway for your VMs:
	pct create <id> /var/lib/vz/template/cache/centos-7-default_20170504_amd64.tar.xz \
	-arch amd64 \
	-ostype <centos\|ubuntu\|etc> \
	-hostname <hostname> \
	-cores <cores> \
	-memory <memory(MB)> \
	-swap <swap(MB)> \
	-storage local-lvm \
	-password \
	-net0 name=eth0,bridge=<bridge>,gw=<gateway>,ip=<cidr>,type=veth &&\