In this post we are going to walk though the steps to be completed in order to securely store and use the credentials necessary for Kubernetes to pull an image from the Gitlab container registry.
Looking at companies like Zapier, Gitlab or Automattic you come to realize that remote-work is not just an utopia, and thata a great company and a great product can be build on async work. Inspired on those great examples I created a guide for us at Piio.
We all know what waiting means, and we don’t want it. It’s awful to be waiting in line, wait for something you bought to be delivered, or to click on a link and wait for a website to load, especially if it is your website. You don’t want to be that company that users slip away because the website didn’t load properly.
It comes a time on the design process were using the same image for desktop and mobile devices doesn’t work. Using a wide hero image on the desktop may look nice, but when you go to a mobile device, the details on the image get lost, and the products are barely visible; not to mention that text might be too small to be read properly. That’s when Art Direction comes into play.
Running scheduled jobs on Laravel is a piece of cake, you only need to add one cron entry on your server calling the laravel scheduler to run every minute and you can manage the rest from your code in _app/Console/Kernel.php_.
If you’re a designer or a developer, it’s clear to you that you need to manage the assets and your user images for different devices and screen sizes. There are also two types of images that you need to work with, the standard images included in the tag `<img>` and the background images included in the CSS styles. We`ll discuss solutions to these problems and how Piio works in each case.
If you're experiencing this problem maybe you've made the checkout with the http or https url, that means that you don't have an authentication method.