web3.storage VS engine

https://web3.storage/ https://estuary.tech/

I'm building Flash — a service to deploy websites and apps on the new decentralized stack. It relies on public infrastructure (such as Estuary, web3.storage and others) instead of providing its own, making the bandwidth and storage very cheap and accessible.

https://web3.storage/ does everything you need

Web3.Storage and other similar projects run a network of IPFS nodes that allow users to store whatever content they like, as a kind of competitor to Dropbox or Google Drive: this could be their personal content, or again, any application content, because some apps integrate directly with this service via their API

You can file this as an issue in the repo here and perhaps mention to them that, as a user, it feels phishy to you.

Typically app developers would be the ones to build on Filecoin and you would choose an app like web3.storage to store your data. As a consumer you dont have to directly hold FIL but you benefit from the Filecoin ecosystem.

Filecoin may not have a front-end but our team has worked on https://estuary.tech and it has been easy for our users that have an invite to onboard to the Filecoin Network, another great option is https://web3.storage

clone repos to your computer, dont just fork them

the fork disappears when the parent repository is taken down, clones stay on your machine

upload to IPFS. you can pin on IPFS for free with filecoin. Use filecoin nodes to pin on ipfs at https://web3.storage

As for storing data on Filecoin directly, that would require making a deal with a Filecoin Storage Provider; doing so is currently a complex task but reading the documentation should get you somewhere. You will need a small amount of the FIL token to make the deal with an SP, who will then store your data. Keep in mind that something like web3.storage or Estuary.tech may be better for your needs if you need easy access to the files later; Filecoin can (currently) be thought of as closer to archival storage, but efforts are being made to make it more generally useful too.

Qovery: Qovery simplifies the deployment process for Kubernetes by letting you declare your project's structure and dependencies, making it an excellent choice for startups looking to focus on development without worrying about infrastructure.

Enter Qovery - an Internal Developer Platform that can be installed on any Kubernetes cluster to bring a delightful and simplified developer experience. But don't take my word for granted. In this quick step-by-step article, I will show you how to deploy one of my GitHub apps and a Postgres database on my Kubernetes cluster running on GCP. And what's really really cool is that I don't even need to understand how Kubernetes work!

Qovery is a comprehensive PaaS tool that offers a range of features to simplify the deployment and management of applications. With Qovery, you can easily deploy your applications in various cloud environments, eliminating the complexities of infrastructure setup. Its intuitive and developer-friendly interface, Git integration, and automatic scaling capabilities make it a powerful choice for building a custom PaaS. Qovery's seamless integration with popular frameworks and databases further enhances its appeal.

Qovery https://www.qovery.com

I have one of my customers who want to use Qovery to deploy their apps on AWS China. Technically speaking, Qovery runs on Kubernetes and on all the usual AWS regions. But AWS China (Beijing) is a bit different (cf here)

Combining GitLab (CI) with Qovery (CD) sounds what you need.

I am eager to get your feedback on Qovery - an open-source CD platform that helps thousands of developers and DevOps to build and scale on AWS.

Qovery - an open-source platform that makes AWS easier and there is a Terraform provider available