Connecting Eclipse to remote Codewind
Complete the prerequisites.
Objectives
In this topic you will:
- Connect Codewind on Eclipse to the remote instance of Codewind in the cloud.
- Add an image registry.
- Create a new project.
- Copy an existing project to your remote connection.
1. Connect your IDE’s Codewind extension to your remote instance of Codewind.
1. Locate the Codewind Explorer view in Eclipse and click the cloud icon to start the new connection wizard:
2. Add a connection name, the connection URL of your deployment, username, and password:
If you do not know these values, ask your system administrator or see Deploying Codewind remotely.
The IDE validates the connection and adds it to the Codewind panel:
The IDE and Codewind are connected.
2. Add an image registry.
Before Codewind style projects can be deployed on Kubernetes, specify an image push registry. For more information about registries, see Codewind container registry guidance. This example uses Docker Hub:
1. Right-click your remote connection in the Codewind Explorer view and select Manage Image Registries
:
2. Locate and click Add… to create a new registry:
3. Complete the container registry connection details:
- Add your container registry username.
- Add your container registry password.
- Click the checkbox to designate this registry as a push registry.
- Enter your container registry namespace, which is usually the same as your username.
The connection is tested to validate your credentials, which are then stored in a Kubernetes secret within the Codewind service.
3. Create a new project.
1. In the Codewind Explorer view, right-click your remote connection and select Create New Project…:
2. Select the template type and name your project. Your new project is built and after a few seconds begins running in the cloud.
4. Copy an existing local project to the cloud.
The following procedure copies an existing local project myFirstNodeProject
to the remote Codewind deployment:
1. Right-click your remote connection in the Codewind Explorer view and select Add Existing Project…:
2. Go to the folder that contains your local project files, or choose the previously created myFirstNodeProject
from the workspace. Click Next:
3. Codewind prompts you to confirm that the project type is identified as Node.js:
4. Click Finish.
The project files are copied over to the Codewind server, and the new myFirstNodeProject
appears under your remote connection. Codewind builds your application code and Docker image, and moments later, the project image is uploaded to Docker Hub and used by your cloud deployment to provision a new pod:
The myFirstNodeProject
project on the CloudName1
cluster is now running and ready.
Next Steps
You have now finished configuring Codewind to be used remotely.
In the next topic, you will learn how to use Codewind remotely to build and run projects in your cloud.