Other

When I use vscode remote explorer to connect to remote servers to read long configuration files. or investigate/search for configuration in a system, software, or solution that has no information about. I face files navigation limitations due to the limited user which I use it to connect to the server is limited. This article explains how to elevate vscode and allow it to connect to remote host as root with sudo

This will allow vscode to work on the remote host as root.

Remote host sudo user.

The user you connect to should have sudo without password in my example username is ansible

Connect to the remote host then create a file in /etc/sudoers.d/ or update the main file using visudo

• Add to /etc/sudoers.d/admin

ansible ALL=(ALL:ALL) NOPASSWD:ALL 

• Then change permission to 0440

chmod 0440 /etc/sudores/admin

• Verify sudo setting by typeing

visudo -c

vscode-Server directory structure

now when you connect to the remote host with vscode for the first time, It creates a hidden directory inside the user’s home directory named vscode-server where it installs vscode-server binaries and configuration inside it.

Next, it creates a sub-directory with unique ID related to your vscode editor inside the vscode-server direcotry. Then, It starts an instance of vscode-server and terminate it when you disconnect

This unique identifier is related to the client you connect from. For example, I connect from two workstations, therefore I have two directories.

Configure vscode with sudo

After you connect to the server

find which client ID you are using by typing ps command

navigate into ~/.vscode-server/bin

List the content to detect latest updated directory

Edit the server.sh which is located inside clientID directory

Add sudo in the begining of the last line

Conclusion, Now when you connect using vscode to the remote host, you will find you self connected with sudo privliges and vscode Terminal will show as root user with full priviliges.

Implementing a reverse proxy servers usually for many reasons. For example, enable load-balancing, high availability, improved performance, and enhanced security. So, This article explains the what is it, how it works. Then, explain the advantage and disadvantages of having it in your architecture.

What is it ? how it works ?

Basically, a Reverse proxy works as an Interface or bridge between the Internet and your web-based services. in other words, instead of exposing many servers to internet, you will exposing one server.

Famous Reverse proxies.

notably, there are many reveres proxy in the marker. nevertheless, It falls back to your environment needs which type you will need.

• HAPROXY.
  A pioneer proxy server known for its efficiency as load balancer for TCP and HTTP-based applications. It has afree version. nevertheless, the paid one (Enterprise version) provides many features like high availablity, Layer 7 load-balancing, Security feautres.
• Nginx.
  A known as high-performance web server. furthermore, It provides reverse proxy feature, caching and, load balancing.
• Microsoft IIS .
  IIS is usually known as webserver. nevertheless, it can work as reverse proxy after enabling some addons. to demonstrate, These serios of articles shows how to setup configure IIS as reverse proxy

Why use Reverse Proxy ( Advantages )?

indeed, Having Reverse proxy in your architecture is highly recommended. as it gives you the opportunity to

• Monitor, analayis, and control web Traffic to your servers.
• Apply security features.
• Provide Load balancing.
• SSL offloading.
• Protect your servers from internet (Only proxy need to be exposed to internet).
• Enable Caching and reduce load on your webservers.
• Reduce Administrative tasks related to websites rules and subdomains.
• consolidate their internet presence as all servers exposed to internet through single IP or servers.
• Allow you consolidate or Customize error pages for whole services.

Reverse Proxy disadvantages

indeed, The use of a Reverse proxy adds an additional layer of complexity to your network architecture. . The following are the disadvantages or the obstacles you might face while having it in your architecture.

• Enabling security cloud block your applications.
• Apps compatibilty with proxy.
• SSL offloading Apps compatibilty .
• Web-Application auditing related issues like client IPs.
• Developers hard coding.
• Redundent headers in Proxy and Backend Server.
• All eggs in one basket (Single point of failure).

Conclution

altogether, having a reverse proxy in your environment will positively impact your environment. After all, the pros outweigh the cons.