Initial EVS client + bridge setup

include/README

@@ -0,0 +1,37 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the convention is to give header files names that end with `.h'.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

include/secrets.example.h

@@ -0,0 +1,21 @@
+#ifndef EVS_SECRETS_H
+#define EVS_SECRETS_H
+
+// Copy to: include/secrets.h
+// Keep include/secrets.h out of version control.
+
+static const char* WIFI_SSID = "REPLACE_WIFI_SSID";
+static const char* WIFI_PASSWORD = "REPLACE_WIFI_PASSWORD";
+
+// EVS bridge endpoint
+static const char* EVS_BRIDGE_HOST = "REPLACE_BRIDGE_IP_OR_HOST";
+static constexpr uint16_t EVS_WS_PORT = 8765;
+static const char* EVS_WS_PATH = "/audio";
+
+// Unique device name per ESP32
+static const char* EVS_DEVICE_ID = "esp32-room-name";
+
+// Connectivity behavior
+static constexpr uint32_t EVS_RECONNECT_MS = 5000;
+
+#endif  // EVS_SECRETS_H