fastn scripts

[amitu]

Note: fastn xtask crate is how we can implement this.

Every fastn powered app is going to need some common scripts etc, how much can we reduce that by adding some basic stuff in fastn is the topic / motivation of this discussion.

fastn launchers

Our main scripts are fastn launchers, e.g., run-ui or run-template, they cd into respective folders, as a single repo often contains multiple folders.

We can reduce that need by doing fastn <app> where <app> may be lets-auth.fifthtry.site, without even needing to write the entire name out. So eg if fastn <unknown-word> is used, we cd into the <unknown-word> and do fastn serve from that folder.

Automatic Wasm Compilation

If the current folder has a folder named backend, or Cargo.toml etc, we run cargo build from backend folder or current folder, depending on presence of backend folder.

We do not optimise wasm as it does not make sense to do that on dev machines most of the time.

Github Actions

If we have a github action, fastn-release or something, it can check if file in any of the packages in current folder has been modified, of so it does fastn upload from that folder. It automatically sets rust-cache github action.