Shared
Settings
Manage server configuration and control server lifecycle
Overview
Update server settings, manage SSH keys, and control server lifecycle for your shared hosting servers. Configure basic server information and manage access tokens for automated deployments.Server Configuration
Editable Fields
Name
Human-readable server identifier (must be unique)
Port
SSH port for server connection (usually 21002)
Server IP
Public IP address of your hosting server
Server Username
Hosting account username for SSH access
Branch
Active deployment branch for your repository
Directory Configuration
Files Directory
Files Directory
Purpose: Where your application files are storedDefault: Repository name (e.g., “myapp”)Location:
/home/username/myapp/Public Directory
Public Directory
Purpose: Publicly accessible web directoryDefault:
public_html or domain folderLocation: /home/username/public_html/Update Process
1
Modify settings
Change name, port, IP, username, directories, and/or branch as needed
2
Save changes
Click “Save” to apply configuration updates
3
Verification
Changes are immediately reflected across the dashboard
Name Validation: Must be unique across your account, cannot be empty
Changing the branch affects future deployments. Ensure the new branch exists in your repository.
SSH Key Management
Loupp SSH Key
Key Information
Key Information
Purpose: SSH key added to your server during setupAccess: View and copy the public keySecurity: Keep this key secure
Key Recovery
Key Recovery
Use Case: If key is accidentally deleted from serverSolution: Copy from Loupp and add back to hosting accountProcess: Add to cPanel SSH Access section
SSH Key Setup
1
Access cPanel
Log into your hosting control panel
2
SSH Access
Navigate to “SSH Access” section
3
Add Key
Copy the Loupp SSH key and paste it in the public key field
4
Authorize
Make sure to authorize the key after addition
Provider Note: Most shared hosting providers use cPanel. Contact your provider if you need help with SSH setup.
Personal Access Token (PAT)
GitLab Integration
Token Purpose
Token Purpose
Use: Same token for all shared hosting server deploymentsSecurity: Update at least twice monthly for securityScope: Repository access and deployment automation
Token Management
Token Management
Update Process: Enter new token and click “Save”Scope: Automatically updates for all your shared serversFormat: Starts with “glpat-” for GitLab
Token Security
Security Warning: Personal access tokens provide access to your repositories. Keep them secure and rotate regularly.
Best Practices
Best Practices
- Update tokens every 2-4 weeks
- Use strong, unique tokens
- Limit token scope to necessary permissions
- Monitor token usage
Token Scope
Token Scope
- Repository read access
- Webhook management
- Deployment automation
Server Lifecycle Management
Server Destruction
Destructive Action: Server destruction is irreversible. All data will be permanently lost.
Destruction Process
1
Access section
Scroll to “Delete Shared Hosting” section at bottom
2
Review consequences
All site data will be permanently lost, SSL certificates preserved
3
Confirm action
Click “Delete” and confirm in the dialog
4
Monitor process
Server status changes to “Deleting” and removal begins
What Gets Removed
Services & Workers
Services & Workers
Stops all services, removes queue workers, deletes scheduled tasks
Files & Configs
Files & Configs
Removes site directory, Nginx configs, environment files
System Integration
System Integration
Restarts web services, updates server configurations
SSL certificates are preserved and can be reused for new sites on the same domain.