Sandbox Environment

Your sandbox is the place where you will clone your themes and edit the code. Each Remote Workstation has a backoffice + the sandbox for the themes.

Connecting with SSH

To connect to your sandbox with the terminal, you will find the command line in the backoffice, when checking the configuration of your workstation in the section "SSH"

Here is an example connecting to a workstation with the alias "my-alias"

When connecting, you will see have access to the folder integration, where you will be able to git clone your themes

$ ssh user@my-alias.tc.exo7d.us -p 2222 -A
 _____               _           
| ____|_  _____   __| |_   _ ___ 
|  _| \ \/ / _ \ / _` | | | / __|
| |___ >  < (_) | (_| | |_| \__ \
|_____/_/\_\___/ \__,_|\__,_|___/

This is an Exodus Sandbox development environment for Galaxy.

$ [user@my-alias:~] $ ls
integration  integration-shared  integration-versions

$ [user@my-alias:~] $ cd integration
$ [user@my-alias:~/integration] $ git clone XXXXXXXXX

Because you connected with the option -A, which enables ForwardAgent, your local SSH key is forwarded and your Gitlab / Bitbucket will be able to recognize you

Enabling SSH Agent Forwarding issues

In case this does not work, some first steps to debug could be to follow Github article about SSH Agent Forwarding https://docs.github.com/en/developers/overview/using-ssh-agent-forwarding#your-local-ssh-agent-must-be-running

They have a section 2 things to check:

  • "Your local ssh-agent must be running"

  • "Your key must be available to ssh-agent"

As you will often work on your remote workstation, remembering the command line/copy pasting it each time could be difficult. You can create a bash alias, but we advise you to use an SSH Config File 💡

Editing code

To edit code, please refer to the guidelines from your IDE to work remotely. At xo7, most of us use Visual Studio Code official extension.

VSC Remote - SSH extension

Git configuration

By default, your sandbox has no custom git configuration (no user set, no alias)

The first thing to do is to set your user name and email

$ git config --global user.name "John Doe"
$ git config --global user.email johndoe@example.com

Feel free to add your other usual configurations, such as aliases, etc.

NVM - Node Version Manager

Last updated