flyctl VS docker-node

Once we finished playing around with the model locally, let’s cast our final spell for the day 🧙‍♂️ and deploy the model to fly.io:

If you dockerize your .net app you can run it on https://fly.io free tier with a Postgres database! You don’t need IIS or MSSQL.

checkout https://render.com/ or https://fly.io for free plans. as of deploy, you need to provide more info about your project. Do you use docker? How do you want to deploy? Etc.

Better yet, pick a few shades of grey ranging from white to black and a few shades of _one_ other colour. https://fly.io/ comes to mind. Also, here is a great video on choosing colour: https://www.youtube.com/watch?v=mq8LYj6kRyE

Hmmmm. I've had some trouble recently where (I think) the Strapi app crashed, when uploading some files (due to the fly.io machines having rather limited resources, where my media would still be listed in the library but, for example the images wouldn't show up - file missing, basically).

fly.io for laravel/mysql. Vue with netlify

This is what my github action is doing currently. Its reading the repo to see if there are any changes, then recreates the docker container and sends it to fly.io. - Then it also creates another container and sends it to dockerhub. When it sends to Fly.io, the website is automatically updated. So any changes on the repo are reflected on the website immediately. Its the same as having a firewall in a linux instance that is guided by the githubaction. Anytime someone makes a change to the file that is in the repo, the firewall gets updates when the instance is recreated. Also if someone deleted the instance the instance would reappear the moment anyone made a change to the repo.

what app? you mean the github action? It doesn't run on a local server, it's hosted on fly.io

These services are the most similar https://fly.io/ https://render.com/ https://railway.app/ If you can pay for hosting you can choose one and stick with it. If not, you'll have to use a combination of the limited free tiers each offer.

This node image is just one of a range published by the Node.js team (https://hub.docker.com/_/node), and they also have the Dockerfile for their build available

Node is about 60mb on it's own.

Taking a peak at the official dockerfile for alpine node (https://github.com/nodejs/docker-node/blob/28ad5e0e5d0e80df4...), they're also pulling in the following packages

        && apk add --no-cache --virtual .build-deps-full \

# Base node images can be found here: https://hub.docker.com/_/node?tab=description&%3Bpage=1&%3Bname=alpine ARG NODE_IMAGE=node:16.17-alpine

Official Docker image of Node 16.16.0

Docker Hub is a container image library where you can find interesting images to use in your projects like the Apache image, Nginx image, PHP image, Node.js image, MySQL image, etc. These images are ready to use, and they come with instructions about how to use them. Usually, you have to pass environment variables to the container and/or tweak a couple of config files.

This was an experiment to see if it was possible to run Node.js (Github) and Docker Hub), Next.js (Github and TinaCMS from Node.js' Docker container.

There are a lot of base Node.js images that you can choose from. These can be found on the official Docker Hub page of Node.js. In our initial Dockerfile, we've chosen the node:17 base image. This node:17 base image incorporates a lot of dependencies from the underlying OS that you most likely don't need. We can try to use the node:17-slim version and check if that fits our needs. This is the resulting Dockerfile:

When deploying your web application you will likely be using Docker for containerization. Many base Docker images like Node or Python are running Alpine Linux. It is a great Linux distro that is secure and extremely lightweight.

With Docker we can use code to generate the environment that our app runs in. We'll begin by searching Docker hub for a Node.js image. The official Node image is just called node.