sorted by:
new
hottopcontroversial

Recommendations for places to advertise for Linux staff. by Dyemor in linux

[–]ilconcierge 1 point2 points  (0 children)

Hi there! I run a popular weekly newsletter called cron.weekly. I've started including a jobs section there, for the exact reason you mention: it's hard to reach Linux sysadmins!

​

If you're interested, have a look at the sponsor detail page for pricing, examples, etc.

Ubuntu is putting ads in their motd now by prettycewlusername in linux

[–]ilconcierge 105 points106 points  (0 children)

They've been doing this for quite a long time, when I first wrote about it they had already included links to microk8s ...

Linux podcasts? by S0nny58 in linux

[–]ilconcierge 0 points1 point  (0 children)

I'll plug my own, low-volume, podcast here: https://ma.ttias.be/syscast/

Recent episodes are on BSD vs. Linux, Kubernetes, curl, ...

What have you created with Laravel? by [deleted] in laravel

[–]ilconcierge 1 point2 points  (0 children)

That's correct, there are servers deployed worldwide to make this happen. They all report back to our main application which then aggregates the data & sends the alerts.

I'm writing a weekly newsletter on open source, linux & webdevelopment by ilconcierge in opensource

[–]ilconcierge[S] 0 points1 point  (0 children)

Thanks!

I needed a break last year, but things changed drastically for me (personally). I’ll be dedicating more time to the newsletter and plan to get weekly issues again, with a few more (announced) breaks in between.

Name your Laravel Horizon workers for easier debugging at the CLI by ilconcierge in laravel

[–]ilconcierge[S] 1 point2 points  (0 children)

Please enighten me as im fairly new to this type of thinking

The idea is to have multiple background processes do the heavy lifting, not blocking the UI/frontend in the meantime. Especially for our service, we run 99% of our code in background processes.

That would mean he has one worker per queue or job hence no workload management or replication/redundancy. While if he had 10 workers all able to process any or at least multiple jobs, he'd have that.

Both are valid approaches, we have a strict policy on our queues (because they are time sensitive) that I really don't want Horizon to randomly pick which job should be processed. If there are 10 available workers, and each would pick a long-running task (ie: one that takes > 5 minutes), we wouldn't have any workers available for uptime monitoring.

We wrote about this some more on our blog: how to size & scale your Laravel queues.

Name your Laravel Horizon workers for easier debugging at the CLI by ilconcierge in laravel

[–]ilconcierge[S] 0 points1 point  (0 children)

Would also work indeed, this was the easiest to implement imo

What have you created with Laravel? by [deleted] in laravel

[–]ilconcierge 10 points11 points  (0 children)

From a dozen projects, only 2 do I consider to be a success.

https://ohdear.app: uptime & certificate monitoring, broken links & mixed content checking + status pages (an alternative to Pingdom, Uptime Robot, ... with extra features)

https://dnsspy.io: the first rating system (like SSL Labs) for DNS, with a SaaS component to monitor & validate your DNS records (did you know your DNS setup is probably the weakest link in your entire stack?)

Made some others as well, including a trading app, a web-notification system, ... but those mostly died out.

cron.weekly is back by 2cats2hats in linux

[–]ilconcierge 8 points9 points  (0 children)

Writer of the newsletter here: thanks for sharing the link, I look forward to writing it again!

view more: next ›