This is a template application with OTA capability, to be used with Espressif IoT Development Framework.

See also (component version): https://github.com/yanbe/esp32-ota-server

OTA capability is achieved with rather small binary and memory footprint.

With OTA template app, your build-flashing-monitor cycle become much easier and faster.

You have to flash via UART first, then confirm IP address (like 192.168.0.3) assigned to ESP32 via log output of make monitor with USB UART.

$ make menuconfig # configure "WiFi Configuration" menu on your network.
$ make erase_flash flash monitor

After that, you can use flashing capability with special make target

$ make ota ESP32_IP=192.168.0.3

ESP-IDF's OTA example project is a good starting point to understand how ESP32's OTA flashing works with official OTA suppoprt components. But it is pull architecture. You have to launch HTTP server on your PC every time, and wait ESP32 to update their program. It is not optimal in terms of speed up build-flashing-monitor cycle on developing phase.

My OTA template app push architecture. So you can flashing natural make command like berow.

$ make ota ESP32_IP=192.168.0.3

Additionally, in esp-idf-ota-template, OTA implementation is placed into components/ota_server so you can concentrate your project without be bothered by OTA-related socket programming code.