Posts made by QuixoticJustin

We hit the update right during a run cycle of the scheduler. So fifteen minutes till we see a first run and over half an hour till we have an idea of how well the fix worked.

Edit: wrong thread. Moved to the Sodium update.

Been very happy as a Zimbra user. Straightforward to use for sure.

Deploy is done. Fingers crossed, this is a big one.

We've been fighting with a scanning bug all week. Got a potential fix for it rolling out today. Fingers crossed that we got it fixed on the first production try. This is an odd one that has been a big stumper and causing no end of performance issues.

Yeah, lots of cleaning up needed for the patch system. It is early and mostly works, but leaves a lot to be desired yet

We are working on a design for a patching dashboard that will give a lot more power specifically around patching.

New NodeJS updates are speeding things up too, I would reckon. They've gotten the platform sped up a bit in the last few months.

And it's official! Okay, not official, there is no downloadable installer yet. But, SS is working on Mac OS. We have our first install and it went pretty smoothly. Was all manual, but worked great. Requires HomeBrew which is not ideal, but not a big deal, either. We will likely make different versions of the installer or something like that, in the future. For now, though, a HomeBrew managed install is simple and working. We might have an installer built and out by the end of the weekend.

Doing some Mac testing this morning. We are very anxious to add Mac support to the list. That's our one large platform hurdle at the moment.

@danp said in Sodium: Apply Updates:

@quixoticjeremy Adding an indicator that a restart is needed would be nice.

Good idea. And then, a button to enact said restart, as well. Or to schedule it.

@stacksofplates said in Learning Git:

@quixoticjustin said in Learning Git:

@stacksofplates said in Learning Git:

@quixoticjustin said in Learning Git:

@stacksofplates said in Learning Git:

@scottalanmiller said in Learning Git:

@matteo-nunziati said in Learning Git:

@scottalanmiller said in Learning Git:

@jaredbusch said in Learning Git:

@tim_g said in Learning Git:

I use VS Code with GitLab.

I need to install VS code. on my desktop. been hearing you two complement it.

It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.

@stacksofplates said in Learning Git:

@jaredbusch said in Learning Git:

@tim_g said in Learning Git:

I use VS Code with GitLab.

I need to install VS code. on my desktop. been hearing you two complement it.

It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.

matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.

I generally use the command line too for GIT. Just so quick and easy, and works every time.

I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.

Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.

I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible

With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".

True. I usually don't alias much. But I think we are at the point where you are writing things to get the cli at the same speed as what's in the applications.

I've not found any application that comes close in speed to the "up arrow, hit enter" speed of the CLI, though.

@stacksofplates said in Learning Git:

@quixoticjustin said in Learning Git:

@stacksofplates said in Learning Git:

@scottalanmiller said in Learning Git:

@matteo-nunziati said in Learning Git:

@scottalanmiller said in Learning Git:

@jaredbusch said in Learning Git:

@tim_g said in Learning Git:

I use VS Code with GitLab.

I need to install VS code. on my desktop. been hearing you two complement it.

It's like Atom but with some benefits (and drawbacks.) If you like Atom and use it mostly for coding, VS Code might be the right choice for you.

@stacksofplates said in Learning Git:

@jaredbusch said in Learning Git:

@tim_g said in Learning Git:

I use VS Code with GitLab.

I need to install VS code. on my desktop. been hearing you two complement it.

It's pretty nice. The built in Git stuff is nicer than Atom. To me it feels faster than Atom also.

matter of taste: I've used both for coding (mostly python) and I prefer Atom. As far as git is concerned I feel constrained with both and I go straight to cmd line.

I generally use the command line too for GIT. Just so quick and easy, and works every time.

I find the integrations in the apps quicker for normal commits. Don't have to switch between the app and a terminal (or even switch to a terminal in the app). The shortcuts are quick, and auto-complete as you type. I've never not had it work.

Quake style terminals are perfect for this. Hit a hot key, terminal is in your face, commit, hotkey and it is gone again.

I use the drop down terminal extension for GNOME3 a lot. I'm just lazy and like typing as little as possible

With a tiny BASH wrapper, you could have essentially no typing at all. Something like "gitcom these are my changes" and it submits for you. Or just alias it to "g".

Hopefully soon-ish there will be workflows for things like ticket closings so that there can be customer defined actions, checks, or whatever when something like that happens.

Long term, as Jeremy implies, loads of filters and views are expected, everywhere in the system. It's not at the top of the list, but it gets higher and higher all of the time as it impacts a lot of basic usability. The system is heavily designed around filters and views being key components of how it all works, both user accessible and behind the scenes.

For example, we want to easily support use by normal users, individual companies, consultants and MSPs. But we don't want to the system to actually work differently, just look different for different people. For example, individual home users likely don't even want to know that there is ticketing. But an MSP might want is very much in the forefront. It will be a view engine making that all possible.

@jaredbusch said in What Are You Doing Right Now:

Art Museum trip canceled. Vehicle decided it needed to visit the shop.

That's too bad. Hope nothing major.

@minion-queen said in Minion Queen client is searching for: JavaScript Developer:

Experience with Node.js and modern build stack including Gulp, Babel, NPM, and Webpack

None of these are part of a development stack. These are all dev side tools. I think the term "stack" might not be understood here.

@quixoticjeremy said in Sodium Update:

@danp Haha I'm sure there will be new features today but nope not yet. Data collection took priority this morning. I did get some things cleaned up but I haven't created a release yet.

Well, you missed that target

Rumour has it, though, we should have some big updates coming in just a few hours.

@jt1001001 said in What is everyone using for basic ticket management these days?:

SodiumSuite I'm keeping on our back burner to look at moving our I-T department to.

Give it a little bit, it's getting quite usable, but still very ugly, for tickets. That will change very soon. Some major changes coming this weekend. From looking at time table estimates, my guess is that you will see a major overhaul that will boost the helpdesk usability dramatically in about two weeks.

@darek-hamann said in What is everyone using for basic ticket management these days?:

Just made a switch from Jira to ZenDesk here - smooth as butter.

Did ZenDesk import Jira data? ZD is certainly one of the better products out there. We've obviously looked at a lot, given that we are trying to make something competitive. ZD isn't cheap, but it does a great job.

Jira is super confusing. Mostly because it is meant to be a project management tool and people either just use the PM tool for ticketing, or they get Jira's ServiceDesk extensions, but those are just interface layers on top of the PM tools. Not being purpose built for ticketing makes Jira a difficult tool to use for that purpose.