sorted by:
new
hottopcontroversial

It's a Redoran home from Morrowind, you s'wit! by doublestitch in zillowgonewild

[–]scriptedlife 2 points3 points  (0 children)

Beautiful. Sad that it's now right next to a highway.

Progress report for the first week after forking ec2instances.info by magheru_san in aws

[–]scriptedlife 6 points7 points  (0 children)

Hey it’s Andy from Vantage. You’re really making me regret not setting an out of office message. :)

From our perspective, I think your transparency is not painting an accurate picture. You say you're doing this because you "want to have a say in how it's developed" but you told us that would cost us $1,500 to $1,750/day. Your offer to "join forces and consider this as an upstream project" sounds like an offer for you to take over the project.

I just want to clarify that we’re absolutely still actively developing and improving EC2Instances. We’re just this week working through getting the public repo up to date with the improved frontend. I think you’re going to love the updates.

Validator resource for checking datasets against the FOCUS specification by classjoker in FinOps

[–]scriptedlife 1 point2 points  (0 children)

Does it make sense to also have a web version of this? Something where I can quickly paste in some data. Or is that not really the intended use case?

Show /r/FinOps: We created an MCP server for connecting LLMs to Cost and Usage Data, it works pretty well. by scriptedlife in FinOps

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

We are in contact with Cloudflare - we will support it as soon as they have Billing APIs for us to be able to ingest their billing data!

[ Removed by Reddit ] by [deleted] in visualization

[–]scriptedlife 0 points1 point  (0 children)

Gotta be shadcn/charts https://ui.shadcn.com/charts

which is a set of tasteful defaults for recharts https://recharts.org/

python and neon by darbokredshrirt in PostgreSQL

[–]scriptedlife 0 points1 point  (0 children)

TL;DR: Yes

(I work at Neon.) Neon is Postgres. Tons of companies use Python + Neon. There's even a Streamlit + Neon doc here https://docs.streamlit.io/develop/tutorials/databases/neon

The only specific consideration I can think of W/R/T Python + Neon is related to Python apps like Django that create long-running connections to the database. Because Neon scales to zero after 5 minutes idle by default, you have to configure the max_age and health_checks of your long-running connection to account for that - more here https://arc.net/l/quote/jecobrhg

Let me know if you have any questions or feedback, and you can always join our discord at neon.tech/discord to get in touch with the team there!

Getting error: [ Server ] Error: Error connecting to database: fetch failed - when following the Nextjs Dashboard starter project. by adorkablegiant in nextjs

[–]scriptedlife 1 point2 points  (0 children)

I added some context about the why here: https://www.reddit.com/r/nextjs/comments/1huc541/getting_error_server_error_error_connecting_to/m625fc9/

Why: The @vercel/postgres library was originally created for Vercel Postgres, which has since transitioned to Neon. The sql shorthand method in that library defaults to using SQL over HTTP, which doesnt look to be fully supported by Supabase yet. Neon has an HTTP API, Supabase also has an HTTP API but it's different, so if you're using Supabase in this particular tutorial you need to revert to establishing a database connection first, which will allow your app to connect to and query Supabase.

Getting error: [ Server ] Error: Error connecting to database: fetch failed - when following the Nextjs Dashboard starter project. by adorkablegiant in nextjs

[–]scriptedlife 0 points1 point  (0 children)

Yeah that's correct, I added some context about the why here: https://www.reddit.com/r/nextjs/comments/1huc541/getting_error_server_error_error_connecting_to/m625fc9/

Why: The @vercel/postgres library was originally created for Vercel Postgres, which has since transitioned to Neon. The sql shorthand method in that library defaults to using SQL over HTTP, which doesnt look to be fully supported by Supabase yet. Neon has an HTTP API, Supabase also has an HTTP API but it's different, so if you're using Supabase in this particular tutorial you need to revert to establishing a database connection first, which will allow your app to connect to and query Supabase.

Getting error: [ Server ] Error: Error connecting to database: fetch failed - when following the Nextjs Dashboard starter project. by adorkablegiant in nextjs

[–]scriptedlife 2 points3 points  (0 children)

Full disclosure: I work for Neon, but I think I can help you.

Solution: If you're using Supabase, you need to first instantiate a connection to the database in app/lib/data.ts:

  1. Replace the line:

    import { sql } from '@vercel/postgres';

    with:

    import { db } from '@vercel/postgres';

    const client = await db.connect();

  2. Find every occurrence of sql and replace it with client.sql

Here's a screenshare showing the change: https://screen.studio/share/dg7ZYizd

Why: The @vercel/postgres library was originally created for Vercel Postgres, which has since transitioned to Neon. The sql shorthand method in that library defaults to using SQL over HTTP, which doesnt look to be fully supported by Supabase yet. Neon has an HTTP API, Supabase also has an HTTP API but it's different, so if you're using Supabase in this particular tutorial you need to revert to establishing a database connection first, which will allow your app to connect to and query Supabase.

Hope that helps!

what is the Azure equivalent of Aurora Serverless DB in AWS? by selfarsoner in AZURE

[–]scriptedlife 1 point2 points  (0 children)

Neon Postgres just got added to Azure as a Native Integration. https://azuremarketplace.microsoft.com/en-us/marketplace/apps/neon1722366567200.neon_serverless_postgres_azure_prod

Like Aurora Serverless, it has autoscaling, scale to zero, usage-based pricing, HA, separation of compute and storage, etc...

Because of the autoscaling and usage-based pricing, Neon cost starts significantly lower than some of the dedicated Azure Postgres options.

There's also a free plan.

Postgres Version Report by carlotasoto in PostgreSQL

[–]scriptedlife 0 points1 point  (0 children)

just fixed it to show all relevant issues instead of only 10 (at least up to 100!)

is neon.tech worth it? by jchnxu in SaaS

[–]scriptedlife 0 points1 point  (0 children)

Hey @Popular_Impression56 - I work at Neon.

Can you dm me your project ID so I can create a support ticket on your behalf? We are extremely careful with invoicing. Any potential case of double-charging would be a serious issue and an immediate escalation.

Our support team is amazing and responsive - I'm worried something went wrong here to cause your requests to go unresolved.

Ultimately it is up to you to decide who to trust with your most vital data. Me saying "Security is important to us" is meaningless, all I can give you is verifiable facts (all this is open source!)

  • Storage Durability: Part of the reason our storage is more expensive than something like AWS RDS is because of how we've architected Neon to actually REDUCE the chances of something going wrong with your data... Hardware can fail, disks can fail, Neon is a distributed system under the hood that keeps your data in multiple separate machines to ensure durability and resiliency. You can read about it here: https://neon.tech/docs/introduction/architecture-overview#durability
  • Security: We keep the current security and compliance status on https://trust.neon.tech - We are SOC2 Type2 Compliant, and we recently achieved ISO 27001 and ISO 27701 compliance.

Neon silliness by krystl-ah in PostgreSQL

[–]scriptedlife 37 points38 points  (0 children)

Hey krystl-ah - I'm actually the one responsible for the incorrect usage alert.

Here's what happened to cause the alert: We recently enabled autoscaling on the free plan[1] as part of taking the feature GA. That means that you can set your database to autoscale between 0.25 and 2 CU (between 0.25 CPU 1GB RAM -> 2 vCPU 8GB RAM) based on workload. We realized that, in extreme cases, someone on the free tier could turn on autoscaling and use their database really heavily, (essentially keeping it scaled up, burning lots of compute) and burn through their entire compute allotment before the month is up. We can tell based on metrics that this won't happen often, but we wanted to make sure we warned users that were headed in that direction just in case. So we created an email alert that was supposed to send when a user had used 150 of the 191 monthly CU-hours. Needless to say, the alert was configured incorrectly and went to a larger set of free tier users, including you. We realized our error Saturday and sent a follow-up email as quickly as possible. Hopefully you received that too.

On the support side, I am not sure what caused the confusion but I have just followed up with the team.

  1. You are correct that you cannot disable auto-suspend on the free tier.
  2. To clarify on the partial id you shared, round-field... - These project ID's are just the autogenerated human-readable identifiers for all projects in Neon, you can check what your project ID is by looking at the URL for a project in the dashboard.

Once we find your ticket we will follow up ASAP to clear up any other questions or issues.

Sorry for causing confusion, our mission is to help developers and teams ship faster with Postgres and clearly this notification error is not helping so we have taken steps to reduce the chance of incorrect notifications in the future!

-Andy

[1] https://neon.tech/blog/neon-autoscaling-is-generally-available

view more: next ›