You're really going to run into trouble with the "no credit card required" thing - people are going to use your service to, at worst, spam and abuse other people and, at best, mine crypto.
Webapp.io's money making part (which facilitates this) is a DevOps company (CI/CD, preview environments, etc) which is already hammered with that sort of thing - see this post (from when we were called LayerCI) discussed by TravisCI for context: https://blog.travis-ci.com/2021-10-20-mining
[I am not parent poster] A new product launched. Abuse can be ignored in initial stages (indeed, it can be useful as a stress test and for boosting user numbers).
Crypto miners and spammers become a problem when they are crowding out legit customers, at which point they'll be pruned, and new signups will require credit cards.
We recently finished our firecracker-based webapp hosting platform.
It's like if Vercel and Docker had a baby: You write VM configurations in a language that looks like a Dockerfile, and every commit creates a preview environment which can be "promoted" to a production site.
Here's an example configuration:
```
FROM vm/ubuntu:18.04
RUN curl -fSsL https://deb.nodesource.com/setup_12.x | sudo -E bash
RUN apt-get install nodejs
COPY . .
RUN npm install
RUN npm run build
RUN BACKGROUND npm run start
EXPOSE WEBSITE localhost:3000
```
This product combines our firecracker-based hypervisor (200ms cold starts) with a global CDN written in Go (using Caddy for TLS termination)
We can offer everything for free because we charge for the DevOps side (CI/CD & preview environments) - we have no intention of getting users and then upselling people for hosting.
We're obviously very excited about this launch, and would love to hear your feedback.
Serverless isn't that enjoyable for me since I don't like using old versions of stuff. Vercel doesn't support Node 19, which means you can't use built-in fetch without it logging a warning about fetch being experimental every time you call it.
IIRC it took a long time for Node 18 to be available.
Containers FTW. You can use things in production when the maintainers release to production, not when AWS Lambda has them.
> You can use things in production when the maintainers release to production, not when AWS Lambda has them.
You can run anything the hell you want in AWS Lambda as it is literally just a container. The documentation even shows you how to write your lambda function entirely in a handful of lines of bash using curl to request the job and submit the result.
Firefox, latest version, no ad blocker enabled.
After nosing around in your source a bit, it seems the redirect to https://docs.webapp.io doesn't work for me?
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?
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)
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.
When creating an account with Github, why do you ask permission to "act on my behalf"? There is no such permission when creating an account with Google
It looks like all of the auth data is empty - maybe you logged into an account which doesn't have permission to install on that repository?
If you email me at colin@webapp.io with your GitHub account name, webapp.io account (if any), and the name of the repository, I can take a look for you.
Ah, I stripped it from the post, didn't want to leave some important tokens on the internets.. :D I removed the authorization and tried again a few minutes later, it ended up working. Probably a temporary problem.
- Access the authenticated user's API
Grants complete read/write access to the API, including all groups and projects, the container registry, and the package registry
