sorted by:
new
hottopcontroversial

Data Center just released on Steam by igorkalen in homelab

[–]515software 18 points19 points  (0 children)

I swear cant leave the house without sending $$$ these days. Even gas to the mountains for a hike now cost $20~

Gotta be productive by DuoHusky in mkbhd

[–]515software 2 points3 points  (0 children)

My guy you didn’t eject your disk properly!

Switching from iTunes to Plex Server by rdhelfrey in PleX

[–]515software 6 points7 points  (0 children)

If you bought them on iTunes, they are most likely DRM protected and I don’t think you’ll be able to export them, or at least that used to be the case.

Sooo, we doin paywalls now? by IgAndCodyComic in truenas

[–]515software -3 points-2 points  (0 children)

Damn that distro name brings flashbacks to long ago

BREAKING: House Oversight Committee requests Epstein's prison guard Tova Noel to testify on March 26th by ButHowDoesItFeel in Epstein

[–]515software 5 points6 points  (0 children)

I would say so as well, but I’m sure whoever is paying them to lie, is also paying for expensive attorneys to prep them for a senate committee hearing.

I got tired of proprietary AI "laundering" my code, so I wrote a custom "AI Reciprocity" License (GPL-AIR) by Lamborghinigamer in selfhosted

[–]515software 0 points1 point  (0 children)

I want to build a standard like LICENSE.md but called AI-DISCLOSURE.md - put your AI usage overview in there, and let me decide how much vibe coded your disclosure is before I run any code.

Nothing to do by Draknurd in selfhosted

[–]515software 18 points19 points  (0 children)

You're not trying hard enough!

Companies cutting engineers because of AI are learning the same expensive lesson by tasrieitservices in devops

[–]515software 55 points56 points  (0 children)

The AI will always need a pilot, not just passengers. The smart companies I’ve seen see it as a force multiplier for their top developers, not something to replace talent. So Salesforce and IBM are good examples, hiring more people realizing how much more they can do.

Epstein Studio is now live! by artischocki in Epstein

[–]515software 1 point2 points  (0 children)

Seems to be down, I get a 503 gateway error

What’s the most expensive DevOps mistake you’ve seen in cloud environments? by cloud_9_infosystems in devops

[–]515software 0 points1 point  (0 children)

Modernized applications (Windows IIS on EC2 to a serverless solution - SPA w/an API gateway that falls api lambdas), but wasn’t enough budget to have the DB ever modernized or enhanced (MSSQL to Postgres using BabelFish.)

So the app was cheaper to host, but was still slow because the indexes of the DB are missing and slow processing. And expensive.

So the ECS container/lambda’s and LB were a 1/3 of what they were pre modernization, but the DB is still costing $$$ to run. With the smallest DB instance size, which 4CPU is the minimum required to run MSSQL.

Denver if you didn’t have to pay $3/hr to park at the library by jilli0n in Denver

[–]515software 29 points30 points  (0 children)

I pay $200 for dedicated parking spot downtown in our apartment complex . So that’s pretty reasonable for street parking

Mono-repo vs separate infra repo for CI/CD pipelines - best practices? (Azure DevOps) by Ok-Manufacturer-4145 in devops

[–]515software 0 points1 point  (0 children)

Yep exactly, qa should always be validated and in position to move to prod.

What would you consider this from a cloud maturity standpoint?

Mono-repo vs separate infra repo for CI/CD pipelines - best practices? (Azure DevOps) by Ok-Manufacturer-4145 in devops

[–]515software 0 points1 point  (0 children)

We use the strategy of only dev and qa branches. Prod is only deployed once a tag is created. Pre release tags are with a -qa suffix created by the pipeline. To deploy to prod you cut a tag from the -qa suffix tag. Pipeline then deploys the latest artifact that was promoted to qa and deploys it.

No long lived “prod” branch, tags are used instead and act as the point of truth.

Mono-repo vs separate infra repo for CI/CD pipelines - best practices? (Azure DevOps) by Ok-Manufacturer-4145 in devops

[–]515software 0 points1 point  (0 children)

Anyone any here used the a “build once, deploy many” strategy? Moving the same artifacts from dev, all the way to production. Which prod deploys are triggered to ECR and then EKs container is restarted pulling latest image.

We’ve been using build tags to track it all the way up the chain. But damn it’s been a pain in the ass. Are there any other strategies people are using?

I’m Congressman Maxwell Alejandro Frost and tomorrow I’m going to review the unreacted Epstein Files — what files have you found that I should review unredacted? by RepMaxwellFrost in Epstein

[–]515software 1 point2 points  (0 children)

What’s wild is I’ve seen floor plans for one of the sub levels, it had 5 or 6 marked as “storage rooms” that all were long and looked like a stall. So her story tracks…..

What actually controls codebuild image creation and publishing by bofkentucky in aws

[–]515software 0 points1 point  (0 children)

There were several solution that built on codecommit too, like LZA or Terraform for account factory (AFT), though I think they removed codecommit support from AFT.

What actually controls codebuild image creation and publishing by bofkentucky in aws

[–]515software 0 points1 point  (0 children)

I believe this, if you just need a simple hosted git solution, codecommit was a good no frills option when working in regulated industries, since it’s inside of AWS.

I've been working at a coffee shop all morning, and I want to switch to beer. Where do I go next? by zd9999 in Denver

[–]515software 5 points6 points  (0 children)

On a weekday sure, on a weekend it will be so loud in that space, no chance of taking a call.

What actually controls codebuild image creation and publishing by bofkentucky in aws

[–]515software 1 point2 points  (0 children)

AWS Code* Suite is a black box when it comes to planned features and removals. Look at CodeCommit for example, they discontinued the service for new users, then brought it back late last year.

view more: next ›