Difference between revisions of "Cloning an instance"
Jump to navigation
Jump to search
(Created page with "== Connecting to the server == First you must access the commandline on the system in question. This is done using a certificate and the Putty program. # Get a certificate private key from an existing admin user # Install Putty on your machine (alternative WinSCP) # Set up the profile in Putty ## Set hostaname = IP / domain name ## Set Category > Connection > SSH > Auth > Credentials > Private key file authentication ## Set Category > Connection > RLogin > Local usernam...") |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
# Install Putty on your machine (alternative WinSCP) | # Install Putty on your machine (alternative WinSCP) | ||
# Set up the profile in Putty | # Set up the profile in Putty | ||
## Set hostaname = IP | ## Set hostaname = {server IP or domain name} | ||
## Set Category > Connection > SSH > Auth > Credentials > Private key file authentication | ## Set Category > Connection > Data > Auto login username = ec2-user | ||
# | ## Set Category > Connection > SSH > Auth > Credentials > Private key file authentication = {private file location} | ||
# Session > Save | |||
Test you can connect to the server | Test you can connect to the server. | ||
Note: Connection will fail if you try connecting from an IP that is not whitelisted by the TS server team | |||
== Cloning the system == | == Cloning the system == | ||
Copy an instance | |||
# Run: ts clone-app | |||
# Define source name | |||
# Define name of new instance | |||
Validate after 2 mins that the instance is running | |||
== Option: Change configurations == | |||
Some server settings are more appropriate for demo/test systems. | |||
Consider setting | |||
# Backend > Modules > Configuration | |||
#* smtpTestMode = false | |||
#* serviceAutostart = false | |||
Latest revision as of 12:27, 7 November 2024
Connecting to the server
First you must access the commandline on the system in question. This is done using a certificate and the Putty program.
- Get a certificate private key from an existing admin user
- Install Putty on your machine (alternative WinSCP)
- Set up the profile in Putty
- Set hostaname = {server IP or domain name}
- Set Category > Connection > Data > Auto login username = ec2-user
- Set Category > Connection > SSH > Auth > Credentials > Private key file authentication = {private file location}
- Session > Save
Test you can connect to the server.
Note: Connection will fail if you try connecting from an IP that is not whitelisted by the TS server team
Cloning the system
Copy an instance
- Run: ts clone-app
- Define source name
- Define name of new instance
Validate after 2 mins that the instance is running
Option: Change configurations
Some server settings are more appropriate for demo/test systems.
Consider setting
- Backend > Modules > Configuration
- smtpTestMode = false
- serviceAutostart = false