This seems, at best, some general security checks but not mapped to any framework in particular.
So. Yes. Ssh access should be passwords only, etc. Some common sense. We don’t need standard to that
UPDATE: sorry for the typo, meant passwordless
Thanks. This is going to be addressed here - https://github.com/melezhik/Sparrow6/issues/13
I probably need to add report example here …
Update - done in readme
I guess cause not every AI stuff is a bad and annoying thing .
Something started to happen to programming.dev see some posts with many downvotes but without any comments , so people don’t even bother to say what /why they don’t like , even in Reddit people usually comment even when they don’t like your posts and explain their point …
Update : or maybe this is just a c/programming tendency …
Example of dsci pipeline - https://forgejo.sparrowhub.io/root/test/src/branch/main/.dsci
It uses yaml only for configuration part, but pipeline itself is far more then that . Not sure what do you mean by “middle ground”, could you please elaborate? Thanks
Just added the feature of running jobs on localhost for debugging:
cd .dsci/job_one; docker run -it -v $PWD:/opt/job --entrypoint /bin/bash dsci -c "cd /opt/job/; s6 --task-run ."
deleted by creator
deleted by creator
Yep,I will figure out the proper design later , but thanks 😊
Oh, sorry for that, changed theme to light , hopefully better now
Feedback are welcome , the project is in very early stage …
Ok. Huge part of building microservices framework is infrastructure automation - like setup nginx load balancing in runtime, build and deploy apps from source code, configuring services, tcp ports, health checks, horizontal scaling (adding new worker nodes), setup logging and monitoring, etc, also this needs to be propagated to all cluster nodes, I am not going to do this from the scratch - Sparky is alike (rough comparison though) ansible but with UI and programmable on Raku, so as Sparky has already addressed the mentioned tasks, it’s logical for me to carry on with it. If we take Sparky out of equation, Raku by itself is reach and super flexible language to automate infrastructure, I don’t see why can’t I use it for that …
The plan is to build the entire system on top of Sparky which is written on Raku and extended by Raku
Typo )) sorry , meant password less