What Is code-server?

code-server is an open-source project developed by Coder that allows you to run VS Code on a remote server and access it through a web browser. This setup provides a consistent development environment that can be accessed from any device, be it a laptop, tablet, or even a smartphone. By leveraging the power of cloud servers, code-server enables faster tests, compilations, and downloads, all while preserving your local device’s resources.

Key Features of code-server

• VS Code in the Browser: Experience the full functionality of VS Code, including IntelliSense, debugging, and Git integration, all within your browser.
• Remote Development: Develop on powerful cloud servers, reducing the load on your local machine and enabling resource-intensive tasks.
• Consistent Environment: Maintain a uniform development setup across different devices, ensuring consistency and reducing the “it works on my machine” problem.
• Extension Support: Install and use most VS Code extensions, enhancing your development workflow.
• Secure Access: Access your development environment securely from anywhere, with options for HTTPS and authentication.

Installation Guide

Setting up code-server is straightforward. The easiest way to install code-server is to use the official install script, which automates most of the process. This script attempts to use the system package manager if possible.

For Linux, macOS, and FreeBSD:

Run the following command in your terminal:

curl -fsSL https://code-server.dev/install.sh | sh

After installation, you can start code-server by running:

code-server

By default, code-server will be accessible at http://127.0.0.1:8080, and your password will be stored in ~/.config/code-server/config.yaml.

For Docker Users:

You can also run code-server in a Docker container:

docker run -it --name code-server -p 127.0.0.1:8080:8080 \
  -v "$HOME/.local:/home/coder/.local" \
  -v "$HOME/.config:/home/coder/.config" \
  -v "$PWD:/home/coder/project" \
  -u "$(id -u):$(id -g)" \
  -e "DOCKER_USER=$USER" \
  codercom/code-server:latest

This command mounts your current directory into the container and forwards your UID/GID so that all file system operations occur as your user outside the container.

Securing Your code-server Instance

To expose code-server securely to the internet, consider the following methods:

• Port Forwarding via SSH: If you have an SSH server on your remote machine, you can forward local ports to access code-server securely.
• Using Let’s Encrypt with Caddy or NGINX: For a more robust solution, you can set up HTTPS using Let’s Encrypt with web servers like Caddy or NGINX.
• Self-Signed Certificates: For internal use or testing, you can generate and use self-signed certificates to enable HTTPS.

These methods ensure that your code-server instance is accessible securely from anywhere.

Keeping code-server Up-to-Date

To ensure you have the latest features and security patches, it’s important to keep code-server updated. You can check for the latest releases on the GitHub Releases Page. To update, simply run the install script again:

curl -fsSL https://code-server.dev/install.sh | sh

This will download and install the latest version of code-server.

Final Thoughts

code-server empowers developers by providing a powerful, browser-based development environment that can be accessed from anywhere. Whether you’re working from a laptop, tablet, or smartphone, code-server ensures that you have a consistent and secure development setup at your fingertips.

By leveraging cloud servers, code-server enables faster development cycles and reduces the load on local machines, making it an ideal solution for modern development workflows.

The post code-server: Unlocking the Power of VS Code in Your Browser appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Mounting your Google Drive on Linux allows you to access your cloud storage as if it were a local directory. This guide will walk you through the complete process of setting up and mounting Google Drive using rclone, a powerful command-line tool for cloud storage management.

Prerequisites

Before starting, ensure you have:

• A Linux system with root or sudo access
• An active Google account with Google Drive
• Internet connection for authentication and file access
• Basic familiarity with the command line

Step 1: Install rclone

Ubuntu/Debian

sudo apt update
sudo apt install rclone

CentOS/RHEL/Fedora

# For CentOS/RHEL
sudo yum install rclone

# For Fedora
sudo dnf install rclone

Arch Linux

sudo pacman -S rclone

Install from Official Script

curl https://rclone.org/install.sh | sudo bash

Verify the installation:

rclone version

Step 2: Install FUSE

To mount filesystems, rclone requires FUSE (Filesystem in Userspace):

Ubuntu/Debian

sudo apt install fuse

CentOS/RHEL/Fedora

# For CentOS/RHEL
sudo yum install fuse

# For Fedora
sudo dnf install fuse

Arch Linux

sudo pacman -S fuse2

Step 3: Configure Google Drive Remote

Start the rclone configuration process:

rclone config

Follow these steps in the interactive setup:

1. Create a new remote: n) New remote
2. Name your remote: name> gdrive (You can use any name you prefer)
3. Select Google Drive: Storage> drive
4. Leave client ID and secret blank (unless you have your own): client_id> [Press Enter] client_secret> [Press Enter]
5. Choose scope (recommended: option 1 for full access): scope> 1 This gives full access to all files except the Application Data Folder.
6. Service Account file (leave blank for personal use): service_account_file> [Press Enter]
7. Enable web browser authentication: y) Yes
8. Browser authentication:
   • rclone will open your default browser
   • Log in to your Google account
   • Grant permissions to rclone
   • Copy the verification code back to the terminal
9. Shared Drive configuration: n) No (Unless you want to access a specific Shared Drive)
10. Confirm configuration: y) Yes this is OK

Read https://rclone.org/drive/#making-your-own-client-id

Step 4: Test the Configuration

Verify that rclone can access your Google Drive:

# List directories in your Google Drive
rclone lsd gdrive:

# List all files
rclone ls gdrive:

# List files with details
rclone lsl gdrive:

Step 5: Create Mount Point

Create a directory where you want to mount Google Drive:

mkdir ~/GoogleDrive

Step 6: Mount Google Drive

Basic Mount Command

rclone mount gdrive: ~/GoogleDrive --daemon

Recommended Mount Command with Options

rclone mount gdrive: ~/GoogleDrive \
  --vfs-cache-mode writes \
  --vfs-cache-max-age 100h \
  --vfs-cache-max-size 10G \
  --vfs-read-chunk-size 32M \
  --vfs-read-chunk-size-limit off \
  --buffer-size 32M \
  --daemon

Mount Options Explained

• --vfs-cache-mode writes: Cache file writes to improve performance
• --vfs-cache-max-age 100h: Keep cached files for 100 hours
• --vfs-cache-max-size 10G: Limit cache size to 10GB
• --vfs-read-chunk-size 32M: Read files in 32MB chunks
• --buffer-size 32M: Set buffer size for better performance
• --daemon: Run in background

Alternative: Mount with GUI Support

If you’re using a desktop environment and want the mount to appear in file managers:

rclone mount gdrive: ~/GoogleDrive \
  --vfs-cache-mode writes \
  --allow-other \
  --daemon

Step 7: Verify the Mount

Check if the mount is successful:

# List mounted filesystems
df -h | grep GoogleDrive

# Check if files are accessible
ls -la ~/GoogleDrive

Step 8: Unmount Google Drive

To unmount the drive:

# Method 1: Using fusermount
fusermount -u ~/GoogleDrive

# Method 2: Using umount
sudo umount ~/GoogleDrive

# Method 3: Kill rclone process
killall rclone

Step 9: Auto-Mount on Boot (Optional)

Using systemd Service

Create a systemd service file:

sudo nano /etc/systemd/system/rclone-gdrive.service

Add the following content (replace username with your actual username):

[Unit]
Description=rclone: Remote FUSE filesystem for Google Drive
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
User=username
Group=username
ExecStart=/usr/bin/rclone mount gdrive: /home/username/GoogleDrive \
  --config=/home/username/.config/rclone/rclone.conf \
  --vfs-cache-mode writes \
  --vfs-cache-max-age 100h \
  --vfs-cache-max-size 10G \
  --vfs-read-chunk-size 32M \
  --buffer-size 32M \
  --allow-other
ExecStop=/bin/fusermount -u /home/username/GoogleDrive
Restart=always
RestartSec=10

[Install]
WantedBy=default.target

Enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable rclone-gdrive.service
sudo systemctl start rclone-gdrive.service

Check service status:

sudo systemctl status rclone-gdrive.service

Using /etc/fstab

Add the following line to /etc/fstab:

sudo nano /etc/fstab

Add this line (replace username with your actual username):

gdrive: /home/username/GoogleDrive rclone rw,noauto,nofail,_netdev,user,exec,allow_other 0 0

Performance Tips

Optimize for Your Use Case

For frequent small file access:

rclone mount gdrive: ~/GoogleDrive \
  --vfs-cache-mode full \
  --vfs-cache-max-size 10G \
  --vfs-read-ahead 256M \
  --daemon

For streaming large files:

rclone mount gdrive: ~/GoogleDrive \
  --vfs-cache-mode off \
  --vfs-read-chunk-size 128M \
  --vfs-read-chunk-size-limit 2G \
  --buffer-size 64M \
  --daemon

Troubleshooting

Common Issues and Solutions

Issue: Permission denied

# Add your user to the fuse group
sudo usermod -a -G fuse $USER
# Log out and log back in

Issue: Mount point is busy

# Force unmount
sudo umount -l ~/GoogleDrive

Issue: Slow performance

# Increase cache settings
rclone mount gdrive: ~/GoogleDrive \
  --vfs-cache-mode full \
  --vfs-cache-max-size 20G \
  --daemon

Issue: Files not showing immediately

# Add directory cache timeout
rclone mount gdrive: ~/GoogleDrive \
  --dir-cache-time 1000h \
  --daemon

Check rclone Logs

# View logs
rclone mount gdrive: ~/GoogleDrive --log-level INFO --log-file ~/rclone.log

# Or run in foreground for debugging
rclone mount gdrive: ~/GoogleDrive -v

Security Considerations

1. Token Security: Your authentication tokens are stored in ~/.config/rclone/rclone.conf. Protect this file with appropriate permissions: chmod 600 ~/.config/rclone/rclone.conf
2. Network Security: All communication with Google Drive is encrypted via HTTPS.
3. Local Access: Use --allow-other carefully as it allows other users to access the mount.

Conclusion

You now have Google Drive mounted on your Linux system! The mounted directory behaves like any other local directory, allowing you to:

• Copy files to and from Google Drive using standard commands
• Edit files directly in your preferred applications
• Access Google Drive through your file manager
• Use command-line tools on your cloud files

Remember that changes to files are synchronized with Google Drive, so always ensure you have a stable internet connection when working with important files.

For advanced usage and additional options, refer to the official rclone documentation.

The post How to Mount Google Drive using rclone on Linux appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.