LUKI NOTES

If we are building a website that requires a PDF generation feature, there are several options for implementing it based on the use cases or user requirements. First, we can generate the PDF on the client side using any available client library. It is suitable if the use case is to print out some data that is already available inside certain website components, and we want to maintain the styles of the components in the document. Second, we can do it fully in the back-end using any library available, such as PDF-lib, jsPDF, and so on. This approach is suitable if we want to keep the data processing or any related business functions in the back-end server. This second approach might have disadvantages, such as the difficulty of maintaining the design assets and styles which are already on our website. Third, it is using a hybrid approach, where certain processes are handled on the client side, and some are handled on the back-end. In this post, I want to discuss more about the...

Although I typically deploy my development environment or experimental services on UpCloud , I do not always stay updated on its announcements. Recently, I discovered that UpCloud has introduced a new plan called the Essentials plan, which enables certain cloud services to be deployed at no cost. The complimentary services are generally associated with network components or serve as the foundation for other cloud services. This feature is particularly useful when retaining foundational services, such as a load balancer, is necessary, while tearing down all services and reconfiguring the DNS and other application settings each time we temporarily clean up infrastructure to reduce costs is undesirable.  When reviewing the service specifications of the cloud services in the Essentials plan, they appear to be very similar to those in the Development plan. The difference in service levels is unclear, but it could be related to hardware or resource allocation. For instance, the loa...

As I have been working on many software projects and teams, I see that sharing credentials among developers is a common thing. Sometimes, developers store credentials in a file where everyone in the team can access them just to streamline the development process. But, I was also wondering how to maintain the security of the software or data managed while the credentials are accessible to everyone. How can we monitor the usage, make sure that no one in the team uses the credentials differently than they're supposed to be, or renew the credentials with ease? Hashicorp Vault is one of the solutions in the market that can answer that question. There are three main problems that Vault solves. The first is called secret sprawl where the credentials are spread everywhere to many individuals. Then, it becomes difficult when someone leave the team and we have to renew the existing credentials to secure the access. Vault can provide a mechanism to centralize the credentials storage, p...

The trick was unexpected and caught Bertolt off guard.