By Paul KrillEditor at Large, InfoWorld |GitHub Enterprise Server 3.12, now generally available, introduces tag patterns for restricting deployment rollouts to GitHub Actions environments. The new release also introduces merge queues, a feature that automates pull request merges.Announced March 6, GitHub Enterprise Server can be downloaded from github.com.With the 3.12 version, developers can restrict deployment rollouts to select tag patterns in GitHub Actions environments. By configuring certain tags or tag patterns on protected environments, users can restrict which branches and tags can be deployed to those environments.Version 3.12 also allows developers to automate pull request merges using merge queues. Merge queues automate the process of validating and merging pull requests into a busy branch, ensuring that the branch does not get broken and reducing time to merge, GitHub said.GitHub Enterprise Server is a self-hosted platform for software development within an enterprise, leveraging Git version control. Other improvements in GitHub Enterprise Server 3.12:Next read this:Paul Krill is an editor at large at InfoWorld, whose coverage focuses on application development.Copyright © 2024 IDG Communications, Inc.Copyright © 2024 IDG Communications, Inc.

GitHub Enterprise Server adds deployment rollout controls. GitHub Enterprise Server 3.12, now generally available, introduces tag patterns for restricting deployment rollouts to GitHub Actions environments.

InfoWorld

Posted on Mar 7                  With the constant developing software industry, building the robust, scalable and maintainable apps is a constant pursuit.In order to achieve such great challenges we have microservices. As the name suggest, these can be judged as multiple small services that are integrated together to form one complete application.And when we write these services with the help of the Nodejs, these are then known as the microservices with nodejs.Microservices architecture decomposes complex applications into independent, loosely coupled services. Each service encapsulates a specific functionality, communicates with others through well-defined APIs (Application Programming Interfaces), and is independently deployable. This approach offers several advantages:Scalability: Individual services can be scaled independently based on their specific needs, ensuring efficient resource utilization.Agility: Development teams can work on and deploy services in isolation, leading to faster development cycles and easier maintenance.Resilience: Failure in one service has minimal impact on others, enhancing overall application reliability.Technology Agnosticism: Different services can be built with different languages and technologies, fostering flexibility.Node.js, with its event-driven, non-blocking I/O model, is particularly adept at building microservices.Here's why:Lightweight and Efficient: Node.js excels at handling numerous concurrent connections, making it ideal for microservices that handle high volumes of requests.Rapid Development: JavaScript, the language behind Node.js, is known for its ease of use and extensive ecosystem of libraries and frameworks, accelerating development.Community and Support: Node.js boasts a vast and active community, providing ample resources and support for developers venturing into microservices.There is a lot more to learn about what are microservices and how to efficiently use the microservice architecture while building your back-end. Here are some of the resources that will help beginners to get started with the microservices in NodejsHands-On Mircroservices with Nodejs by :- Diogo Resende .YT channel explaining microservices with nodejs  .Feel free to make a learning project github repository and reach out to me, to learn together and collaborate to develop your first Nodejs back-end system with MicroservicesHappy Coding!! Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Ramu Narasinga - Feb 27                          Akash Pattnaik - Feb 27                          Rubén Alapont - Feb 27                          Ricardo Esteves - Mar 2                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

#Microservices in Nodejs. Here are some of the resources that will help beginners to get started with the microservices in NodejsHands-On Mircroservices with Nodejs by :- Diogo Resende

DEV Community

#Microservices in Nodejs

Posted on Mar 7                  When creating websites or apps even those, with skills can make common errors.Whether it's overlooking responsiveness or neglecting security issues these missteps can impact performance and user satisfaction.Let's explore some of these traps and how to steer clear of them.NOTE: some analogies have been taken from ChatGPT to make the article more engaging.Just as too much construction can lead to traffic jams, excessive DOM manipulation can slow down your website.Imagine scrolling through a website on your phone, constantly zooming in and out just to read the text or click a button.Frustrating, right?That's why it's essential to prioritize responsiveness in design for a smoother user experience.To ensure your website loads quickly it's important to optimize performance by getting rid of any unwanted elements (like files) and following best practices.Imagine setting sail on a grand sea voyage, only to realize that your ship can't cruise certain waters.Like preparing for a voyage testing your website across browsers is necessary to avoid any compatibility issues.Close your eyes and imagine yourself using a website without being able to see the screen.That's why you should follow accessibility standards for inclusivity.Read more here.Without the right map and compass, your website as a treasure is destined to remain unexplored.So, use semantic HTML and meta tags for better search engine visibility.Without records of your progress, chaos would surely follow.Thus, you should always use version control, like Git, for code management.Sometimes, blindly using spells from a random book you found on the ground will just lead to the worst.So please, understand frameworks, and don't over-rely without comprehension.Neglecting security is like leaving the gates wide open, inviting trouble to come knocking.Accordingly, prioritize front-end security to prevent vulnerabilities.Imagine your code as a toolbox, neatly organized with each function and component designed for a particular task.This approach not only smoothens the development process but also enhances the effectiveness of our website.Avoid duplicating code; use functions or components for reusability.Ever wondered why your website isn't performing as well as it could? 🤔Or why do users seem frustrated with your app? 😠By asking yourself questions like these, you can make progress for smoother web experiences.I hope you liked the article! ❤️Connect with me: linktreeHappy Coding! 🚀Thanks for 18899! 🤗Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              fajarriv - Mar 4                          Andrew Bone - Mar 4                          Samuel Lubliner - Mar 4                          Ollie Bannister  - Mar 4                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

🔟 Things You Must Not Do In Frontend Development. Without the right map and compass, your website as a treasure is destined to remain unexplored

🔟 Things You Must Not Do In Frontend Development

Posted on Mar 7                      • Originally published at phuoc.ng                   Here's what we'll cover:The macOS Calculator app is a simple but powerful tool that has been included with every Mac for many years. It lets you do basic arithmetic functions like addition, subtraction, multiplication, and division. The app's interface is clean and user-friendly, which makes it a go-to tool for anyone needing quick calculations.In this post, we'll explore how to create a macOS calculator layout using HTML and CSS. To make it fully functional, we'll need JavaScript to implement the real calculator. But we'll skip this part and focus solely on creating the layout.Before we get into the details, here's the final layout we'll be creating:The calculator is constructed using various elements, including a div element to display the result and several buttons that allow users to interact with it.It's all pretty straightforward. We've added div and button elements in the order they appear on the calculator, from top to bottom and left to right.The result element has the calculator__result class, while all the buttons have the calculator__key class.Let's talk about how to create a grid layout for our calculator. Imagine the calculator as a grid of 4 columns and 6 rows. To make this happen, we use the display: grid property which sets the root element as a grid container. Then, we can define the number of columns and rows in our grid using grid-template-columns and grid-template-rows.To keep things simple, we use the repeat() function to set up our grid without having to manually specify each column or row. In this case, we want a grid with 4 columns, each with a width of 4rem, and 6 rows, each with a height of 4rem. This creates a neat and uniform grid where each cell has equal dimensions.Here are the CSS styles we apply to the root element of the calculator:Let's take a closer look at the result element in our calculator layout. This is the big box at the top that shows all the calculations. We make it take up the whole first row of the layout using a special CSS property called grid-column. Remember how we talked about grid-column-start and grid-column-end in our previous post? Well, we set grid-column to 1/5. This means the element starts at column 1 and ends at column 5, effectively covering the whole top row of the layout.With this one simple CSS trick, the result element now dominates the top row of our calculator layout.Next, let's talk about the special button that allows users to enter the number zero. This button takes up two cells in our grid. To make it span two columns, we use the grid-column property to position it. We add a new CSS class with the declaration grid-column: 1 / 3; to style the zero button and set its position in the grid layout.To align the result element to the right of its cell, we can use the justify-content property with a value of end. This will push the contents of our result element to the right. We can also set the align-items property to center and add some padding to the right side using the padding-right property, to make it look more visually pleasing. Depending on the font size, you may need to manually adjust the padding-right value.By using these declarations, we have aligned the result element to the right side of its cell while keeping it centered vertically.To make our buttons look sleek and professional, we need to center their content. Luckily, we can easily achieve this with CSS flexbox. By adding display: flex to our .calculator__key CSS class, we can turn each button into a flex container. This allows us to use align-items and justify-content properties to align the content of our buttons both horizontally and vertically.In this case, we want to center the text inside each button. To do this, we simply add the following declaration to our .calculator__key CSS class:By making these declarations, the content of all our buttons will now be centered both horizontally and vertically within their respective cells in the grid layout.To make the calculator look like the real deal, we can change the background and text colors of the result and buttons. It's a simple fix. Here's an easy implementation using the background property to adjust the background color of these elements:Check out the demo below:In this post, we explored how to create a macOS-style calculator layout using HTML and CSS. We learned how to use the grid-template-columns and grid-template-rows properties to define the number of columns and rows in our grid layout.Additionally, we discovered how to use the grid-column property to adjust the placement of a grid item. By using align-items, justify-content, and display properties with flexbox, we were able to align the content of our buttons both horizontally and vertically.As you can see, the macOS calculator layout is just one example of the many amazing things that can be achieved with CSS grid.If you found this series helpful, please consider giving the repository a star on GitHub or sharing the post on your favorite social networks 😍. Your support would mean a lot to me!If you want more helpful content like this, feel free to follow me:Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Joseph - Feb 17                          Pieces 🌟 - Mar 1                          Raza - Feb 21                          Siddhartha Mishra - Feb 18                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

Create a macOS calculator layout. Before we get into the details, here's the final layout we'll be creating:. To align the result element to the right of its cell, we can use the justify-content property with a value of end.. Additionally, we discovered how to use the grid-column property to adjust the placement of a grid item.

Create a macOS calculator layout

GitHub Enterprise Server adds deployment rollout controls

Posted on Mar 7                      • Originally published at browsercat.com                   Visual tests are a powerful tool, but they're hell to work with in CI/CD. They're slow, flaky, a pain to debug, and difficult to maintain.Getting them going is no easy task. After all, you need some way to store the snapshots between runs, and you need some way to let your pipeline know when it's OK to update the snapshot cache.Thankfully, I took care of all this for you. :)This article solves all of these problems, and lays the foundation for you to take your visual tests to the next level.If you get value here, you'll love my Ultimate Guide to Visual Testing in Playwright. It covers advanced testing techniques, fine-tuning your snapshot configuration, and more.Let's get started...Your CI/CD environment is not like your local environment, and we should account for that in our Playwright configuration.Update your playwright.config.ts with the following options. Feel free to merge these with any other options you've set so far:Here's what's going on:Next, let's create a basic pipeline. It doesn't do everything (yet), but it's a solid foundation to work from.Create a file at .github/workflows/visual-tests.yml:Notice that we're running our tests with the --ignore-snapshots flag. Since we have no way to store snapshots between test runs, this is literally the only way to get our tests to pass.If you push your repo to Github now, this workflow will run, and it will pass, but it won't guarantee anything about your app.Let's remedy that...For our visual tests to work, we'll need to store snapshots between runs. For this, we'll cache them using Github's "artifacts" feature.Second, let's also write a step that generates new snapshots if they don't exist. This will solve the problem of our tests failing the first time they run on a branch.Third, let's stop ignoring our snapshot assertions.Here's the updates:Notice that our cache key includes the current branch as well as a fallback to the master branch. That way a new branch has some material to work from on the first push.If you trigger the pipeline now, on the first run, you'll see snapshots generated, the tests pass, and the cache updated. On subsequent runs, you'll see the cache hit, no new snapshots generated, and the tests still pass.Not bad, but what happens when the snapshots need to be updated?Now that we have visual tests that really work, let's change our workflow so that we can update snapshots on demand.First, let's parameterize our workflow...workflow_call allows us to manually trigger the workflow with or without updating snapshots. workflow_dispatch allows other Github workflows the same set of options.Here's what the manual widget looks like:Let's also update "Initialize snapshots" to trigger an update when this parameter is enabled:Lastly, let's upload our HTML report as an artifact, so that we can reference it before deciding if we should ask the workflow to update snapshots... or if we need to debug the problem:Notice that our "Test" step now enables continue-on-error, so that we can upload our report even if the tests fail.The new "Upload test report" step uploads the report as an artifact. In the workflow results, you'll see a direct link to a zip file containing our report.Things are going great, but there's one more thing we can do to make visual tests even better: make them blazingly fast!You've probably noticed two steps are slowing your pipeline down:Thankfully, we can fix both of these issues, and most-likely for free!BrowserCat hosts a fleet of Playwright browsers in the cloud that you can connect to with just a few lines of code.If you do so, you won't have to install browsers in your CI/CD environment, and you'll be able to run your tests entirely in parallel.And the best part? BrowserCat has an awesome forever-free plan. Unless you're running a huge team, you'll probably never have to pay a dime.So let's get started!First, sign up for a free account at BrowserCat.Second, create an API key and store it as a secret named BROWSERCAT_API_KEY in your Github repository. You can do this by navigating to your repository, clicking "Settings," then "Secrets," then "Actions," then "New repository secret."Third, let's update playwright.config.ts to use BrowserCat:In the updates above, you'll notice we've increased parallelization to 10 workers when using BrowserCat. This is a good starting point, but you can increase it significantly more without issue.Notice that this config connects to BrowserCat whenever BROWSERCAT_API_KEY is defined. This is useful for running tests locally, as well as in CI/CD.OK, now here's the last bit of magic... Let's stop installing Playwright's browsers every time we run our pipeline:If you run your pipeline now, you'll witness a dramatic speed-up, even with just a single test in your suite. And with 1000 free credits per month, you can run your pipeline for hours on end with plenty of time left over.You've got your CI/CD pipeline working. Now it's time to write some tests!Be sure to check out my Ultimate Guide to Visual Testing in Playwright for advanced snapshot testing strategies and ready-made solutions for running visual tests in CI/CD.In the meantime, happy testing!Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Karen Payne - Feb 24                          Clifton Beale - Feb 1                          Gregor Schafroth - Feb 1                          Mohamed Jubair - Feb 29                  DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

How to Run Snapshot Tests in CI/CD with Playwright. If you run your pipeline now, you'll witness a dramatic speed-up, even with just a single test in your suite.