Category: Server Management

Website monitoring is the process of checking the availability, performance, and functionality of a website.

It’s an essential, and on-going task for web developers and owners to ensure that their websites are always online, fast, and user-friendly.

Effective website monitoring can help detect and resolve issues, prevent downtime, improve user experience, and optimize website performance.

UptimeRobot is a service that monitors your website’s uptime and alerts you when it goes down. By integrating UptimeRobot with RunCloud, you can monitor all of your websites hosted on RunCloud servers, and access a number of features and benefits from both.

In this article, we will show you how to use UptimeRobot and RunCloud together for website monitoring. We’ll cover the following topics:

• What is UptimeRobot and how does it work?
• How to integrate UptimeRobot with RunCloud to monitor websites hosted on RunCloud servers.
• Tips and best practices for website monitoring with UptimeRobot and RunCloud.

Understanding UptimeRobot

UptimeRobot is a service that monitors your website’s uptime and alerts you when it goes down.

It achieves this by sending requests to your website at regular intervals and checking the response status code, response time, and keyword presence. If the response is not satisfactory, UptimeRobot will notify you via email, SMS, webhook, or other method of your choice.

UptimeRobot has several features and benefits that make it a popular choice for website monitoring. Some of them are:

• Free and paid plans: UptimeRobot offers a free plan that allows you to monitor up to 50 websites with 5-minute intervals, and 2 alert contacts. You can also upgrade to a paid plan that gives you more websites, shorter intervals, more alert contacts, advanced settings, and premium support.
• Multiple types of checks: UptimeRobot supports different types of checks for your websites, such as HTTP(S), ping, port, keyword, and heartbeat. You can choose the type of check that suits your website’s needs – and customize the settings accordingly.
• Various notification methods: UptimeRobot can alert you via various methods should your website go down or come back up. You can choose from email, SMS, voice call, webhook, Telegram, Slack, Discord, Pushbullet, Pushover, and more. You can also set different alert contacts for different websites and scenarios.
• Status pages: UptimeRobot allows you to create public or private status pages for your websites. You can display the uptime and performance data of your websites on these pages, and share them with your visitors or clients if you wish. You can also customize the look and feel of your status pages with your own logo, domain name, colors, etc.

Different Monitor Types

UptimeRobot supports different types of monitors to check the availability, performance, and functionality of websites or web services. Here is a brief explanation of each type of monitor:

• HTTP: This type of monitor sends an HTTP or HTTPS request to a website, and checks the response status code and response time. If the status code is not 2xx (success) or 3xx (redirection), or if the response time exceeds a certain threshold, the monitor will alert you that the website is either down, or slow.
• Keyword: This monitor also sends an HTTP or HTTPS request to a website, but it checks the presence or absence of a specific word or phrase in the response body (typically HTML or JSON). You can choose to be alerted if the keyword is either found or not found on the website. This can help you verify the content or functionality of your website.
• Ping: This type of monitor sends an ICMP ping packet to an IP address or a domain name, and checks both the response time and packet loss. If the response time is too high, or if there is no response at all, the monitor will alert you that the device is unreachable or slow. This can help you check the network connectivity and availability of your servers or devices.
• Port: This type of monitor sends a TCP or UDP packet to a specific port on an IP address or a domain name, and checks if the port is open and listening. If the port is closed or filtered, the monitor will alert you that the service is down or inaccessible. This can help you check the status and performance of various services running on your servers or devices, such as email, database, FTP, SSH, etc.
• Heartbeat: This type of monitor requires you to send an HTTP request to a specific URL provided by UptimeRobot at regular intervals from your own server or device. If UptimeRobot does not receive a request within a certain time frame, the monitor will alert you that the server or device is down or malfunctioning. This can help you monitor recurring background jobs or intranet devices connected to the internet.

You can choose the type of monitor that suits your website’s needs, and customize the settings accordingly.

Setting-up UptimeRobot

To use UptimeRobot to monitor your websites, you’ll need to follow these steps:

1. Sign up for a free or paid account on UptimeRobot, and log in to your dashboard. On the top left corner, click on “Add New Monitor” to create your first monitor.

2. Provide a suitable name for your monitor, and enter the URL of your website that needs to be monitored. Here you can also specify the frequency of your tests and other basic configuration.

3. Next, configure the alert settings by selecting the notification methods and contacts for each monitor. If your website experience crashes, these notification channels will be used to notify the specified contact(s).
4. Optionally, you can create status pages for your monitors by choosing the template and options. Status pages are public pages that you can display to your customers or other stakeholders to track the health of your service.

After you have performed the above steps, you can enjoy peace of mind – UptimeRobot will now keep an eye on your websites, and notify you if anything goes wrong.

Understanding UptimeRobot Teams

Team member functionality on UptimeRobot is a feature that allows you to add your team members to your UptimeRobot account, and assign them different levels of access and notification.

You can use this feature to collaborate with your team members on website monitoring, and keep them informed of any issues or updates.

There are two types of team members that you can add on UptimeRobot:

1. Read or write access: These are team members who can log in to your UptimeRobot account with their own credentials and perform actions such as adding, editing, or deleting monitors, alert contacts, or status pages. You can choose to give them read-only or read-write access depending on their role and responsibility. You can also choose which monitors, alert contacts, or status pages they can access or manage.
2. Notify-only: These are team members who cannot log in to your UptimeRobot account but can receive notifications via email, SMS, or voice call when your monitors go down or come back up. You can add them as alert contacts and assign them to specific monitors. You can also customize the notification frequency and content for them.

Dos and Don’ts For Using UptimeRobot

Here are some tips and best practices for website monitoring with UptimeRobot and RunCloud:

Choose the right type of check and interval for your website

Depending on the nature and purpose of your website, you may want to use different types of checks and intervals to monitor its uptime and performance.

For example, if your website is a static HTML page, you may use a simple HTTP(S) check with a 5-minute interval. But if your website is a dynamic web application that relies on a database or an API, you may use a keyword or a heartbeat check with a 1-minute interval.

Use multiple alert contacts and methods for different scenarios

You may want to notify different people or teams when your website goes down or comes back online. For example, you may want to alert your web developer via email and SMS when your website goes down, but only alert your marketing manager via email when your website comes back up.

You can also use different notification methods for different urgency levels. For example, you may want to use a voice call for critical issues, but only use a webhook for minor issues.

Create status pages for your websites and share them with your clients

Status pages are a great way to communicate the uptime and performance of your websites to your visitors or clients. These pages can help you build trust and transparency with your audience, and reduce the number of support requests.

You can create public or private status pages for your websites using UptimeRobot, and customize them with your own logo, domain name, colors, etc.

Don’t rely on a single type of monitor, or a single alert method.

You may miss some issues or receive false positives if you only use one type of monitor or one alert method. You should use multiple types of monitors and alert methods to cover different scenarios, and ensure that you receive timely and accurate notifications.

Don’t set unrealistic expectations for your website uptime

You should understand that no website can achieve 100% uptime or perfect performance all the time. There are many factors that can affect your website’s availability and speed, such as network issues, server issues, code issues, traffic spikes, etc.

You should set realistic and reasonable goals for your website uptime and performance, and measure them against industry standards and best practices.

Final Thoughts

Website monitoring is a vital part of your web development and maintenance strategy. It can help you ensure that your websites are always online, fast, and user-friendly. By using website monitoring tools such as UptimeRobot, you can detect and resolve issues, prevent downtime, improve user experience, and optimize website performance.

But wait, there’s more! If you are looking for the best cloud hosting service provider for your websites, look no further than RunCloud.

RunCloud is a platform that allows you to easily manage your web servers and web applications on any cloud provider.

RunCloud lets you choose from a variety of cloud providers such as AWS, Google Cloud, DigitalOcean, Vultr, Linode, etc. and connect them to RunCloud with just a few clicks. You can then enjoy the benefits of RunCloud’s optimized web stack, backup, deployment, team collaboration, analytics, optimizer, and much more.

What are you waiting for? Join RunCloud today and take your website hosting to the next level!

Is your website suffering from frequent outages and unexpected downtime? If yes, then you should look into Synthetic monitoring.

Synthetic monitoring is a proactive way to monitor the performance and availability of your web applications and services by simulating user requests and actions from different locations. Synthetic monitoring helps you to:

• Detect issues before they affect your real users
• Ensure consistent user experience across devices and browsers
• Measure service level agreements (SLAs) and objectives (SLOs)
• Optimize your web performance and reliability.

RunCloud allows you to manage your cloud servers with ease, and you can also integrate RunCloud with Datadog to monitor your server metrics, logs, and events.

Datadog is a cloud-based platform that provides synthetic monitoring solutions for API, browser, and mobile tests. You can create and manage different types of synthetic tests with Datadog, such as API tests, multistep API tests, browser tests, or private locations.

In this post, you will learn how to use Datadog and RunCloud together to monitor your web applications and servers with synthetic monitoring. You will also see how to create and manage synthetic tests with Datadog, analyze and troubleshoot synthetic test results with Datadog, and set up alerts, dashboards, and reports for your synthetic tests with Datadog.

Let’s get started!

Setting up Datadog and RunCloud

Before you can use Datadog and RunCloud for synthetic monitoring, you’ll need to create an account on both platforms, and install the Datadog agent on your RunCloud server. Here are the steps to do that:

• Creating an account on Datadog: Go to the Datadog website and click on the “Get Started” button.
• Logging in to your server via SSH: You need to connect to your server with superuser privileges to install the monitoring agent. Read our guide on configuring SSH to learn more.

• Install the Datadog agent on your RunCloud server: The Datadog agent is a tool that collects and sends metrics, logs, and events from your server to Datadog. To install the Datadog agent, follow these steps:
  • Go to the Datadog dashboard and click on the “Integrations” button.
  • Select “Datadog Agent” from the list and click on the “Ubuntu” tab to view the installation command.

• Copy the Installation Script and paste it in your terminal. This will start the installation process – wait for the installation to complete.

You have successfully set up Datadog and RunCloud for synthetic monitoring. After installation, the agent will start sending data within a few minutes. Once you get the message “Your first Datadog Agent is reporting. Congrats!”, you can click on the “Finish →” button to complete the installation.

In the next section, you will learn how to create and manage synthetic tests with Datadog.

Creating and managing synthetic tests with Datadog

Synthetic tests are simulated user requests and actions that you can create and run with Datadog to monitor the performance and availability of your web applications and services. Datadog supports three types of synthetic tests: API tests, multistep API tests, and browser tests.

• API tests: API tests are HTTP requests that you can send to your API endpoints and verify the response status code, body, headers, or latency. You can use API tests to check the functionality, performance, and reliability of your API endpoints. You can also chain multiple API tests together to create multi step API tests.
• Multistep API tests: Multistep API tests are sequences of API tests that you can use to simulate complex user journeys or workflows involving multiple API calls. You can use multistep API tests to check the end-to-end functionality, performance, and reliability of your web applications and services. You can also extract variables from one API test and use them in another API test within the same multi step test.
• Browser tests: Browser tests are user interactions that you can record and replay with a headless browser to monitor the performance and availability of your web pages. You can use browser tests to check the functionality, performance, and reliability of your web pages. You can also add assertions, variables, screenshots, or video recordings to your browser tests.

In addition to this, you can also run tests from private locations. Private locations are dedicated machines that you can use to run synthetic tests from your own network or infrastructure. You can use private locations to monitor internal or private web applications and services that are not accessible from the public internet.

To create tests with Datadog, follow these steps:

• On your Datadog dashboard, click on “UX Monitoring” tab and go to the “Synthetics” page.
• Click on the “New Test” button and choose the type of synthetic test you want to create: API test, multistep API test, or browser test.

• Follow the instructions on the screen to configure your synthetic test settings, such as the test name, URL, frequency, locations, assertions, variables, screenshots, video recordings, etc.
• Click on the “Save Test” button to save your synthetic test. After you have created a synthetic test with Datadog, it will be executed automatically according to the specified interval.

Analyzing and Troubleshooting Synthetic Monitoring Results

You can use synthetic test results to identify and resolve issues that affect your web performance and reliability. To access and interpret synthetic test results with Datadog, follow these steps:

• Click on the synthetic test that you want to analyze. You will see the Test Details page, which shows the latest test result, and the historical test results for that synthetic test.
• On the Test Details page, you can see various information about your synthetic test result, such as the test status, duration, response time, latency, errors, screenshots, video recordings, APM traces, etc. You can use this information to evaluate the performance and availability of your web applications and services. You can also compare different test results over time or across locations to identify trends or anomalies.
• If your synthetic test result shows an error or a failure, you can use the Error Panel to see the details of the error or failure, such as the error message, stack trace, screenshot, video recording, APM trace, etc. You can use this information to troubleshoot and fix the issue that caused the error or failure. You can also click on the “Share” button to share the error details with your team or stakeholders via email or Slack.

Summary

Synthetic monitoring is a proactive way to monitor the performance and availability of your web applications and services by simulating user requests and actions from different locations. In this post, you have learned how to use Datadog and RunCloud for synthetic monitoring.

By using Datadog and RunCloud together, you can monitor your web applications and servers with synthetic monitoring in a simple and efficient way. You can also benefit from the features and capabilities of both platforms to improve your web performance and reliability.

If you want to start using RunCloud for your web hosting needs, you can sign up for a free trial. RunCloud makes server management easy by providing you with a user-friendly interface, a powerful script installer, a robust security system, and a flexible backup system.

In today’s digital landscape, the smooth operation of web applications is crucial to business success, and the performance and reliability of your server infrastructure cannot be overstated.

Server monitoring protects your applications against unexpected downtimes and performance bottlenecks, as well as valuable insights into the health, performance, and security of your infrastructure.

Dynatrace is a cutting-edge observability platform designed to provide real-time insights into the performance of your web applications and the underlying server infrastructure.

In this article, we’ll explore how to use Dynatrace to monitor your RunCloud servers, maximize uptime, and supercharge your web application’s performance.

Let’s get started!

Setting Up Dynatrace for RunCloud Servers

Prerequisites

Before you can start using Dynatrace to monitor your RunCloud servers, you’ll need to ensure you meet the following prerequisites:

1. RunCloud Account: You should have an active RunCloud account with at least one server connected to it. If you haven’t set this up yet, visit the RunCloud docs for detailed instructions on getting started.
2. SSH Access: Open your preferred SSH client or terminal. Use the SSH credentials associated with your RunCloud server to establish an SSH connection. Ensure that you have the required SSH access to execute commands on the server where you intend to install Dynatrace, and integrate it with your RunCloud-managed infrastructure. This access is essential for a successful Dynatrace installation and integration.

Once you have these prerequisites in place, you’re ready to move on to the installation process.

Dynatrace Installation

1. Access the Dynatrace Dashboard: Log in to your Dynatrace account and to view the Dynatrace dashboard. In the dashboard, look for the “Start collecting data” option. Click on it to begin the setup process.

2. Choose One Agent: On the next screen, you’ll have the option to choose the type of agent you want to install. Select “One Agent“. On the next screen, click “Set up“.

3. Generate PaaS Token: Since we’re working with a RunCloud server, choose the “Linux” option for the type of environment. After selecting the Linux option, you’ll be presented with instructions on how to generate a PaaS token. This token is essential for establishing the connection between Dynatrace and your RunCloud server. Click on the “Create Token” button to generate the PaaS token.

4. Execute Commands: Once you’ve generated the PaaS token, a set of commands will be provided. These commands need to be executed in your SSH terminal on your RunCloud server. These commands will install and configure the Dynatrace agent on your server.

Ensure that you follow each step carefully to complete the installation process successfully. Once the installation is complete, the Dynatrace agent will start collecting data from your server, and you will see your server in the Dynatrace dashboard.

Monitoring Real-time Server Health

After successfully installing the Dynatrace agent, you’ll need to wait for a few minutes to allow the data to populate in your Dynatrace dashboard. Once the data from your RunCloud server is connected and visible in Dynatrace, you can start taking advantage of the powerful features that Dynatrace offers.

Creating Custom Dashboards:

Custom dashboards in Dynatrace allow you to tailor the monitoring experience to your specific needs, helping you keep an eye on the most important metrics for your application. Follow these steps to create a custom dashboard:

1. Create a New Dashboard: In your Dynatrace account, navigate to the Dashboard section. Click on the “+ Dashboard” button on the top left corner. Give your dashboard a meaningful name that reflects its purpose.
2. Add Tiles: Within your dashboard, you can add tiles representing various metrics such as response times, error rates, CPU usage, memory utilization, and more. Click the “+” button on the top right part of the dashboard and select the metrics you want to monitor.

3. Configure Tiles: Customize each tile by selecting the specific metric, filtering options, and visualization preferences. You can resize, move, and arrange the tiles to create an intuitive layout.
4. Save Your Dashboard: Once you’re satisfied with your custom dashboard, save it. You can access this dashboard anytime to get a quick overview of the metrics that matter most to you.

Setting Up Service-Level Objectives (SLOs)

SLOs in Dynatrace help you define performance goals for your applications, and measure how well they meet those goals. To set up SLOs:

1. Navigate to SLO Management: In the Dynatrace menu, find the “SLO” section (sometimes under “Settings” or a similar category).
2. Create a New SLO: Click on “Create SLO” or a similar button to start creating a new Service-Level Objective.
3. Define the SLO: Name your SLO, specify the application or service it applies to, set the target performance threshold (e.g., response time under 500ms), and choose the evaluation window (e.g., last 7 days).
4. Save the SLO: Once you’ve configured your SLO, save it. Dynatrace will continuously monitor your application’s performance against the defined objectives.
5. Review and Optimize: Regularly review the SLO performance data. If an SLO is frequently breached, consider optimizing your application or infrastructure to meet the defined objectives.

Key Metrics to Monitor

1. CPU Utilization

Monitoring the CPU utilization of your servers is essential to understand their processing capacity and identify potential bottlenecks. This enables you to spot any spikes or consistently high usage that might indicate performance issues. By integrating Dynatrace with RunCloud, you can seamlessly access this critical metric, allowing you to make informed decisions about resource allocation – and ensure optimal server performance.

2. Memory Usage

Memory is a finite resource, and efficient management is crucial to maintain stable server operation. Having real-time insights into memory consumption trends allows you to identify potential memory leaks or unusually high usage patterns. This ensures that you can proactively address memory-related issues before they impact application stability.

3. Network Performance

Network connectivity is the lifeline of any web server. Monitoring network performance is vital to ensure smooth data transfer between servers and clients. Comprehensively tracking network performance metrics, such as latency, packet loss, and network throughput, allows you to detect network anomalies, troubleshoot connectivity issues, and optimize your application’s responsiveness to deliver a seamless user experience.

Final Thoughts

The old adage “prevention is better than cure” couldn’t be more applicable to server management. Dynatrace equips you with the ability to detect anomalies before they impact users, allowing you to resolve issues before they become critical.

The proactive monitoring approach ensures that you stay one step ahead, maintaining a smooth user experience and reducing downtime to an absolute minimum.

While Dynatrace supercharges your monitoring capabilities, RunCloud serves as an exceptional cloud management platform that simplifies server management, saving you time and effort. With RunCloud, you can effortlessly manage your servers, deploy applications, and enjoy a user-friendly interface that streamlines tasks. Start using RunCloud today!

Email testing is an essential part of any email marketing campaign. It allows you to check the quality, functionality, and deliverability of your emails before you send them to your subscribers.

However, email testing can also be a frustrating and time-consuming process, and this is where local email testing can help.

Local email testing means that you send your emails from your local development environment to your own email address, or to a test email account. This way, you can see how your emails look and behave in different email clients and devices without affecting your actual subscribers – or your reputation.

Caveats with Traditional Email Testing

It’s important to be aware that email testing can come with some common problems or challenges, such as:

• Spam filters: Your emails may end up in the spam folder or be blocked by the email provider due to various reasons, such as invalid sender address, poor content quality, suspicious links, etc.
• Delay in SMTP servers: Your emails may not be sent or received at all due to the limitations or errors of the SMTP server that you use to send your emails locally. You may have to configure the SMTP settings manually or use a third-party service to send your emails.

These problems can make email testing a tedious and unreliable process. You may waste a lot of time and effort in testing your emails locally without getting the results that you want.

That’s why you need a better way to test your emails locally.

That’s where MailHog comes in.

By the end of this article, you will be able to use MailHog to test your emails locally with maximum effectiveness. This will significantly help you improve the quality, functionality, and deliverability of your emails before you send them to your subscribers.

Are you ready to learn how to use MailHog to test your emails locally? Let’s get started!

What is MailHog?

MailHog is a simple and powerful tool that can transform your local email testing process. It can easily help you test your emails locally without any hassle or headache, and can help you fix the problems that you’re currently facing when testing your emails locally.

Why use MailHog?

Local email testing can help you improve the quality, functionality, and deliverability of your emails before you send them to your subscribers. It can also save you time and hassle in testing your emails. Here are some of the benefits of local email testing:

• It is instantaneous: You don’t need to wait for network delays or server issues to see how your emails look and behave. You can test your emails in real time and get immediate feedback.
• It saves email quota. Sending too many emails might reduce your spam score or trigger spam filters. By testing your emails locally, you can avoid wasting your email quota or damaging your email reputation.
• It prevents accidentally sending to real customers if there is a bug in your code. Sometimes, you may have errors or typos in your code that could cause your emails to be sent to the wrong recipients or with the wrong content. By testing your emails locally, you can catch these mistakes before they cause any harm or embarrassment.
• It allows you to simulate situations where the communication between your program and the email server is interrupted or degraded due to various reasons, such as network congestion, packet loss, latency, etc. These faults can cause your emails to be delayed, corrupted, or lost. By testing emails locally you can create and control these network faults and test how your program behaves under these conditions.

Jim: The Chaos Monkey

MailHog comes with an interesting extension, Jim – a chaos monkey. It’s a tool that simulates random failures and disruptions in your email system. This is useful for testing the resilience and reliability of your email system, as well as your ability to handle, and recover from, unexpected errors.

By inviting Jim to your email testing, you can expose and fix any weaknesses or vulnerabilities in your email system. You can also learn how to build better automatic recovery mechanisms, and improve the quality, functionality, and deliverability of your emails.

For example, you can test how your program handles the following scenarios:

• Rejecting incoming connections with a certain probability
• Disconnecting sessions randomly
• Applying a rate limit to connections
• Rejecting authentication attempts
• Rejecting a sender’s or recipient’s address

By using these tools, you can see how your program reacts to different types of network faults – and whether it can recover from them gracefully. You can also improve your error handling and logging mechanisms and make your program more robust and resilient.

How To Use MailHog

Here is a step-by-step guide on how to install and set up MailHog on your local machine, and configure it to capture and display the emails that you send from your application:

1. Download MailHog from its GitHub repository. You can choose the version that suits your operating system and architecture. For example, if you are using Windows 10 64-bit, you can download the file named mailhog_windows_amd64.exe.
2. Save the downloaded file in a folder of your choice. For example, you can create a folder named mailhog in your C:\ drive and save the file there.
3. Open a command prompt window and navigate to the folder where you saved the MailHog file. For example, you can type cd C:\mailhog and press ‘Enter’.
4. Run the MailHog file by typing its name and pressing ‘Enter’. For example, you can type mailhog_windows_amd64.exe and press ‘Enter’. You should see a message saying that MailHog is listening on port 1025 for SMTP and port 8025 for HTTP.

5. Open a web browser and go to http://localhost:8025. You should see the MailHog web interface, which shows the list of emails that MailHog has captured.

6.  Configure your application to send emails to MailHog instead of your actual SMTP server. You can do this by changing the SMTP settings in your application to use localhost as the host name and 1025 as the port number.
   You can also use any username and password for authentication, as MailHog doesn’t check them. 

For WordPress Sites

There are many WordPress plugins that allow you to send emails using a specific mail server. You can configure them to use MailHog to test your email. After sending the email, you can view the email in the MailHog dashboard.

For Generic PHP Applications

If you are using PHPMailer to send emails from your PHP application, you can use the following code snippet to send emails to MailHog server:

<?php
// Load PHPMailer library
require 'PHPMailerAutoload.php';
// Create a new PHPMailer instance
$mail = new PHPMailer;
// Set Mailer to use SMTP
$mail->isSMTP();
// Set SMTP host name
$mail->Host = 'localhost';
// Set SMTP port number
$mail->Port = 1025;
// Set SMTP username
$mail->Username = 'anyusername';
// Set SMTP password
$mail->Password = 'anypassword';
// Set email subject
$mail->Subject = 'Test email from MailHog';
// Set email body
$mail->Body = 'This is a test email sent from MailHog';
// Set email sender address
$mail->setFrom('sender@example.com', 'Sender Name');
// Set email recipient address
$mail->addAddress('recipient@example.com', 'Recipient Name');
// Send email
if ($mail->send()) {
    echo 'Email sent successfully';
} else {
    echo 'Email sending failed: ' . $mail->ErrorInfo;
} ?>

7. Test your application by sending an email from it. You should see the email appear in the MailHog web interface. You can also open the email and check its content, layout, design, attachments, links, etc.

Conclusion

MailHog is a simple and powerful tool that can transform your local email testing process. In this article we have shown how to use MailHog to test your emails locally and fix the common problems or challenges that developers face when testing emails locally, such as spam filters, email clients, SMTP servers, etc.

If you are looking for a great cloud management platform that saves time and doesn’t require you to be a Linux expert, we recommend you check out RunCloud.

RunCloud is a modern web server panel designed to help you manage your PHP web applications and websites.

With RunCloud, you don’t need to be a Linux expert to build a website, and you can host it on a cloud provider of your choice such as Vultr, Linode, UpCloud, Hetzner, AWS, Google Cloud or DigitalOcean.

Start your free trial today and see for yourself how RunCloud can make your cloud hosting experience easier and better.

Laravel Valet is a local development environment for Mac users who want to create WordPress sites quickly and easily. It’s a lightweight, minimalist tool that uses the built-in PHP server and Nginx to serve your WordPress sites.

Unlike other local development tools, such as MAMP, XAMPP, or Local by Flywheel, Laravel Valet does not require you to configure a virtual host, a database, or a port for each site.

Instead, you can simply create a new site in any directory, and link it to a custom domain name (such as .test) with one command. It also provides automatic HTTPS for your sites, so you can test them securely and avoid browser warnings.

Some of the features and benefits of Laravel Valet are:

• Fast and easy installation: You can install Laravel Valet with Composer and Homebrew in only a few minutes. You don’t need to download or install any bulky software or packages.
• Automatic HTTPS: Laravel Valet uses the mkcert utility to generate and trust SSL certificates for your sites. You can access your sites with HTTPS without any configuration or hassle.
• Custom domain names: Laravel Valet allows you to use any domain name (such as .test, .dev, or .local) for your sites. You can link any directory to a domain name with one command, and access it in the browser.
• Multiple PHP versions: Laravel Valet lets you switch between different PHP versions (such as 7.3, 7.4, or 8.0) with just one command. This enables you to test your sites with different PHP versions without affecting other sites or settings.
• Custom drivers: Laravel Valet supports various frameworks and applications, such as WordPress, Laravel, Symfony, Drupal, etc. You can also create your own custom drivers for any application that you want to use with Valet.

Laravel Valet is a great tool for WordPress developers who want to work locally with speed and simplicity. It’s especially useful for developers who work on multiple WordPress sites or projects at the same time.

In this article, we will show you how to use Laravel Valet to set up a local WordPress dev environment in only a few minutes.

Prerequisites

Before you can use Laravel Valet to create and run WordPress sites, you need to have the following requirements:

• A Mac computer: Laravel Valet is only compatible with macOS. You’ll need to have a Mac computer with macOS Sierra (10.12) or higher.
• Port 80 is free: The websites will be served port 80 of your computer. You should make sure that no other programs, such as Apache or Nginx, are binding to your local machine’s port 80.
• Supported PHP Version: Laravel Valet requires PHP 7.3 or higher to work. You can check your PHP version by running php -v in the terminal.
• Composer: Composer is a dependency manager for PHP. You’ll need to have Composer installed on your Mac in order to install Laravel Valet and other tools.
• Homebrew: Homebrew is a package manager for macOS. You’ll need to have Homebrew installed on your Mac to install some of the dependencies of Laravel Valet, such as Nginx and MySQL.

These are the main prerequisites for using Laravel Valet. If you already have them, you can proceed to the next section. If not, you can follow the links provided to install them on your Mac.

Installing Laravel Valet

To install Laravel Valet on your Mac, you need to follow these steps:

• Open the terminal and run the following command to install Laravel Valet using Composer:

composer global require laravel/valet

• Run the following command to install and start Valet:

valet install

• This command will install Nginx and Dnsmasq using Homebrew, and configure your Mac to use Valet’s drivers. It will also register Valet’s daemon to launch when your system starts.
• By default, Valet will use the .test domain for your sites. If you want to use a different domain, such as .dev or .local, you can run the following command:

valet domain <tld-name>

For example, if you’d like to use .app instead of .test, run valet domain app and Valet will start serving your projects at *.app automatically.

• To check if Valet is running properly, you can run the following command:

valet status

• This command will show you the status of Valet’s services, such as Nginx, Dnsmasq, and PHP. You should see something like this:

Valet services are running:
[OK] Nginx is running
[OK] Dnsmasq is running
[OK] PHP 7.4 is running

• If you see any errors or warnings, you can run the following command to restart Valet:

valet restart

That’s it! You have successfully installed Laravel Valet on your Mac. You are now ready to create and run WordPress sites with Valet.

Installing WordPress

To create a new WordPress site using Laravel Valet, you need to follow these steps:

• Choose a directory where you want to store your WordPress site. For example, you can create a directory called wordpress in your Sites folder:

cd ~/Sites
mkdir wordpress

• Go to the directory and install WordPress using WP-CLI or Composer. You can use either of them to download and install WordPress core files and dependencies. For example, you can use WP-CLI to install WordPress with the following command:

wp core download

• Alternatively, you can use Composer to install WordPress with the following command:

composer create-project roots/wordpress

• Both commands will create a wp-config.php file in your directory. You can edit this file to configure your database settings and other options. You can also use WP-CLI or Composer to install plugins, themes, and other components for your WordPress site.
• Use Valet to link your site directory to a custom domain name. For example, if you want to use wordpress.test as your domain name, you can run the following command:

valet link wordpress
valet open

• This command will create a symbolic link between your site directory and the .test domain. You can also use a different domain name if you want.
• Access your site in the browser. You can now visit your site by typing wordpress.test in the browser. You should see the WordPress installation screen where you can enter your site title, username, password, and email address. After completing the installation, you can log in to your WordPress dashboard and start building your site.
• Use Valet to secure your site with HTTPS. If you want to use HTTPS for your site, you can run the following command:

valet secure wordpress

• This command will generate and trust an SSL certificate for your site using the mkcert utility. You can then access your site with HTTPS by typing https://wordpress.test in the browser. You should see a green lock icon in the address bar indicating that your site is secure.

You have successfully created a new WordPress site using Laravel Valet. You can now enjoy the benefits of a fast and easy local development environment for WordPress.

Troubleshoot Common Issues

If you encounter any problems with Valet or WordPress, you can try some of the following solutions:

• Restart Valet by running valet restart.
• Check the status of Valet by running valet status.
• Check the logs of Valet by running valet logs.
• Check the configuration of Valet by running valet config.
• Unlink and relink your site by running valet unlink wordpress and valet link wordpress.
• Unsecure and resecure your site by running valet unsecure wordpress and valet secure wordpress.
• Update Valet by running composer global update.
• Update WordPress by running wp core update or composer update.

Final Thoughts

In this article, we have covered how to use Laravel Valet to set up a local WordPress dev environment in minutes. Laravel Valet is a great tool for WordPress developers who want to work locally with speed and simplicity. It’s especially useful for developers who work on multiple WordPress sites or projects at the same time.

You can start using Laravel Valet to keep your site directories organized and consistent, such as using a naming convention or a folder structure to group your sites by type, client, or status. For example, you can use clientname-projectname.test as your domain name, or create a clients folder to store all your client sites. For more information and documentation on Laravel Valet, you can visit the official documentation.

Another quick and easy way to set up a testing environment is by creating a staging site on RunCloud. RunCloud lets you focus on your product and takes care of server management. You don’t need to be a Linux expert to host a successful website, start using RunCloud today and see for yourself.

If you’re looking for a free and open-source solution to manage your customers, you might want to check out FreeScout.

FreeScout is a web-based customer support system that lets you manage your email conversations with your clients and customers. You can also add modules for live chat, knowledge base, reports, and more.

The official Wiki page provides detailed instructions and tips for installing FreeScout on a fresh server. However, if you’re using RunCloud to manage your servers, this process is much simpler. You don’t need to worry about installing and configuring any server software, such as Nginx, PHP, and MySQL. You can just create a web app on RunCloud – and follow the steps in this article to install FreeScout in minutes.

By the end of this article, you’ll have a fully functional FreeScout system that you can use to provide awesome customer service. Sounds good? Then let’s get started!

Step 1: Create an Empty Web Application

First, you need to create a blank web app on RunCloud. A web app is a way of telling RunCloud how to run your website. To do this, you’ll first need to log in to your RunCloud dashboard.

On the RunCloud dashboard, you will see a button that says “Create Web Application”. Click on it, and you will see a form where you can enter some details about your web app.

You need to enter a name for your web app, such as “FreeScout”. You also need to enter a domain name for your web app, such as “freescout.example.com”. This is the address where people can access your website. You can either use your own domain name, or get a free one from RunCloud for testing purposes.

After you enter the name and the domain, you will see some options for the application type and the public path. These are settings that tell RunCloud how to run your web app. For now, leave them as they are and click on “Create Web Application”. RunCloud will create a blank web app for you and show you some information about it.

Step 2: Log in via SSH

You’ll next need to connect to your server using SSH. After logging in, the first thing you need to do is change the directory to the web app root directory. This is the folder where your web app files are stored. You can do this by typing cd <path> and pressing “Enter“, where <path> is the path to the root directory of your web application – you can get this from your RunCloud dashboard.

Step 3: Download FreeScout

After that, you need to download the latest version of FreeScout on your server. To download FreeScout, visit https://github.com/freescout-helpdesk/freescout/releases/latest and copy the download link for the latest release. It should look something like https://github.com/freescout-helpdesk/freescout/archive/refs/tags/1.8.86.tar.gz.

Next, you’ll need to use wget to download the zip file to your server. To use wget, type “wget” followed by the download link and press “Enter“.

For example:

wget https://github.com/freescout-helpdesk/freescout/archive/refs/tags/1.8.86.tar.gz.

Step 4: Extract the Archive

After downloading the file, type ls and press “Enter“. This will show you a list of everything that is present in the current directory. If you followed the steps correctly, your output will look something like this:

Next, you’ll need to extract the files from the archive file. To extract the files, type tar -xf followed by the name of the archive file, and press “Enter“.

For example:

tar -xf 1.8.86.tar.gz.

This will create a folder named freescout-x.x.xx, where x.x.xx is the version number of FreeScout. Inside this folder, you will find all the files and folders that make up FreeScout.

Step 5: Move the Contents

Next, you should move the files from the freescout-x.x.xx folder to the root of your application. You can do this by using cp -r followed by ./freescout-x.x.xx/* and . and press “Enter“. For example, your command should look something like this:

cp -r ./freescout-1.8.86/* .

This will copy all the files and folders from the freescout-x.x.xx folder to the current directory. After that, you can delete the downloaded file and the freescout-x.x.xx folder because you don’t need them anymore. You can also remove the default index.html file. You can do this by using rm -rf and then the name of the file or folder, and press “Enter“.

rm -rf freescout-1.8.86/
rm 1.8.86.tar.gz
rm index.html

Step 6: Create the .env File

The next step us to create a file named .env.example in the current directory. This file will store your FreeScout configuration settings, such as your database name and password. To create this file, run the following command: touch .env.example.

Step 7: Update the Application Settings

Next, you’ll need to update your web application settings. Go back to your RunCloud dashboard and click on the “Settings” tab. Under the “Stack” sub-section, you will see a option for the application type and the public path. These are settings that tell RunCloud how to run your web app.

FreeScout uses the Laravel framework to run. The public path is the folder where your web app files are accessible from the internet. You should change the application type to Laravel and set the public path to /public.

After you change these settings, click on “Update Stack”. RunCloud will apply the changes and restart your web app. As a result, you will see a new section of Laravel settings in the left menu.

Next, scroll down to the PHP settings section, and look for the symlink function in the disabled functions list and delete it – make sure you delete the trailing comma as well.

After removing the function from the disabled list, click on the “Update PHP Settings” button to save the settings.

Step 8: Create a Database and User

Finally, you’ll need to finish the installation by opening your web browser and going to your web app domain. You should see the FreeScout installation wizard. This is a page where you can enter some details about your FreeScout system, such as your email and password. You also need to create a database and a user for FreeScout.

To create a database and a user, you can use RunCloud’s database manager. You can find this in the RunCloud dashboard under the “Database” tab. Follow our tutorial on creating a database to learn more.

After creating the user, granting them access to a database, and connecting that database to your web application, go back to the FreeScout installation wizard and enter the same details that you used to create the database and the user. Make sure you have selected the MySQL option in the database connection drop-down, and leave the hostname and port as default.

If everything is okay, you can proceed with the installation by clicking on “Install”. FreeScout will install itself on your server and then show you a success message.

Final Thoughts

As you can see, installing FreeScout on Ubuntu using RunCloud is easy and fast. You don’t need to be a Linux expert or spend hours configuring your server. You can leave the hard work to us and focus on your projects.

RunCloud lets you manage your web apps with a simple and intuitive interface. You can create, deploy, and scale your web apps with just a few clicks. You can also monitor your server performance, secure your web apps, and automate your tasks with RunCloud.

With RunCloud, you can save time, money, and hassle. You can run any web app on any cloud server provider, such as DigitalOcean, AWS, Google Cloud, and more. You can also enjoy the benefits of RunCloud’s features, such as:

• One-click SSL certificates
• Custom domain names
• Automatic backups
• Firewall and malware protection
• Cron job scheduler
• Git deployment
• And more!

Whether you’re a developer, a freelancer, or a business owner, RunCloud is the perfect solution for you. You can manage your web apps with ease and get support from our friendly team anytime you need it. Sign up for RunCloud today and see how it increases your productivity.

Docker is a technology that allows you to run applications in isolated environments called containers.

Containers are lightweight, portable, and scalable, making them ideal for cloud-native development and deployment.

Did you know that containerization saw a massive leap in adoption in 2022, with over 31% of developers worldwide stating that they are running container technologies?

RunCloud Docker is a server that leverages the popular Docker technology to isolate most of your application dependencies such as Redis, MariaDB, NGINX, PHP, and beyond from the operating system level.

This makes your applications more secure and easier to manage.

But beyond that, this is a big under-the-hood improvement that stands to allow us to continue leveling up on how you manage your servers with RunCloud.

RunCloud provides a simple interface to start and stop these predefined containers. Your web applications are further protected by facl, a UNIX interface to manage access, which prevents them from accessing each other’s files and folders.

Containerized Core is now out of beta and in early access.

This means it’s safe to use in production (while there may still be rare edge-case scenarios as it rolls out across the board).

It’s no longer necessary to be a Linux expert anymore to be able to enjoy the flexibility and security of containerized applications.

Before we proceed, it is important to note that Docker server runs on a containerized environment without a built-in firewall. To secure your server, you need to configure the firewall provided by your cloud provider. If you use DigitalOcean, Linode, Vultr, or AWS Lightsail, RunCloud makes it easy for you to do that from the dashboard itself.

How To Use Docker On RunCloud

RunCloud allows you to easily manage and deploy your web applications on any cloud provider that provides a network firewall using Docker.

To use Docker on RunCloud, you need to create a new server and select the Docker option during the setup installation.

You cannot use Docker on existing servers that are already managed by RunCloud. This is because RunCloud needs to install some packages and configurations that are specific to Docker and may conflict with your existing setup.

Here are the steps needed to create a new server with Docker on RunCloud:

1. Log in to your RunCloud account and click on the “Connect a Server” button.
   
2. Choose your cloud provider and select the provision method. We recommend using RunCloud’s automatic provisioning feature for a painless installation.
   
3. In the “Installation Type” section, select the Docker option. Currently, this method only supports Nginx servers.

4. The next steps will differ slightly depending on your installation method. If you picked the automatic installation, you can select your server configuration and deploy it directly from within the RunCloud dashboard.
   
   If you selected the manual installation, you’ll need to log in to your virtual machine via SSH and run the installation script.
   
   Either way, it’s a straightforward process; refer to our blog post about the installation process for more information.
   
5. Once your server is ready, you can access it from the RunCloud dashboard and start using Docker.

How Docker Enhances Security

Docker provides better security for your application by isolating it from the host operating system and other applications on the same server. Docker containers have their own file system, network stack, and process space, which limits the access and impact of a potential attacker.

Docker also supports various security features that can restrict the capabilities and resources of a container.

For example, if you run a WordPress site in a Docker container and it gets hacked by a malicious actor, the hacker will not be able to interact with the host operating system or other containers on the same server. The hacker will be trapped in the container, and will only have access to the files and processes within it.

In this way, you can protect your server and other applications from being compromised or damaged by a security breach.

How to Upgrade to RunCloud Docker

As we mentioned earlier, if you are using the native variant of RunCloud and want to upgrade to RunCloud Docker, you’ll need to create a new server with Docker, and clone your existing applications from your old server to your new server.

If you don’t have a server with Docker installed, go back to the How To Use Docker On RunCloud section.   

Here are the steps to upgrade from the native servers to RunCloud Docker:

1. Once your new server is ready, you can clone your existing applications from your old server to your new server. To do this, go to the Applications tab on your old server and click on the “Cloning” button. You need to do this individually for each application that you want to clone.

In the above example, the server using Nginx was named “nginx” and the server using Docker was named “docker” for demonstration purposes. These names will vary depending upon your setup.

2. Choose your new server as the destination, and enter a name for the cloned application. You can also choose whether to clone the database and the files of the application. If you are cloning a web application that relies on a database (e.g. WordPress), you must select this option.

Select the database that you want to clone from the drop down menu. The name of the database is generally similar to the name of the application. After this, provide a new name for your database and web application – this will be displayed in the RunCloud dashboard under your new server.

3. After this, you need to select the user account on your server that will be the owner of your web application. You can either pick one of the existing users, or create a new user.

4. Finally, you need to configure the domain name of your application. We recommend using a test domain during migration. This will allow you to access your containerized application and, in the meantime, all the existing traffic will continue to go to your old servers. Once you are satisfied, you can update your test domain. 
5. Click on the Clone Application button and wait for RunCloud to clone your application to your new server. Repeat the above steps for each application you want to clone from your old server to your new server.
6. Once you have cloned all your applications, you’ll need to update the DNS records of your domains to point to your new server. To do this, you can either use RunCloud’s Cloudflare integration, or go to your domain registrar or DNS provider and change the A records or CNAME records of your domains to point to the IP address of your new server.
7. Wait for the DNS changes to propagate, and verify that your applications are working properly on your new server. If you are planning this ahead of time, you should also read our guide on How To Speed Up DNS Propagation.

You have successfully upgraded from the native variant to Containerized Core.

You can now enjoy the benefits of using Docker containers on your new server. You can also log in to your server via SSH to access your new server, and manage your containers via Docker CLI.

Conclusion

Docker is an incredibly powerful tool for creating and running applications in containers. With this improvement to RunCloud’s core powered by containerization – we’re beyond excited for you all to take advantage of the benefits of containerization as well as what this means for the future of managing your infrastructure on RunCloud.

The RunCloud team is committed to delivering the best possible experience to our users across the board. We welcome your feedback and suggestions on how to make it better for you. Please feel free to reach out to us, or join our community forum to share your thoughts and experiences.

You don’t need to be a Linux expert anymore to enjoy the benefits of Docker. With RunCloud, you can create and run isolated web applications with just a few clicks.

Sign up today and see for yourself how easy and convenient it is to use Docker on RunCloud.