HN user

deepersprout

898 karma
Posts11
Comments52
View on HN
[dead] 11 months ago

They have awesome uptime for the resources they have, so I am looking forward to the post mortem.

I usually feed all the documentation to an llm and ask the question to the llm that fetches the info with rag. For example:

how do i configure Traefik to proxy traffic to two backend services?

Configuring Traefik to proxy traffic to multiple backend services is a common use case. You can achieve this by defining multiple entry points and routers in Traefik's configuration, each pointing to a different backend service. Here's a basic example of how you can configure Traefik to proxy traffic to two backend services:

  yaml
  
  # traefik.yaml
  
  # Enable API and Dashboard
  api:
    dashboard: true
  
  # Define entry points
  entryPoints:
    web:
      address: ":80"
    app1:
      address: ":8081"
    app2:
      address: ":8082"
[...more stuff...]
How I Backup 2 years ago

I do something similar[1] with rsync --link-dest and hard links, so that I can go back in time if I delete something. OP seems to just have a copy of his actual files, but if he sees a file missing after 2 weeks after deleting it, he has no way of recovering it.

[1]https://31337.it/incremental-backups-with-rsync/

From the moment the driver hit the gas pedal, everybody was on their phones. From the back row, I watched my friends scroll their social media feeds with ferocious intensity.

Sorry, but I think you should change friends. Or your friends have a serious problem with social media that you should help them overcome. There are tons of other interesting venues on the internet. This is one of them. And here you have articles from the past, as from the present. No need to live in The Never Ending Now.

The folder you copy your file (any file that has some importance to you) to should be a onedrive synced folder. Word/Excel/Powerpoint/... files you edit in a synced folder save automatically without the need for you to ctrl+s.

If you undo copy that file you will find it in your onedrive history.

Send an ajax request to your api with invalid credentials. The response returns a 401 and loggs the user out. Then redirect to the pre-login page.

I think this whole christmas thing makes a lot of people feel alone and depressed. I hate that. Posts like these make me think this even more. I am alone, and I like it. I can play Warzone and code some stuff I wanted to finish. I can do things I like. I know this may sound stupid, but if you feel alone, don't. There is no reason to. It's just a day like many others. There is really nothing to it.

And we don't need "Christmas" for a virtual hug. We can do that every day of the year.

No Cookie for You 6 years ago

GitHub still sends the same personal data to their own analytics endpoint

I see nothing wrong with that. Analysing your users on your own site is no problem for me. I should know what users do on my property.

What's the problem you have with that?

because police brutality is kind of a global phenomenon

No it's not. Police in Europe is, on average, very kind. When they stop you, you don't have to be afraid of anything, and more often than not you stop them to ask for help, even if it's just to ask for directions.

Some people like their sites to work with out javascript.

The 2020 solution to CSRF attacks is using `SameSite` cookies. That makes CSRF tokens obsolete. So if you can accept that old browsers may be vulnerable, you can just use `SameSite` cookies and be done with it.

A year after you release v1.0.0 (which you say is a tag), a customer reports a bug in it. They don't want a breaking upgrade to v9.13.0. They want to pay for v1.0.1 (aka "hotfix").

But you can't open a PR against a tag v1.0.0. Hence you discover that v1.0 should be a branch, and both v1.0.0 and v1.0.1 tags. This way you can open a PR against v1.0 and easily create v1.0.1, v1.0.2, etc.

So you could just `git checkout v1.0.0; git checkout -b v1.0`, commit your hotfix and deploy v1.0.1.

Another problem. You are at "master" and approach v13.0.0. But there are numerous bugs to fix before you release. Testing takes >24 hours. You choose to work on bugs on a branch (v13.0) this way master can proceed with new features and not be feature-frozen for days or weeks.

Or you could use topic branches for new features, and fix bugs on master at the same time.

Another problem. Your CI is deficient in that it allows merging and cloning before it makes sure that previous merge produced good product. Puny as it is, it is the current industry standard. Thus your main branch becomes broken now and then. So you call it "develop" and only merge it to "master" what you are sure is a good product.

I don't understand your point here. Usually your CI builds a branch, runs some tests on the compiled product and makes sure the `master` branch is ok before deploying to staging or production.

If these common situations don't apply to you - proceed as you are. Do the simplest thing possible, but not simpler. What you've described doesn't create any roadblock or dead end street for the project.

I think there are a lot of branching strategies for a reason. Your use cases can be covered with other branching strategies as well.