Web Dev Trends
21 subscribers
697 photos
6 videos
690 links
Полезные статьи и новости веб разработки
Download Telegram
#js #JavaScript #frontend #webdev

The "boolean" function in JavaScript lets you convert any value into either "true" or "false". This can be useful when dealing with TypeScript, outputting JSON, or using it with the "filter" method.

👉 Watch video 👈

@webdev_trends
#css #frontend #webdev

Grid is awesome, and there are some neat tricks that you can do with it that I don’t see enough people taking advantage of, like overlapping named grid lines, using position absolute with grid, and animating template-rows and template-columns.

👉 Watch video 👈

@webdev_trends
#laravel #php #tips #webdev

Check out this awesome article on clean code tips!📝

Learn how to use scopes to get rid of those long code blocks and keep your code neat!

👉 Watch video

@webdev_trends
#beginners #docker #devops #tutorial

1. Running our First Docker Image

In the recent years, technological improvements across all industries have dramatically increased the rate at which software products are demanded and consumed. Trends like agile development and continuous integration also increased demand. As a result, many organizations have opted to switch to cloud infrastructure.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

2. Basic Container Lifecycle Management

Throughout your container journey, you will be pulling, starting, stopping, and removing containers from your local environment quite frequently. Prior to deploying a container in a production environment, it is critical to run the container locally to understand how it should work. This includes starting, stopping and restarting containers, getting details about how the container is running, and, of course accessing verbose logs to view critical details about the applications running inside the container.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

3. Getting Started with Dockerfiles

In the previous posts, we discussed how you can run your first Docker container by pulling pre-built Docker images from Docker Hub. While it is useful to get pre-built Docker images from Docker Hub, we can't only rely on them. This is important for running our applications on Docker by installing new packages and customizing the settings of the pre-built Docker images.

This will be done using a text file called a Dockerfile. This file consists of commands that can be executed by Docker to create a docker image. Docker images are created from a Dockerfile using the docker build or docker image build command.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

4. Attaching To Containers Using the Attach Command

In the previous post, we discussed how to use the docker exec command to spin up a new shell session in a running container instance. The docker exec command is very useful for quickly gaining access to a containerized instance for debugging, troubleshooting, and understanding the context the container is running in.

However, Docker containers run as per the life of the primary process running inside the container. When this process exits, the container will stop. If you need to access the primary process inside the container directly (as opposed to a secondary shell session), then you can use the docker attach command to attach to the primary running process inside the container.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

5. Building Docker Images


In the previous post we discussed how to create a Dockerfile. The next step of the process is to build a Docker image using the Dockerfile.

A Docker image is like a compiled file. It's built in layers, starting with the base layer that contains the fundamental setup. This is usually the layer we use the FROM directive. Each subsequent layer adds on top of the previous one, making small adjustments or additions. These layers are stacked on top of another, and each layer builds up the changes made in the layer before it.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

6. Advanced
Dockerfile Directives

In this post, we are going to discuss more advanced Dockerfile directives. These directives can be used to create more advanced Docker images.

For example, we can use the VOLUME directive to bind the filesystem of the host machine to a Docker container. This will allow us to save the data generated and used by the Docker container to our local machine.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

7. Advanced Dockerfile Directives


In the previous posts of the series, we discussed in depth about Docker images. As we've seen, we've been able to take existing images, provided to the general public in Docker Hub, and run them or reuse them for our purposes. The image itself helps us streamline our processes and reduce the work we need to do.

In the next few posts, we are going to take a more in-depth look at images and how to work with them on our system. We're going to discuss how images can be better organized and tagged, understand how different layers of images work, and set up registries that are both public and private to further reuse the images we have created.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

8. Understanding
CMD, ENTRYPOINT and RUN in Docker - An Interlude Post

Docker is undeniably a powerful tool for containerization, but its versatility and extensive feature set can be overwhelming, especially for newcomers. The platform offers multiple ways to achieve similar goals, making it crucial for users to carefully weigh the advantages and disadvantages of each option to determine the best approach for their specific projects. This decision-making process requires a solid understanding of Docker's underlying mechanisms and the trade-offs involved in different strategies.

Docker can be a bit of a maze, especially when it comes to the nitty-gritty of instructions like RUN, CMD, and ENTRYPOINT. These three instructions often cause confusion, as they seem to have overlapping functions.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

9. Creating Base Docker Images


Creating your base Docker image is quite straightforward. Just as we used the docker commit command previously to create an image from a running container, we can also create an image from a system or server where our applications are originally hosted. However, it's crucial to keep the base image small and lightweight. Simply moving existing applications from traditional servers to Docker isn't enough.

If you're using a production server, the resulting image could end up quite large. For smaller virtual machines that seem ideal for a base image, you can follow these steps to create one. Similar to the docker commit command, this method works for any system you have access to.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

10.
Dockerfile Best Practices Explained - Interlude Post 2

In this post, we'll dive into the best practices for writing Dockerfiles that will help you create efficient, secure, and maintainable Docker images while reducing build times.

👉 Read article

@webdev_trends
👍1
#beginners #docker #devops #tutorial

11. Docker Image Naming and Tagging


As we get more acquainted with Docker, let's explore a little bit more what image tags are all about, even if we have discussed them before. All told, a tag is essentially a label you apply to your Docker image. Like a little sticky note informing you—and everyone else using the image—something significant about it, including what version it is or what type of software it contains. Consider it as a means of maintaining easily comprehensible and orderly Docker images.

Working on our Docker images, we had assumed that we are all by ourselves. That won't always be the case, though, particularly as our development team expands. The following post will help us to understand how best to tag and name our images for a team environment. Following these guidelines will help us to maintain our Docker images clear and understandable for every project participant..

👉 Read article

@webdev_trends
👍1