For this example we are going to launch a Cloud9 Development container for the Taisun project:
Port 8010 will be used on the Taisun host for accessing the Cloud9 interface
Port 3010 on the host will forward to port 80 inside the container.
We will expose the Host level Linux docker socket to the container so the application can use Docker.
Once running you can click on the Launch button in Taisun to access Cloud9:
You will be greeted with a screen to set your username. This is needed to leverage the collaboration features of Cloud9, multiple people can hop into this endpoint and work together on the same project with shared terminals and editor windows.
Once Cloud9 loads up because this is a NodeJS project our first order of business will be to install packages via NPM in the terminal:
We can then start the application using nodemon to monitor file changes:
You can now open a new tab and access:(for this example port 3010)
Since we also exposed the Docker socket to this container we can also run docker commands to build and deploy from our current directory IE:
docker build -t mytestapp .
This just barely scratches the surface on using these containers to develop your application. It is important to note that these containers will stay in the state you leave them as long as your server stays online.
For example you can start working on a project from home , close your tab and make a run to the local coffee shop. Using the remote access gateway Remote Access hop right back in and continue where you left off.
Given you are in a full Linux Desktop or for Cloud9 have root level CLI access to a contained development environment you can:
Install or remove system level applications
Build docker containers and push to DockerHub or another registry
Commit and push to your Github repository while having a live testing environment