First off. What is Monarch.
It’s a premium social sharing plugin for WordPress from Elegant Themes.
Monarch Plugin Documentation | Elegant Themes Documentation
Updating the twitter logo to the new X from Mr Elon Musk.
You first need to upload a new logo to your WordPress website. You can download them here.
Then you need to add this CSS to your website.
Unfortunately it’s not 100% perfect. But it’s better than the solution I received directly from elegant themes.
li.et_social_twitter:hover i.et_social_icon.et_social_icon_twitter, i.et_social_icon.et_social_icon_twitter {
color: transparent;
background-image: url(/wp-content/uploads/2024/06/twitter-logo-dark.png) !important;
background-size: contain;
background-repeat: no-repeat;
background-position: center;
background-size: 35%;
}
.et_monarch .et_social_twitter,
li.et_social_twitter:hover i.et_social_icon.et_social_icon_twitter,
.et_monarch .et_social_networks.et_social_circle li.et_social_twitter:hover i,
.et_monarch .et_social_networks.et_social_circle .et_social_twitter i{
background-color: #ececec !important;
}
The terms “Software Developer” and “Software Engineer” are often used interchangeably in the tech industry, but there are some distinctions between the two roles based on their scope of work, responsibilities, and focus areas. Here are the key differences:
Scope of Work
-
Software Developer:
- Primarily focuses on writing and maintaining code.
- Involved in the development lifecycle, including designing, coding, testing, and debugging software applications.
- Works on specific applications or functions within an application.
-
Software Engineer:
- Takes a broader, more systematic approach to software development.
- Engages in the full software development lifecycle, from initial concept and design to deployment and maintenance.
- Works on entire systems, infrastructure, and software architecture.
- Often involved in integrating software with hardware and ensuring the overall system meets requirements.
Responsibilities
-
Software Developer:
- Write clean, efficient, and maintainable code.
- Collaborate with other developers and team members to develop software solutions.
- Focus on implementing features and functionalities as specified in requirements.
- May handle some aspects of testing and debugging but typically not as comprehensively as engineers.
-
Software Engineer:
- Design software solutions to solve complex problems, considering scalability, security, and performance.
- Develop and maintain software architecture and infrastructure.
- Ensure that software integrates seamlessly with other systems and components.
- Often involved in project planning, requirement analysis, and risk management.
- Conduct extensive testing and validation to ensure the system’s integrity and reliability.
Focus Areas
-
Software Developer:
- Application development and feature implementation.
- Front-end or back-end development, depending on specialization.
- Writing and maintaining codebases.
-
Software Engineer:
- System design and architecture.
- Full-stack development, often with an emphasis on backend and infrastructure.
- Optimizing systems for performance and scalability.
- Applying engineering principles to software development, including problem-solving, project management, and analytical skills.
Education and Skills
-
Software Developer:
- Often has a background in computer science or related fields.
- Strong programming skills in specific languages (e.g., Python, Java, JavaScript).
- Proficiency in using development tools and frameworks.
- Focus on practical coding skills and application development.
-
Software Engineer:
- Typically has a formal education in software engineering, computer science, or related engineering disciplines.
- Broad knowledge of computer science principles, software engineering methodologies, and system design.
- Skills in various programming languages, software architecture, and engineering practices.
- Emphasis on analytical thinking, problem-solving, and systematic approaches to software development.
Summary
While both roles are crucial in the software development process, software developers are primarily focused on coding and application development, whereas software engineers have a broader scope, dealing with system-level design, architecture, and integrating software with hardware and other systems. The distinction can vary depending on the organization and industry, but these are the general differences between the two roles.
I use this mostly for WordPress & Laravel.
Primarily this is useful for any PHP projects.
Step 1 :
You need to enable vhosts.
Open C:\xampp\apache\conf\httpd.conf
Find the line inside there that looks like this :
# Virtual hosts
# Include conf/extra/httpd-vhosts.conf
And remove the # from the include statement.
# Virtual hosts
include conf/extra/httpd-vhosts.conf
Step 2 :
Enable any php extensions you want to use.
In the xampp control panel. If you select config on the apache line. Select PHP (php.ini)
This is where you enable php extensions you may need.
Same as before. If you want to enable any extensions.
Remove the # at the beginning of the line.
Step 3 :
You need to configure the httpd-vhosts.conf and hosts
Vhosts
Then you need to update https-vhosts.conf with your project directory.
The file can be found at :
C:\xampp\apache\conf\extra\https-vhosts.conf
Inside the hosts file for each project you want to add.
# Virtual Hosts # # Required modules: mod_log_config # If you want to maintain multiple domains/hostnames on your # machine you can setup VirtualHost containers for them. Most configurations # use only name-based virtual hosts so the server doesn't need to worry about # IP addresses. This is indicated by the asterisks in the directives below. # # Please see the documentation at # <URL:http://httpd.apache.org/docs/2.4/vhosts/> # for further details before you try to setup virtual hosts. # # You may use the command line option '-S' to verify your virtual host # configuration. # # Use name-based virtual hosting. # ##NameVirtualHost *:80 # # VirtualHost example: # Almost any Apache directive may go into a VirtualHost container. # The first VirtualHost section is used for all requests that do not # match a ##ServerName or ##ServerAlias in any <VirtualHost> block. # ##<VirtualHost *:80> ##ServerAdmin webmaster@dummy-host.example.com ##DocumentRoot "C:/xampp/htdocs/dummy-host.example.com" ##ServerName dummy-host.example.com ##ServerAlias www.dummy-host.example.com ##ErrorLog "logs/dummy-host.example.com-error.log" ##CustomLog "logs/dummy-host.example.com-access.log" common ##</VirtualHost> <VirtualHost *:80> DocumentRoot "C:/xampp/htdocs/dashboard" ServerName localhost </VirtualHost> #################################### # Sites <VirtualHost *:80> DocumentRoot "C:/xampp/htdocs/digi" ServerName site-name1.localhost </VirtualHost> <VirtualHost *:80> DocumentRoot "C:/xampp/htdocs/coverweb/public" ServerName site-name2.localhost </VirtualHost> <VirtualHost *:80> DocumentRoot "C:/xampp/htdocs/coverweb/public" ServerName site-name3.localhost </VirtualHost>
hosts file
This is located under :
C:\Windows\System32\drivers\etc
hosts
Open the hosts file with administrative privileges.
Use any text editor of your choice.
# Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 192.168.0.1 local.website1.com # Comment here # 192.168.0.1 local.website2.com # Comment here # localhost name resolution is handled within DNS itself. 127.0.0.1 localhost ::1 localhost ########################################### # Sites 127.0.0.1 site-name1.localhost 127.0.0.1 site-name2.localhost 127.0.0.1 site-name3.localhost ########################################### wsl.localhost ########################################### # Added by Docker Desktop 192.168.0.106 host.docker.internal 192.168.0.106 gateway.docker.internal # To allow the same kube context to work on the host and the container: 127.0.0.1 kubernetes.docker.internal # End of section