SaltShacker (SaltStack UI Free)



  • Hello,

    Just raising awareness of this project that caught my eye:
    https://github.com/yueyongyue/saltshaker/blob/master/README.md
    especially checking that screenshots. sadly the instructions are not very clear:
    https://github.com/yueyongyue/saltshaker/blob/master/install.txt

    But I hope I can manage to install this on server separate from the salt master, and have it functioning with good guide.

    Will keep you posted, and any help analyzing the instructions are welcomed.


  • Service Provider

    Oh wow, very cool!!



  • I'm very interested in seeing more about this!



  • LOL - here's the open source thing I was talking about the other day ;) J/K



  • Development appears to have stalled.



  • @danp said in SaltShacker (SaltStack UI Free):

    Development appears to have stalled.

    Considering it's open source - I wonder if the Sodium folks could use this code to jump start theirs?



  • @dashrender said in SaltShacker (SaltStack UI Free):

    @danp said in SaltShacker (SaltStack UI Free):

    Development appears to have stalled.

    Considering it's open source - I wonder if the Sodium folks could use this code to jump start theirs?

    I'd have to take a look, it looks to be written in python which we weren't using but that doesn't necessarily mean it can't be used. A lot of what they have we already have in development or have completed to some degree. In my few free minutes I'll take a look and see if there is anything salvageable here, which is entirely possible.


  • Service Provider

    @dashrender said in SaltShacker (SaltStack UI Free):

    @danp said in SaltShacker (SaltStack UI Free):

    Development appears to have stalled.

    Considering it's open source - I wonder if the Sodium folks could use this code to jump start theirs?

    That would only make sense if this lined up with the Sodium project goals, which it does not. This isn't an RMM tool, this is a Salt GUI. Sodium isn't a Salt GUI. This isn't a management tool. So while one does use Salt and one is a GUI for Salt, it looks like the overlap probably stops there.

    Developers know that picking up other projects generally means more work than starting over. Bootstrapping with old code tends to be counter productive, especially if the old code is not absolutely exactly what you need to use. If it's not using the languages, technologies, frameworks, authentication, coding styles, paradigms, licensing and such that is identical to what is needed in the new project it is likely to be an encumbrance rather than a boost.

    Even with bespoke software, NTG tends to start over from scorched earth every seven years or so because of developments in the industry and changes in direction making it cheaper and more effective to not even reuse our own code that we made in house and own completely internally and already know.



  • @scottalanmiller said in SaltShacker (SaltStack UI Free):

    @dashrender said in SaltShacker (SaltStack UI Free):

    @danp said in SaltShacker (SaltStack UI Free):

    Development appears to have stalled.

    Considering it's open source - I wonder if the Sodium folks could use this code to jump start theirs?

    That would only make sense if this lined up with the Sodium project goals, which it does not. This isn't an RMM tool, this is a Salt GUI. Sodium isn't a Salt GUI. This isn't a management tool. So while one does use Salt and one is a GUI for Salt, it looks like the overlap probably stops there.

    Developers know that picking up other projects generally means more work than starting over. Bootstrapping with old code tends to be counter productive, especially if the old code is not absolutely exactly what you need to use. If it's not using the languages, technologies, frameworks, authentication, coding styles, paradigms, licensing and such that is identical to what is needed in the new project it is likely to be an encumbrance rather than a boost.

    Even with bespoke software, NTG tends to start over from scorched earth every seven years or so because of developments in the industry and changes in direction making it cheaper and more effective to not even reuse our own code that we made in house and own completely internally and already know.

    Can I upvote this twice?



  • @scottalanmiller said in SaltShacker (SaltStack UI Free):

    Even with bespoke software, NTG tends to start over from scorched earth every seven years or so because of developments in the industry and changes in direction making it cheaper and more effective to not even reuse our own code that we made in house and own completely internally and already know.

    This is kinda of amazing actually. Could you imagine someone like MS starting Windows over every 7 years so they can be using the latest and greatest coding techniques? I'm guessing they would loose a lot of backward compatibility, but maybe not.


  • Service Provider

    @dashrender said in SaltShacker (SaltStack UI Free):

    This is kinda of amazing actually. Could you imagine someone like MS starting Windows over every 7 years so they can be using the latest and greatest coding techniques? I'm guessing they would loose a lot of backward compatibility, but maybe not.

    Don't they? NT 3 to NT 4 was only about three years. NT 4 to NT 5 was four years. NT 5 to NT 6 was seven years. Do they completely rewrite? We don't actually know. But they heavily rewrite. It's a major overhaul.

    If they lost backward compatibility, that would only be from products relying on broken parts of the old system, not the rewrite. Properly written software running on top would not be affected.

    Does Linux get rewritten like this? No. But huge portions of it are continuously refactored in this way or just left untouched.


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.