edweis
Y Combinator: Paxel, understand how you build with AI
Why some GitHub labels illegible (2023)
SQLite – Professional Support and Extension Products
Humanoid Robots Perform Kung Fu at China's 2026 Spring Festival Gala
An open format for API collections
Trump says U.S. operation captured Venezuela's president Nicolas Maduro
Two New React 19 Vulnerabilities
Cloudflare Is Down Again
tRPC: End-to-end typesafe APIs made easy
For naming, just name the directory the same way on your file system.
Shareable urls can be a hash of the path with some kind of hmac to prevent scraping.
Yes if you move a file, you can create a symlink to preserve it.
Is there a decade-old software that provides a UI or an API wrapper around these features for a "Google Drive" alternative? Maybe over the SAMBA protocol?
However there are tons of services that require Google (or outlook) to work with your emails.
My main problem is that I have to put a lot of effort to not use gmail for my business because most of third-parties (like CRMs) work only/better with gmail.
Fastmail team, how about a Gmail compatible API ?
I can tell that the on-premises will be deployed on AWS accounts. We can manage the resources ourselves.
We have few fanouts that can be refactored. So Redis/Valkey for SQS is OK, hopefully it can also cover our SNS use case.
I am afraid Kubernetes is overkill for our lambda needs.
If we manage to bundle our whole app in one server and have only 1-2 clients on -premise, do you still suggest Kubernetes or a simpler rsync on all servers is enough?
Also, should we have a separate database instance for each client, or a Postgres cluster sharded? The latter seams more manageable.
All your points are valid and can be included in the contract: - We'll be the ones to choose the cloud provider, - We'll take servers that are big enough, - The client should upgrade their server according to our specs, - Upgrades are mandatory.
Any idea what other (simpler) recovery plans we can have besides on-premise?
Moving away from AWS lambda/SQS/SNS/Aurora, worth it?
Our clients are interested in using our SaaS solution on-premises to mitigate the risk of service interruption.Considering the opportunity, I am assessing the cost of doing on-premise deployments and maybe partially or fully moving away from AWS.Our current stack is EC2/lambda/SQS/SNS/Aurora/S3 & minor networking setups. AWS deployments made via serverless V3. All the code is in Node.js....
I did this 4 years ago on my personal email address and I never had to recover any email.