Add local dev command to run backend and plugin

[dsimansk]

Changes

• Add local page cmd to view

GitHub Pages local development - fetch('plugin.yaml') always fails locally because plugin.yaml is only generated by the CI workflow (helm template). Add a way to test the GitHub Pages site locally (e.g. a script that generates plugin.yaml into the pages directory, or a local dev server setup).

@matejvasek @twoGiants is this somewhat coming closer to the idea stated above?

[dsimansk]

After spending some time with local dev setup on CRC, I'm rethinking the very simple approach of separate command. I see it needs to be properly wired into local dev loop.

[twoGiants]

Nice, going into the right direction! I'd just move it to the init script. See my comments below.

[twoGiants]

We're having an init.sh script which starts everything. This script won't work when init was run before, the ports are the same.

Maybe you can wire it all up in the init.sh script, so the pages assets are build every time we start the development environment?

[twoGiants]

Can you update the entire Option 1 (rename to Setup) section to say that init.sh should be used to start the dev env?

A few more things:

• Remove the sections:
  • #### Running start-console with Apple silicon and podman
  • Option 2: ...
• Add a small section in the Readme telling how to view the github pages locally.
• Add go and helm to the prerequisites.
• You could make the plugin.yaml generation optional in the init.sh script, then go and helm will also be optional.

[twoGiants]

You probably should ignore those too:

• backend/static/plugin.yaml
• backend/static/index.html

[dsimansk]

Good catch, it's leftover from my experiments. I'll clean it up.

[twoGiants]

Just curious, why are those two added?