setup/configuration issues on apple m3

[michaeljabbour]

Describe the feature

installation and use is unnecessarily complex

Potential Solutions

-simple terminal or terminal docker deployment
-models should be a drop down
-keys.cfg should be in the repo with correct permissions and format
-ability to set API configs and test in the interface
-graphical connections to github to identify correct repo and branch
-ability to address port conflict if something is running on 3000, 3001, etc.

[klieret]

That's a lot things for one issue, but thank you for the suggestions ;)

Regarding the web GUI: We currently don't have enough personpower to work on improving this. Though I would probably accept simple PRs to improve things.

Therefore I'll have to close this issue.

-simple terminal or terminal docker deployment

We do have a terminal interface if that's the question.

The port thing is #550 (you can switch the port of the frontend, but not of the backend atm)

[michaeljabbour]

Hi @klieret - I'm happy to contribute code to support these changes over time if that is of interest.

[klieret]

Awesome! I think from my POV, #550 would be important.

-keys.cfg should be in the repo with correct permissions and format

Don't want to do that, because people (or me) might actually commit it to the repo which is dangerous.

-graphical connections to github to identify correct repo and branch

Not sure if this is worth the added complexity

-models should be a drop down

This is a little bit annoying at the moment, because models.py is a bit of a mess. I think it would be more important to do something like #64

-ability to set API configs and test in the interface

Not sure what that means. You mean for configuring the model?

But anyway, regaring model config, I don't think people switch that around too much, so I don't think it's worth putting effort into the GUI for that. I think it's acceptable to set up a keys.cfg once.

We want to keep the GUI as lean and simple as possible for now.