Spacing the Cans
6 by hams-andwich | 2 comments on Hacker News.
Sunday, March 31, 2024
Saturday, March 30, 2024
Friday, March 29, 2024
New top story on Hacker News: Beware Scaling on AWS in Early Days
Beware Scaling on AWS in Early Days
9 by Kalanos | 3 comments on Hacker News.
During my first month on AWS, I used AWS Batch a lot. AWS decided to bill me mid-month (for more than I utilized I should add) even though the cycle ends on the 31st. The transaction failed. Instead of contacting me to resolve the issue, AWS completely locked me out of the account. Card is also now locked due to "fraud." I've been trying to resolve this for a week now (closer to 3 weeks if you include quota-related tickets). It's Friday, and I have a demo with a Fortune 100 company next week. In order to get results for this demo, I need to run a lot of Batch jobs - not great. I shudder to think about what would happened if this had been a launch with paid customers. From their perspective, I get that crypto miners probably sign up and cancel their credit cards, but I was just using the cloud as intended. I had multiple tickets related to resource quotas that explained why I was using the cloud.
9 by Kalanos | 3 comments on Hacker News.
During my first month on AWS, I used AWS Batch a lot. AWS decided to bill me mid-month (for more than I utilized I should add) even though the cycle ends on the 31st. The transaction failed. Instead of contacting me to resolve the issue, AWS completely locked me out of the account. Card is also now locked due to "fraud." I've been trying to resolve this for a week now (closer to 3 weeks if you include quota-related tickets). It's Friday, and I have a demo with a Fortune 100 company next week. In order to get results for this demo, I need to run a lot of Batch jobs - not great. I shudder to think about what would happened if this had been a launch with paid customers. From their perspective, I get that crypto miners probably sign up and cancel their credit cards, but I was just using the cloud as intended. I had multiple tickets related to resource quotas that explained why I was using the cloud.
Thursday, March 28, 2024
Wednesday, March 27, 2024
Tuesday, March 26, 2024
Monday, March 25, 2024
New top story on Hacker News: Show HN: Auto-generate an OpenAPI spec by listening to localhost
Show HN: Auto-generate an OpenAPI spec by listening to localhost
12 by adawg4 | 1 comments on Hacker News.
Hey HN! We've developed OpenAPI AutoSpec, a tool for automatically generating OpenAPI specifications from localhost network traffic. It’s designed to simplify the creation of API documentation by just using your website or service, especially useful when you're pressed for time. Documenting endpoints one by one sucks. This project originated from us needing it at our past jobs when building 3rd-party integrations. It acts as a local server proxy that listens to your application’s HTTP traffic and automatically translates this into OpenAPI 3.0 specs, documenting endpoints, requests, and responses without much effort. Installation is straightforward with NPM, and starting the server only requires a few command-line arguments to specify how and where you want your documentation generated ex. npx autospec --portTo PORT --portFrom PORT --filePath openapi.json It's designed to work with any local website or application setup without extensive setup or interference with your existing code, making it flexible for different frameworks. We tried capturing network traffic on Chrome extension and it didn't help us catch the full picture of backend and frontend interactions. We aim in future updates to introduce features like HTTPS and OpenAPI 3.1 specification support. For more details and to get started, visit our GitHub page ( https://ift.tt/NxBwnjb ). We also have a Discord community ( https://ift.tt/qFv9Gfm ) for support and discussions around using OpenAPI AutoSpec effectively. We're excited to hear what you all think!
12 by adawg4 | 1 comments on Hacker News.
Hey HN! We've developed OpenAPI AutoSpec, a tool for automatically generating OpenAPI specifications from localhost network traffic. It’s designed to simplify the creation of API documentation by just using your website or service, especially useful when you're pressed for time. Documenting endpoints one by one sucks. This project originated from us needing it at our past jobs when building 3rd-party integrations. It acts as a local server proxy that listens to your application’s HTTP traffic and automatically translates this into OpenAPI 3.0 specs, documenting endpoints, requests, and responses without much effort. Installation is straightforward with NPM, and starting the server only requires a few command-line arguments to specify how and where you want your documentation generated ex. npx autospec --portTo PORT --portFrom PORT --filePath openapi.json It's designed to work with any local website or application setup without extensive setup or interference with your existing code, making it flexible for different frameworks. We tried capturing network traffic on Chrome extension and it didn't help us catch the full picture of backend and frontend interactions. We aim in future updates to introduce features like HTTPS and OpenAPI 3.1 specification support. For more details and to get started, visit our GitHub page ( https://ift.tt/NxBwnjb ). We also have a Discord community ( https://ift.tt/qFv9Gfm ) for support and discussions around using OpenAPI AutoSpec effectively. We're excited to hear what you all think!