I can help. Send me a PM.

@scottalanmiller said in Caddy vs. Nginx:

But they wouldn't see it, right? Because you'd still have CloudFlare in front of it. So while it gets an A, what does that matter?

I'm not using CF as a reserve proxy or origin certificates.

@scottalanmiller said in Caddy vs. Nginx:

@VoIP_n00b said in Caddy vs. Nginx:

@JaredBusch said in Caddy vs. Nginx:

Yes, I want various security headers set, etc.

Caddy gets an A out of the box on ssllabs.com

They are owned by them, so that's pretty sus.

About Qualys

Qualys, Inc. (NASDAQ: QLYS) is a pioneer and leading provider of cloud-based security and compliance solutions with over 9,300 customers in more than 100 countries, including a majority of each of the Forbes Global 100 and Fortune 100. The Qualys Cloud Platform and integrated suite of solutions help organizations simplify security operations and lower the cost of compliance by delivering critical security intelligence on demand and automating the full spectrum of auditing, compliance and protection for IT systems and web applications. Founded in 1999, Qualys has established strategic partnerships with leading managed service providers and consulting organizations including Accenture, BT, Cognizant Technology Solutions, Deutsche Telekom, Fujitsu, HCL, HP Enterprise, IBM, Infosys, NTT, Optiv, SecureWorks, Tata Communications, Verizon and Wipro. The company is also a founding member of the Cloud Security Alliance (CSA). For more information, please visit www.qualys.com.

They are no NTG, I'll give you that.

@JaredBusch said in Caddy vs. Nginx:

Yes, I want various security headers set, etc.

Caddy gets an A out of the box on ssllabs.com

@Dashrender said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@travisdh1 said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@scottalanmiller said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@travisdh1 said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@syko24 said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@scottalanmiller said in Changing Installation Location for MicroSIP Installed via Chocolatey:

By default, installing MicroSIP using Chocolatey causes the install to go to an inappropriate data folder location and is only available for the admin installing user, rather than for the end users of the Windows system. Does anyone have any experience or ideas in changing the installation location so that system users can actually use MicroSIP when installed and maintained using choco?

Asking for @Dashrender and @romo as well.

I think this might work:
choco install microsip -ia "'/D=C:\SomeDirectory'"

choco install microsip -ia "'/D=C:\temp'"

Did install it to C:\temp for me

Is it working for non-admin users?

Yep, I can run the .exe from my C:\temp. You'll probably have to create a shortcut for a user tho.

yep, I just tried it - I pushed to c:\program files\microsip

and non admins can run it.

and you're right, the shortcut is put on the installing admin's desktop, and nothing in the start menu.

MicroSIP - open source portable SIP softphone based on PJSIP stack for Windows OS.

https://www.microsip.org/

It says right on the website it’s a portable app, why would you expect a desktop icon or anything on the start menu?

@travisdh1 said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@syko24 said in Changing Installation Location for MicroSIP Installed via Chocolatey:

@scottalanmiller said in Changing Installation Location for MicroSIP Installed via Chocolatey:

By default, installing MicroSIP using Chocolatey causes the install to go to an inappropriate data folder location and is only available for the admin installing user, rather than for the end users of the Windows system. Does anyone have any experience or ideas in changing the installation location so that system users can actually use MicroSIP when installed and maintained using choco?

Asking for @Dashrender and @romo as well.

I think this might work:
choco install microsip -ia "'/D=C:\SomeDirectory'"

choco install microsip -ia "'/D=C:\temp'"

Did install it to C:\temp for me

Ah, so the documentation provided work

cloudns.net is good too

Youtube Video

@IRJ said in When Does It Stop Even Being IT: Buyers vs Doers:

Maybe I'm Scott

Maybe we all...

@travisdh1 said in Looking for a NC host for an Open Source project:

Would Wasabi be an acceptable host for said file? That'd be 8TB x $0.06 = $0.48/month to host the file. I would just make another bucket to store just it in, and make the file publicly accessable.

Wasabi has a $5 minimal monthly fee.

Also how do you plan to handle cooling?

This doesn't seem wife approved

Enjoy your $500+ power bill

@scottalanmiller said in Automated NextCloud Backup to Wasabi or Amazon S3:

It is indeed. It's running now.

How much data? How long is it taking?

Note: Use the -P/--progress flag to view real-time transfer statistics

@stacksofplates said in Reconsidering ProxMox:

If I snapshot a VM and copy the snapshot off somewhere else it's a backup.

Sure, agreed. But that's not what @scottalanmiller said.

@scottalanmiller said in Reconsidering ProxMox:

Yeah, just for some reason in that table it shows that you can't. My guess is that it is a typo, but I've not tested it so I can't confirm.

It's defiantly not a typo. I am the member of a proxmox user group, and someone just did a install with LVM and everything related to snapshots was grayed out. Then we figured out it was LVM and not LVM-thin. So regardless if it's "all the same" it matters to proxmox.

@scottalanmiller said in Reconsidering ProxMox:

We do, shouldn't, but we do because customers don't want to pay for better backups.

I am surprised NTG would take on a client like this. We sure wouldn't. The risk is too great. We just tell the client to take there business elsewhere. Maybe we are sending clients to you guys! =P

@scottalanmiller said in Reconsidering ProxMox:

You definitely can. We use that as the backing to our main backup tools on LVM.

Then your using LVM-thin. Maybe that's just a subset of LVM?

@stacksofplates You can't take snapshots on LVM. https://pve.proxmox.com/wiki/Storage

@scottalanmiller said in Reconsidering ProxMox:

LVM is what we use.

So you don't take snapshots?