@scottalanmiller said in What Are You Doing Right Now:

trying to support a customer in Qatar and it turns out they can only buy 10/100 switches (at least they aren't hubs) in the country. This is making the US seem downright modern by comparison. I didn't know any country was left that was this far behind on tech.

That's impossible. They must have supply chain problems or looking at the wrong thing. A lot of rugged switches are still 10/100 for instance.

Qatar has one of the highest GDP in the world.

@jt1001001 said in Printer Recommendations??:

@Pete-S HP MMFP 477 they were here before I started; frequent roller issues causing problems with paper jams

Yeah, it's probably too light duty for the job. It has recommended max volume of 750 to 4000 pages per month.

I have it's slightly smaller MFP brother, the HP MFP M281 on my desk and I wouldn't want to use that one for anything more than the occasional print job. So I'd aim at the lower end of HP's recommended volume.

I think you need to step up one or two sizes.

@jt1001001 said in Printer Recommendations??:

@Danp Oops sorry all should be 5000 pages/month B&W.

Which models are you using today?

@JasGot said in Slack? What is it?:

@Pete-S said in Slack? What is it?:

If you want automatic calendar reminders to go out then it's not what you're looking for. Then you want something that can integrate with Skyetel's SMS API directly.

This doesn't exist and I am not building one.

Why does it have to be Skyetel? If it's just a reminder, like "don't forget your dentist appointment tomorrow" the number used doesn't matter.

All the automation apps (like zapier, microsoft flow etc) doesn't require you to program a single line of code. You just set up the trigger and what action to take and you're done.

Some booking apps also have direct support for SMS reminders and in that case you don't need any external automation. Microsoft Bookings for example if your customer is Microsoft-centric. I have no experience with Bookings myself.

@travisdh1 said in Printer Recommendations??:

@Danp said in Printer Recommendations??:

@jt1001001 said in Printer Recommendations??:

High volume (500 pages/month B&W)

Is that really considered high volume? Personally, I would put that in the low volume category.

I agree, high volume would be more like 500 pages per day.

That said, I've had good luck with Xerox's solid ink printers in the past. ~2 million pages in 2 years with them at a previous job. Xerox ColorQube 8700 or 8900 are the current multifunction models.

A lot of printers have printer duty cycle in the specs. So you can get the right type of printer for the job.

Something like a HP Laserjet Pro M400 series has recommended max volume of 750-4000 pages per month.

@JasGot said in Slack? What is it?:

@Pete-S said in Slack? What is it?:

What @flaxking is trying to say is that you DON'T want Slack. Normally calendar reminders over SMS is something that is fully automatic once it's in operation.

How can you say that when you don't know what the requirements are?

Because you said: "The sole purpose for looking at Slack for this customer is to send appointment reminder vis SMS using Skyetel's "Postcards for Slack" feature."

I just assumed those were the requirements and if there were other requirements that were relevant, you would have mentioned them.

Appointment reminders are very common, almost SOP in some businesses.

@JasGot said in Slack? What is it?:

@flaxking said in Slack? What is it?:

At it's core Slack is a chat app. Think Teams without video calls or SharePoint integration.

It's also kind of treated like a shared mailbox. I.e. a channel will get sent alerts, and that's how people get notified and can talk about it right at the alert.

"ChatOps" is kind of the next step here where with integrations and bots, you can trigger actions from right within Slack. A benefit of this is that the log of the action and the conversation surrounding it is all logged in the same place. Someone looking back at what was done could see the whole history of events (alert raised, talk that something should be done about it, and the action being done triggered and recorded right there)

I have never heard of Slack being the only interface for something except for internal tools. It makes the most sense to use it for integrations when you're already having conversations there, but maybe the benefits of having the action log and the ability for different people using the integration to leave notes in the chat could mean it could be worth it to use if there are not other tools that does the same thing.

Thank you. This answer is exactly the info I was hoping to hear. It looks like Slack will work great if we choose NOT to use another full service sms reminder provider.

For example, we are comparing what Slack can do for us with ClickSend, TextBetterInc, Text-Em-All, and SimpleTexting.

What @flaxking is trying to say is that you DON'T want Slack. Normally calendar reminders over SMS is something that is fully automatic once it's in operation.

Skyetel's Postcards for Slack is the ability to chat (send and receive) SMS and MMS from your Skyetel phone numbers, using Slack as the UI.

https://support.skyetel.com/hc/en-us/articles/4402279765911-Postcards-for-Slack

If your customers wants to chat over SMS that might be the right thing. If you want automatic calendar reminders to go out then it's not what you're looking for. Then you want something that can integrate with Skyetel's SMS API directly.

What is Postcard? I thought SMS postcards was SMS mass marketing?

Anyway, appointment reminders are just transactional SMS.

There are plenty of SMS services that can send whatever SMS you want and have their own APIs. We use Clickatell for instance.

You can also trigger SMS services from apps like Zapier, Zoho Flow and many other integration apps without having to code anything. Basically connecting calendar events with the SMS API.

For example have Zapier send SMS reminders for google calendar events:
https://zapier.com/apps/sms/integrations/google-calendar

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

deb http://deb.debian.org/debian bullseye-updates main contrib

If you just want to get past the error, you can change the above line to:

deb [trusted=yes] http://deb.debian.org/debian/dists/bullseye-updates/InRelease

I think you might end up with another error instead though. Because I don't think it's the actual problem.

Right, I think that the CDN is blocking this for some reason.

Go to the bottom of the page and you'll find all official debian mirrors all over the world.
https://www.debian.org/mirror/list

Pick a mirror and see if you can access the InRelease file from the server. Then you can change the /etc/apt/sources.list and then run apt update again.

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

deb http://deb.debian.org/debian bullseye-updates main contrib

If you just want to get past the error, you can change the above line to:

deb [trusted=yes] http://deb.debian.org/debian/dists/bullseye-updates/InRelease

I think you might end up with another error instead though. Because I don't think it's the actual problem.

You should probably check that you can get to the repository at all from that machine. It could potentially be a repository problem.

For example using wget or curl fetch this file:
http://deb.debian.org/debian/dists/bullseye-updates/InRelease

It's the first file that apt is trying to fetch.

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

Updated, but same issue...

deb http://db.debian.org/debian bullseye main contrib
deb http://deb.debian.org/debian bullseye-updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

# security updates
deb http://security.debian.org/debian-security bullseye-security main contrib

Ah, it's proxmox. If I remember correctly they started to use Debian 11 before it became Debian stable. It should probably not matter though.

When I look at debian gpg keys (apt-key list) on Debian 11 in front of me, it looks like this:

Do you have the same three Bullseye keys?

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

When doing an "apt update", getting this error on Debian 11 Bullseye..

The repository 'http://ftp.debian.org/debian bullseye-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

We have the GPG keys, and the initial install was fine. This is a system that has been in production for a while. How do we get it to accept these repos?

It's not hard to get past that message. But the real question is why you get it. Something has to be wrong.

Maybe it's because Bullseye is stable now.

What does /etc/apt/sources.list look like?

I don't think so. I have scores of these servers with the same package list. But most don't have this issue.

It's also strange that you have ftp.debian.org as repository when deb.debian.org should be the default.

If you use the latter you will be fetching files over a CDN.

I wonder if this is a clean bullseye (debian 11) install or has it been updated from buster or earlier?

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

When doing an "apt update", getting this error on Debian 11 Bullseye..

The repository 'http://ftp.debian.org/debian bullseye-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

We have the GPG keys, and the initial install was fine. This is a system that has been in production for a while. How do we get it to accept these repos?

It's not hard to get past that message. But the real question is why you get it. Something has to be wrong.

Maybe it's because Bullseye is stable now.

What does /etc/apt/sources.list look like?

I don't think so. I have scores of these servers with the same package list. But most don't have this issue.

It's also strange that you have ftp.debian.org as repository when deb.debian.org should be the default.

If you use the latter you will be fetching files over a CDN.

@Pete-S said in Debian Packages Not Trusted, APT Linux:

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

When doing an "apt update", getting this error on Debian 11 Bullseye..

The repository 'http://ftp.debian.org/debian bullseye-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

We have the GPG keys, and the initial install was fine. This is a system that has been in production for a while. How do we get it to accept these repos?

It's not hard to get past that message. But the real question is why you get it. Something has to be wrong.

Maybe it's because Bullseye is stable now.

What does /etc/apt/sources.list look like?

@scottalanmiller said in Debian Packages Not Trusted, APT Linux:

When doing an "apt update", getting this error on Debian 11 Bullseye..

The repository 'http://ftp.debian.org/debian bullseye-updates InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

We have the GPG keys, and the initial install was fine. This is a system that has been in production for a while. How do we get it to accept these repos?

It's not hard to get past that message. But the real question is why you get it. Something has to be wrong.

@PhlipElder said in Manage domains and DNS for customers?:

@JaredBusch said in Manage domains and DNS for customers?:

@Pete-S said in Manage domains and DNS for customers?:

Is there a good way to manage domain renewals and DNS settings on behalf of a customer?

Basically handle everything and then invoice the customer. But the customer should still legally own the domain(s).

Anyone granted access to log in to the registrar can become the sole owner by transferring the registration to someplace that no one else has access to.

Without any legal contracts stating clearly how it all works, the legal owner is whoever is paying for it. That would be you, not them, in the scenario listed.

IANAL, but barring things like previously trademarked names, a company would likely not win (assuming cost of litigation is not an issue) in court if you said they did not own the right to their domain registration.

We actually put it in writing that we are managing their Internet properties and services and that ownership of said properties are theirs. If they decide to move on, it's in the contract that they would pay the fee(s) for the transfer out with the unlock codes presented once that process was initiated.

OK, so if you work with a new customer you will transfer their domains to your registrar and account? And then you can take care of everything - renewals, dns settings etc.

When the relationship ends, you will transfer their domain back to a registrar of their choosing.

Is there a good way to manage domain renewals and DNS settings on behalf of a customer?

Basically handle everything and then invoice the customer. But the customer should still legally own the domain(s).

@scottalanmiller said in I Cant Even...:

I love dealing with someone who has a DEGREE in Cybersecurity, claims to be an experienced system administrator, yet doesn't even know what an SPF record is for email and leaves it blank - even after being taught how to do it. And then puts the wrong data in from the wrong vendor because they don't know how to follow directions or what it is for.

It's fun stuff for sure. We do a hard bounce on all incoming email with SPF failures. Wish Microsoft and Google would do that too, because it's a wake up call for people.

@Obsolesce said in GitLab Now Integrates VS Code Into the Browser:

@Pete-S said in GitLab Now Integrates VS Code Into the Browser:

@scottalanmiller said in GitLab Now Integrates VS Code Into the Browser:

This is a really cool update to GitLab. Microsoft's VS Code is now the web IDE used online in GitLab. So you can use VS Code without needing to install it. This is the coolest!!

That's interesting.

Editing on the webserver breaks the idea of how git is suppose to work though. Basically makes it a central version control and repository, instead of a distributed one.

Good to know that it exists though!

Of course, it totally depends on what you're working on. Now that that's out of the way...

You can still do a lot the same as far as branching and PRs. If you're not compiling or testing things locally or need local resources, then there's not much other benefit doing it on your local PC versus some more simpler editing directly, besides some efficiency factors. But that other stuff should be done automatically anyways when you (for example, create a PR) via automation / pipelines.

If I need to fix something real quick and don't have my local environment ready or for whatever reason, it seems nice to not have the typical shitty editor like GitHub has, and I can easily create a new branch and make the changes, create a PR, and get it merged in in the end. It's not a bad thing to be able to do it from the browser, the same as you would from your local environment in VSCode (if what you are doing works out that way). All the testing, cleanup/linting, security checks, building, etc. should be kicked off automatically anyways no matter from where your changes come from.

Thanks for your post.

I think it's better to consolidate processing power in the datacenter than in the workstations so I never do anything local. Have any number and size of VMs I want at my disposal. From the perspective of git though I'm using a local repository.

It's clear to me that it's not how the majority are setup though.

I actually have a number of pain points using git and gitlab in this kind of setup.