cool.
cool.
pipeline schedules. once a month I clone the remote repo into a local branch, and push it back to my repo with an automatic merge request assigned to me. review & merge kicks off build pipeline.
I also use pipeline schedules to do my own ddns to route 53 using terraform. runs once every 15 minutes.
also once a week I’ve got about 50 container images I cache locally that I build my own images from.
someone got their Egyptology degree from Queen Cleopatra.
Egypt was actually pretty well mixed between lower Saharan Africans, Greeks, Turks, etc. that’s because Egypt was a trusted trade route between many successful economies around the Mediterranean sea.
self-hosted gitlab.
I love it. I can clone external repos on a schedule and build my projects based on my local cache. I’m even running some automation tasks like image deployments out of it too.
my first 1tb drive was Seagate.
after a firmware update bricked it I swore off Seagate for life.
I would rather eat a pound of my own shit before I’ll use a Seagate ever again.
I’ve bought used SAS drives from ebay. was running them in a raid10 until about a month ago when I retired the server.
ran for about 5 years on them no problems.
I do agree, there are risks buying any tech used, especially for servers.
are we talking shooting up in an old abandoned factory bad, or “mom help I got my dick stuck in a fish.” bad?
as a full stack dev, everything you said has offended me.
port 20 is used for FTP, unless you were using FTP, then go right ahead. Guessing that since you didn’t know the protocol you were not using FTP.
port usage reservations are incredibly important to ensure that the system is running within spec and secure. imagine each interface like a party telephone line and the ports are time slots.
your neighborhood has reserved specific times (ports) for everyone to call their relatives. if you use the phone not in your slot (port) your neighbors might get pissed off enough to interrupt your slot. and then it’s just chaos from there.
the government does, and what they do with it is harshly regulated.
the TSA is part of DHS but operates outside of DHS and can do whatever it wants with your information if you give it freely. it’s one of the reasons how that facial recognition apparatus works. it was developed by a contractor to USDOD and delivered to DHS for the TSA to use on the public.
DHS cannot investigate the general public without probable cause, TSA can. so what information they gleam from the general public is then shared with DHS, DOD, and sold back to the contractor as a part of the delivered contract. what they do with it afterwards is entirely up to them.
both accepting and rejecting the scan is harmful to your privacy. by accepting you are now indexed in a database and that information can be used in multiple government sanctioned investigations. by rejecting it, you are flagged as a concern and your profile is then processed through and algorithm to identify your threat level.
the TSA are doing more than just looking at your passport when you reject. they’re waiting on that threat level response to identify if you should be taken for further questioning.
it’s a data collection point.
can’t scan AI recognition on your passport, so they get your consent this way and with an updated photo.
it’s the only thing that makes sense if they’re taking photos and checking passports.
yeah, r*st.
flour and water paste should work pretty well as long as there’s no wax or tape to block the paper bonding.
in your defense Amazon would spray their boxes with poison if it didn’t add any extra costs.
PSA: Companies couldn’t give a shit about you or your packages. the sooner you realize that, the sooner you’ll realize how insignificant you are in the world.
congrats, you’ve had a far better experience than I have. just because you haven’t had the joys of experiencing Jira in its true form doesn’t negate the atrocious UX many others have. if Jira was the perfect product that you claim, then why is there so much vitrol and hate for the product at all?
I started my career as a big supporter of Jira. It made the work so easy to manage and report on. then sometime in 2020 an update came through that absolutely shit on my already over-burdened workload.
I used to deal with the sprint problem every kickoff, and yes I did select migrate to new sprint. no it doesn’t work when the process breaks in the middle and doesn’t recover or rollback. now I don’t handle kickoff, so not my problem anymore but I witness it happen literally every kickoff.
I also used to deal with the WYSIWYG issue daily. now I don’t post updates to cards outside of one-liners like “check the logs at this time” or “fixed upstream in xy branch”.
I get why people share their hate online because misery loves company, but I just don’t get why anyone would waste so much effort on defending it. example; I use spaces over tabs. lots of hate either way online. never have I defended or argued over one vs the other. it’s a preference much like Jira. forced to use it at work and have to make the best of it.
so, why be a white knight for Atlassian if you’re not employed by them? and if you are employed by them, why be so dismissive about the issues brought up?
Jira is great software if you ignore all the insufferable bugs in it that Atlassian ignores just to make their on-prem option so clunky you have no choice but to use their SAAS offering. I know, I know, “ThEy DrOpPeD sUpPoRt AlReAdY!”
ever had to rebuild a sprint because Jira failed to properly migrate the old cards over to the new one, but instead throws them all into the backlog randomly and now you have to hunt them down over the next hour?
how about when you’re writing an update to a card and you’re two paragraphs in with log examples and the UI decides to dump your entire content when you accidentally click outside the wysisyg?
But how can I forget the worst one! have you ever had your session timeout while you’re writing a detailed bug report with screenshots, logs, and example data, and when you finally submit it you lose EVERYTHING because you need to login again and you can’t go back?
I have, and you know what, I’ll still use Jira because even the best trash can be better than the worst trash.
yeah, I’ll take a fat dump on shitty products all day long because the negligence of Atlassian product development is abhorrent and deserves to be called out.
I absolutely love how this implies that the team is happy before going to Jira.
so not only can Atlassian not write software, they can’t develop a usable product, and they can’t even market it without insinuating how shitty it is.
I would recommend it. Speaking from personal experience, I trusted my VPN connection to remain on and self-heal. Thinking that cost me a strike against my ISP.
Now I know for a fact that if anything goes wrong with the VPN connection, all the containers that need it will need to restart before they have connectivity again and that can only happen after the VPN container restarts and passes healthcheck.
I love this plan!