5 ms·

Why would I use this over fly.io? It seems to be very similar at first glance

by sosodev 4y ago

Existenceblinks 4y ago
I can't even find their vm details (cpu/memory + bandwidth) and many other things.
- colinchartier 4y ago
  Will add those to the landing page - they got lost in the Figma design
mayli 4y ago
Same question here, it seems to be a fly.io clone without the global anycast network.
- colinchartier 4y ago
  We do have a caching anycast proxy like fly, render, and other webapp-focused PaaS providers.
  - dmw_ng 4y ago
    I'd like to try out your service, but would not be willing to link my GitHub account, and I do not have a Google account. Any chance of a non-federated sign in method?
    - Tostino 4y ago
      What access does it require to your GitHub that you are weary about? (Actual question, I am not involved with Webapp.io at all)
colinchartier 4y ago
Practically - We don't actually require you to use Docker, and we don't use it under the hood. The configuration (which looks like a Dockerfile) can run multiple containers in the same VM: FROM vm/ubuntu:22.04 RUN (install docker) RUN REPEATABLE docker-compose build RUN BACKGROUND docker-compose up EXPOSE WEBSITE localhost:8080 You can also just run entirely non-docker services: RUN BACKGROUND redis-server - The DSL will watch which files are used for each build step to skip everything you haven't changed, so builds are much faster - You can use us to clone VMs and run Cypress tests in parallel, then promote one of the clones to a preview environment, and another to a production environment - We're more declarative (in my opinion), we don't have a CLI. Everything is done by editing a Layerfile and git pushing it TL;DR, we focused on a declarative configuration format to quickly build, fork, and hibernate VMs, where Fly is more focused on building/shipping docker containers (though the products do fill a similar niche)
- tptacek 4y ago
  Hey! Best of luck with this. Real quick: we don't use Docker "under the hood" at fly.io either. We take OCI containers as inputs, and transform them into VMs. The only "Docker" running here is the code that allows us to accept our users existing containers.
  - colinchartier 4y ago
    Sure, I meant "docker" here as a simplification for the OCI format.
intelVISA 4y ago
It's good to diversify the built-on-Firecracker-as-a-service space.

Why would I use this over fly.io? It seems to be very similar at first glance

Existenceblinks 4y ago

I can't even find their vm details (cpu/memory + bandwidth) and many other things.

colinchartier 4y ago
Will add those to the landing page - they got lost in the Figma design

mayli 4y ago

Same question here, it seems to be a fly.io clone without the global anycast network.

colinchartier 4y ago
We do have a caching anycast proxy like fly, render, and other webapp-focused PaaS providers.
- dmw_ng 4y ago
  I'd like to try out your service, but would not be willing to link my GitHub account, and I do not have a Google account. Any chance of a non-federated sign in method?
  - Tostino 4y ago
    What access does it require to your GitHub that you are weary about? (Actual question, I am not involved with Webapp.io at all)

colinchartier 4y ago

Practically - We don't actually require you to use Docker, and we don't use it under the hood. The configuration (which looks like a Dockerfile) can run multiple containers in the same VM: FROM vm/ubuntu:22.04 RUN (install docker) RUN REPEATABLE docker-compose build RUN BACKGROUND docker-compose up EXPOSE WEBSITE localhost:8080 You can also just run entirely non-docker services: RUN BACKGROUND redis-server - The DSL will watch which files are used for each build step to skip everything you haven't changed, so builds are much faster - You can use us to clone VMs and run Cypress tests in parallel, then promote one of the clones to a preview environment, and another to a production environment - We're more declarative (in my opinion), we don't have a CLI. Everything is done by editing a Layerfile and git pushing it TL;DR, we focused on a declarative configuration format to quickly build, fork, and hibernate VMs, where Fly is more focused on building/shipping docker containers (though the products do fill a similar niche)

tptacek 4y ago
Hey! Best of luck with this. Real quick: we don't use Docker "under the hood" at fly.io either. We take OCI containers as inputs, and transform them into VMs. The only "Docker" running here is the code that allows us to accept our users existing containers.
- colinchartier 4y ago
  Sure, I meant "docker" here as a simplification for the OCI format.

intelVISA 4y ago

It's good to diversify the built-on-Firecracker-as-a-service space.