jdsleppy

It took me minutes to find what it actually cost, which is $50/month for the cheapest, 256MB deployment.

Looks cool, but this info should be easier to get to. Tell us what resources we get in a "nano", "micro", etc. and how much they cost. That's the first and usually only thing I look at with these.

It's a nice idea, but after I get to the graph page things just stop. Clicking on nodes doesn't do anything. Bug?

Doesn't stealing the cookies/token require a non-HTTP-only session cookie or a token in localstorage? Do you know that Discord puts their secrets in one of those insecure places, or was it just a guess?

I believe if you always keep session cookies in secure, HTTP-only cookies, then you are more resilient to this attack.

I interviewed frontend devs last year and was shocked how few knew about this stuff.

Multiple processes, multiple threads per process, and/or greenlets (monkey patch network calls, like async but no keywords involved). Scale out horizontally when there's a problem. It could get expensive.

I can second the other commenter: you are having a different discussion than the rest of the comments and OP.

Er... is it software? Hardware?

If you continue to not find what you need and are willing to be a subject matter expert on what Pivotal actually is (because I never saw it), I would be interested in building this. A lot of people share your sentiment so it could be successful, but it's hard to clone something unless you know the thing.

Also disadvantaged groups might consume less healthcare and might be less aware of air quality, etc. and so may be more likely to have bad health outcomes for given environmental inputs.

The source code does not get to the filesystem on the prod server. It is sent to the Docker daemon when it builds the image. After the build ends, there's only the image on the prod server.

I am now convinced that this is a hidden docker feature that too many people aren't aware of and do not understand.

No, in my example the docker-compose.yml would exist alongside your application's source code and you can use the `build` directive https://docs.docker.com/reference/compose-file/services/#bui... to instruct the remote host (Hetzner VPS, or whatever else) to build the image. That image does not go to an external registry, but is used internal to that remote host.

For 3rd party images like `postgres`, etc., then yes it will pull those from DockerHub or the registry you configure.

But in this method you push the source code, not a finished docker image, to the server.

I've been very happy doing this:

DOCKER_HOST=“ssh://user@remotehost” docker-compose up -d

It works with plain docker, too. Another user is getting at the same idea when they mention docker contexts, which is just a different way to set the variable.

Did you know about this approach? In the snippet above, the image will be built on the remote machine and then run. The context (files) are sent over the wire as needed. Subsequent runs will use the remote machine's docker cache. It's slightly different than your approach of building locally, but much simpler.

This is for running code on your own servers, he doesn't deal with running others' code.

Did you compile the Python yourself? If so, you may need to add optimization flags https://devguide.python.org/getting-started/setup-building/i...

I assume they are saying that in practice, if wealth gives one influence (if one lives in capitalism), one will use that influence to make one's market less free to one's benefit.

You also skip the docker compose pull if you configure it to always pull in the compose file or in the up command.

Do what the sibling comment says or set DOCKER_HOST environment variable. Watch out, your local environment will be used in compose file interpolation!

I really like `DOCKER_HOST=ssh://... docker compose up -d`, what do you miss about Deployments?

HTMX has a very nice drag and drop extension I just found, though. And old-school forms can include image files. The little image preview can be a tiny "island of JS" if you have to have it.

Where do you suggest we sanitize values? Only in the client, when rendering them?

They could always fall back to storing a value in a hidden element in the worst case. All/some/none selected is often done with an indeterminate state checkbox https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/... that can represent all three states.

Maybe I don't understand the problem you are talking about.

I have not started to use LLMs, so yes I still use search engines.

Yes, in that I have the time but need something meaningful to build with it. Let me know if you might need a partner.

Too late to edit, but I've learned this is not necessarily true (but could be a default date used by the SS code in particular). Sorry for spreading rumors.

Apparently the 150 year old Social Security recipients were due to a COBOL quirk where the zero datetime is 1875. Interesting, but not fraud.

Working the backhoe requires more skill than shoveling and can command a higher wage. You want to more carefully vet and care for the person driving your expensive equipment. Also you had an engineer to design the backhoe and factory workers to assemble it who are getting paid during this process. It's possible that the net wage per hole dug goes up as a result.

...but with manually running autoinstrumentation in the post fork hook.

I guess there is a lot of undocumented magic in OTel...

I found this to work fine https://opentelemetry-python.readthedocs.io/en/latest/exampl...

Thank you for this, I'm glad to hear you acknowledge that having kids isn't a constant philosophical bliss. I have two under 5 as well and don't relate to the dozens of comments gushing about their kids, wanting to spend more time with them. A few hours a day with my 4 year old is plenty (and most days, too much).

Nice, that is my current approach on my latest project (referring to what your linked repo does). Inlining it here for others: copy a .env and a docker-compose.yml, run `docker compose "$@"` on the instance via ssh. That lets me deploy, run one-off commands, and tail logs easily.

Same (but not a shopping site). Bundle the JS and CSS into one file each and cache it forever (hash in the filename to bust the cache). Then with each page transition there's exactly one HTTP request to fetch a small amount of HTML and it's done. So fast and simple.