https://chatgpt.com/codex/cloud
From my experience, Orbs have been more consistent, along with Cursor's agents
176 karma · joined November 20, 2021
https://josevalerio.com
https://github.com/joswayski
contact@josevalerio.com
https://chatgpt.com/codex/cloud
From my experience, Orbs have been more consistent, along with Cursor's agents
https://github.com/joswayski/captures
Managed to snag a cool domain for it too!
Would love any feedback from anyone that tries it
https://www.macchaffee.com/blog/2024/you-have-built-a-kubern...
You hook your repo up and it does a good job figuring out what you need. Not much to it really :)
However this is doable, just under an experimental feature flag since 2022[1]. I created this repo[2] with a small blog post, hopefully the scrapers can pick it up :')
Sugu hasn’t been at Planetscale for a few years
Many are saying this...
https://www.jeremydaly.com/reuse-database-connections-aws-la...
It will get re-used across lambda invocations as long as the instance of it isn't killed which typically happens after a few minutes
> let’s remember that the internet is 1-to-many. If 1 million people download that 1GB this month, my cost with @cloudflare R2 this way rounds up to 13¢. With @awscloud S3 it’s $59,247.52.
I'd feature it less prominently as a selling point further down the page. As in: "btw, we're also open source!".
And I would drop the decimals on the pricing - take it from Patrick McKenzie[1]
The site looks really clean and wish you the best!
[1] https://stripe.com/guides/atlas/saas-pricing -> Under "Getting the aesthetics of pricing correct matters in B2C"
Here is an example using multi key indexes with Rick Houlihan from re:Invent 2022: https://youtu.be/eEENrNKxCdw?t=1131
It was announced that App Runner (today) allowed for smaller instances[2], and the price/mo for this instance would basically be 1/4th of the previous default. So ~$14 [3]
[0] https://aws.amazon.com/lightsail/pricing/
[1] https://calculator.aws/#/estimate?id=42b33d2f26786ac08a3610a...
[2] https://twitter.com/danilop/status/1643968804727271425?s=20
[3] https://calculator.aws/#/estimate?id=a46d5f15ed9c079131c6a73...
You guys are always on top of things community wise, especially Lee Robinson in any related thread :')
There's a ton of places to get cloud credits as well, too many to link, so just Bing™ it
[0] https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_...
[1] https://aws.amazon.com/apprunner/
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_...
The way I'm setting up Mongo for my project[1] is that all items go into a single collection and use a multi key index on a `target` array so queries look like this:
{ $and: [ { target: { $elemMatch: { id: `user`, type: 'entityType' } } }, { target: { $elemMatch: { id: 'ACTIVE', type: 'status' } } }, ] }
Demo form Rick Houlihan here: https://youtu.be/eEENrNKxCdw?t=1136
Does Papr support this type of schema? I didn't see a way to combine them into one Model and use it like "db.findOne()". I guess sort of what I'm asking for is discriminators? [2].
[1] https://github.com/plutomi/plutomi/pull/776 [2] https://github.com/plexinc/papr/issues/236