> How would you sell me on Pantry vs. AWS S3?

Is this question really appropriate? The developer is sharing a pro bono offering, where does selling anyone on it against a commercial service even come into play?

It looks like a project that must have been fun to make and could be useful for storing non-sensitive data with very little hassle. Long bucket IDs appear to leave little chance for name collision.

If you are building a piece of software that deals with anything remotely like PII or has specific availability requirements, I sincerely hope this is not something you are seriously considering (otherwise, pardon me, I hope I won’t be your user or customer), starting from the fact that you aren’t paying for it and there is no SLA.

Of course it’s appropriate! From the docs this service doesn’t even meet the “viable” part of MVP! Ok a user can post some json that’s public (no authentication) and doesn’t even work across domains (CORS).

Suppose adding those things and targeting “mobile backend as a service” or even more general “backend as service” there is still a lot to be desired. Like static html, ok you’re competition is Firebase.

How’s Firebase doing these days?

Thanks for the kind words and for understanding where I'm coming from, and my perspective :)

"Sell me on X vs. Y." is a colloquialism. It's just a different way of asking "what are the benefits of X over Y."

We’re talking welcoming a stranger sharing the result of their work with “but what are the benefits of your free solution over megacorp Z’s paid offering Y?”.

That is your interpretation but not my meaning.

Hey, thanks for the feedback.

This is definitely been a learning experience for me, and I'm really not sure what the future holds for the project.

CORS was/is an issue that I've yet to fully figure out, if you have any ideas please share - I'd love to learn.

Authentication is something that I've delebratly avoided as I feel Pantry should not be used to store sensitive data, nor should it be ever used in production. It's for POC's, hackathon projects, and should be used as a development tool for rapid prototyping.

Please let me know if you have any suggestions, and please feel free to submit PR's if you'd like!

Let the user register a site when they create a UUID (Account). You are not storing private data. Let the user make cors request using the UUID as an authorization token. If the website and the UUID match, the server responds with the content.

Hi, found an earlier comment of yours mentioning you changed to being a hotel owner. We make a free hotel PMS -- would you like to get in touch and see how we can make it better for you? https://hoteliera.com/