Skip to content
This repository has been archived by the owner on Mar 9, 2020. It is now read-only.

Home

Jump to bottom
Joshua Worden edited this page Nov 13, 2015 · 19 revisions

You must have a provisioned development environment for this exercise. A URL with the setup form should have been emailed to you. If you haven't received this, please contact [email protected].

In this exercise, you will be connecting to a server with a provisioned development environment. This guide will walk through how to connect to this server to make changes, view the changes in your browser, and provide instructions for configuring your FTP client if needed.

If you would prefer to set up and use your own development environment, you can see the project requirements and installation steps.

Your environment

<GHUser> should be replaced in any commands or URIs with your Github username.

Hostname: <GHUser>.test-sandbox.baseplatform.io
Username: <GHUser>
Password: <GHUser>

Connecting

You will need to connect to your environment using SSH. If you are Windows and do not have an SSH client, download Putty.

Connect via SSH

Open your Terminal and execute the following command to connect to your instance. When prompted, your password is the same as your username.

ssh <GHUser>@test-sandbox.baseplatform.io

You now have a connection open to your environment -- you will use this later when committing your changes.

Making changes

Your working directory for this project is located in the htdocs folder.

If you are comfortable using server-side tools such as vim or nano, you can use them to modify files in your workspace via SSH.

If you prefer a local text editor or IDE, you can use these configuration instructions to configure an FTP client to access your files. Your FTP client must be capable of SFTP (FTP over SSH), or use the recommended clients.

Previewing changes

You can view your instance of the application by visiting the Hostname above in your browser.

Committing changes

To commit a change, use the command-line git application.

  • To see what files are changed, execute git status.
  • To see what is changed, execute git diff[ filename].
  • To add a file to be committed, execute git add <filename>.
  • To commit your changes, execute git commit -m '<message>'.

Asset management

To keep assetic updated with your most recent changes

  • In ~/htdocs execute the following app/console assetic:watch

To keep ember updated with your most recent changes

  • In ~/htdocs/src/AppBundle/Resources/todo execute the following ember build --watch
Clone this wiki locally