personal-site | Personal website - This is the code behind sergiodxa | Blog library

A friend pointed out to me that I was missing an index.js page within the src/components/ directory.

As I understand it whenever you setup an alias which points toward a directory, it will actually reference the index.js file contained within the specified directory.

After creating the file and re-exporting the components within it, webpack no longer had any issues.

Contents of my src/components/index.js:

This commonly happens when migrating from a local site to a live site.

The "src" for the image needs to be published/hosted somewhere on the web so it has a direct URL to the image, like this image of a cat: https://ichef.bbci.co.uk/news/1024/cpsprodpb/151AB/production/_111434468_gettyimages-1143489763.jpg

It works locally because that file is present on your local machine in a folder somewhere. Because the file path is relative it now searches for the image like this: https://sakurach4n.github.io/images/mafalda.png (which does not exist)

It seems your memory limit reached by program. In windows you can extend your node memory limit in windows via:

In files.associations you mention the languageId to use for a particular file extension

I think the problem is that you run all your npm commands with sudo except the firebase deploy command. You should definitely run everything with the current user and not the superuser. You will see in official tutorials that nothing is run with sudo except for very specific cases.

Also, instead of doing this ./node_modules/.bin/firebase deploy you could use npx run firebase deploy which first look in the local node_modules then in the global ones.

"Back-off restarting failed container" has nothing to do with the readiness probe. Failing readiness probe never causes a container to be killed or restarted. It is just responsible for considering the container ready for serving requests and for adding it to the load balancer of a service.

the other builds an application and drops the assets into a build directory

What I suspect here is that the personal-site-container builds the assets and exits. As the default restart policy is always, the container gets restarted, and so on, and so on, it enters a "back-off restart" loop.

By the way, readiness probe for the personal-site-container makes not much sense. First, it does not belong to any service, second it's meant to do the job and exit (as far as I understand). You might want to have a look on Kubernetes jobs.

The best way is to customize your image's entrypoint as following:

• Once you finish building the /var/app/dist folder, copy(or move) this folder to another empty path (.e.g: /opt/dist)

Thanks for marcelo-waisman's post.

If we follow the documentation tightly...