Skip to content

Feature, Add Independant Versioning to LittleFS, Web Pages #576

@ForrestErickson

Description

@ForrestErickson

Is your feature request related to a problem? Please describe.
_A clear and concise description of what the problem is. Ex.

I'm always frustrated when there are changes with out versions visible to mark changes to which we can refer.
The Krake served Web page have no version.

Describe the solution you'd like
A clear and concise description of what you want to happen.

In response to: We are using the C and C++ language of Arduino framework. In addition our ESP32 application serves embedded web pages and I think the LittleFS file or files may need version identification independent of the ESP32 firmware.

An AI suggests:
To manage this setup cleanly, you should use two distinct SemVer tracking systems: one for your core ESP32 Firmware and one for your LittleFS Web Assets. Because the firmware and web pages have different development cycles and breaking change conditions, decoupling them prevents unnecessary, high-risk firmware reflashes when you only need to fix a typo on a web page.

Details including how to automate the build and versioning at:
https://share.google/aimode/tPWuPGt9TG7plB2mJ

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions