Skip to content
This repository was archived by the owner on Nov 28, 2022. It is now read-only.

Commit 538dc9a

Browse files
authored
Add a new section to importing (#372)
* Add a new section Signed-off-by: micgibso <MICGIBSO@uk.ibm.com>
1 parent deed0df commit 538dc9a

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/_documentations/importing-existing-projects.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,12 @@ order: 0
1414

1515
Modifications are usually required to successfully add and deploy projects that have never been run in Codewind before. This tutorial covers the basics of configuring a project to run in Codewind.
1616

17+
## Requirements for importing an existing project not created in Codewind or through Appsody or Odo
18+
19+
Local projects are built and run on Docker. To import your project to a local Codewind instance, it must include a Dockerfile. For more information about Dockerfiles, see [Dockerfile documentation](https://docs.docker.com/engine/reference/builder/).
20+
21+
Remote projects are built and run on Kubernetes. To import your project to a remote Codewind instance, it must include a Dockerfile and a Helm chart. For more information about Dockerfiles, see [Dockerfile documentation](https://docs.docker.com/engine/reference/builder/) and for more information about Helm charts, see [Helm chart documentation](https://helm.sh/docs/topics/charts/).
22+
1723
## What kind of projects can I add?
1824

1925
Codewind is designed to develop cloud native microservices. Therefore, each project must be self-sufficient, so not reliant on other projects to build. The requirements to add projects for each of the supported application types are outlined in the following sections:

0 commit comments

Comments
 (0)