5 ms·

you do need to install cockpit on [all] your server[s], right? i am trying to figure out if there is a business case for a desktop app. there is plenty of ope

you do need to install cockpit on [all] your server[s], right? i am trying to figure out if there is a business case for a desktop app. there is plenty of open source and commercial systems more or less similar to cockpit, and it's hard to compete with free

johnchristopher 6y ago
I don't like having to install cockpit on every instance/devices. That means I have to keep all of them up to date in addition of installing them and configuring the devices to make it operable. I'd rather have a client-only app that connect through ssh and get its data from standard binaries installed on the server. So, yes. I'd give that a try.
- java-man 6y ago
  any specific feature that would motivate you to shell out fifty bucks? (half-joke)
  - johnchristopher 6y ago
    As a hobbyist that'd be hard to justify. At work I manage two standard LAMP servers only. So I am not really your audience. I think I'd like some kind of alerts on some specific events (disk space, some logs, IDK), systemctl management and status/reporting, some instantaneous “update as I type” filtering/searching in logs, cron and/or systemctl timer management, space usage graphics, booting reports, etc. ... maybe these are just things I usually do and think a GUI would be nice to have if I had to do it for multiple servers. Not enough experience with that in a professional setting though so take it all with a grain of salt. But as-is, I think I could justify asking for 50 bucks for the product if I needed it.
    - java-man 6y ago
      Thank you! Looking at the logs is how this tool was started. This in itself is a failrly involved chunk of functionality. It'll be a year, probably, before I can release even that.
dspillett 6y ago
> you do need to install cockpit on [all] your server[s], right? apt install cockpit Installation is not an issue, more is keeping it up to date package-wise. Little or nothing extra on to of having the tools and libraries it needs installed. So unless you have a _really_ compelling auto config system for common enough workloads I doubt there would be a large enough paying market. There could be a case for if using cockpit or similar was not possible due to policy rather than technical concerns (there aren't going to be many circumstances where someone who can't install cockpit has a SSH account with the privs required for your app to be useful much beyond monitoring). Perhaps there is a use case for people tentatively moving from shared hosting to having their own VMs/servers, so they can give your app the host address, user, and pass word/key & let it discover available resources & install what they need. But that is a market who notoriously won't want to pay for anything generally (they want the unlimited ride their last shared hosting provider promised but failed to deliver, for as little as that host or some chapter other is charging) but will bitch endlessly if there free moon-ona-stick isn't 100% perfect and 110% reliable.

johnchristopher 6y ago

I don't like having to install cockpit on every instance/devices. That means I have to keep all of them up to date in addition of installing them and configuring the devices to make it operable. I'd rather have a client-only app that connect through ssh and get its data from standard binaries installed on the server. So, yes. I'd give that a try.

java-man 6y ago
any specific feature that would motivate you to shell out fifty bucks? (half-joke)
- johnchristopher 6y ago
  As a hobbyist that'd be hard to justify. At work I manage two standard LAMP servers only. So I am not really your audience. I think I'd like some kind of alerts on some specific events (disk space, some logs, IDK), systemctl management and status/reporting, some instantaneous “update as I type” filtering/searching in logs, cron and/or systemctl timer management, space usage graphics, booting reports, etc. ... maybe these are just things I usually do and think a GUI would be nice to have if I had to do it for multiple servers. Not enough experience with that in a professional setting though so take it all with a grain of salt. But as-is, I think I could justify asking for 50 bucks for the product if I needed it.
  - java-man 6y ago
    Thank you! Looking at the logs is how this tool was started. This in itself is a failrly involved chunk of functionality. It'll be a year, probably, before I can release even that.

dspillett 6y ago

> you do need to install cockpit on [all] your server[s], right? apt install cockpit Installation is not an issue, more is keeping it up to date package-wise. Little or nothing extra on to of having the tools and libraries it needs installed. So unless you have a _really_ compelling auto config system for common enough workloads I doubt there would be a large enough paying market. There could be a case for if using cockpit or similar was not possible due to policy rather than technical concerns (there aren't going to be many circumstances where someone who can't install cockpit has a SSH account with the privs required for your app to be useful much beyond monitoring). Perhaps there is a use case for people tentatively moving from shared hosting to having their own VMs/servers, so they can give your app the host address, user, and pass word/key & let it discover available resources & install what they need. But that is a market who notoriously won't want to pay for anything generally (they want the unlimited ride their last shared hosting provider promised but failed to deliver, for as little as that host or some chapter other is charging) but will bitch endlessly if there free moon-ona-stick isn't 100% perfect and 110% reliable.