generated from camel.apache.org/component
Update wiki Home page for digitalocean
parent
db42e7755f
commit
8a346a4d5a
45
Home.md
45
Home.md
@ -1,21 +1,38 @@
|
|||||||
# Deploy the Project on CamelX Platform
|
# DigitalOcean
|
||||||
|
|
||||||
Deploy on CamelX Platform in three steps
|
Manage Droplets and resources within the DigitalOcean cloud.
|
||||||
|
|
||||||
## Step 1: Create a release
|
## Metadata
|
||||||
From the project space, click on **"Create a release"**
|
|
||||||
|
|
||||||
The new version is automatically available in the list
|
| Property | Value |
|
||||||
|
|----------|-------|
|
||||||
|
| Scheme | `digitalocean` |
|
||||||
|
| Support Level | Stable |
|
||||||
|
| Labels | cloud,management |
|
||||||
|
| Version | 4.10.2 |
|
||||||
|
|
||||||
## Step 2: Deploy
|
## Maven Dependency
|
||||||
Click on **"Deploy"**
|
|
||||||
|
|
||||||
- **Version:** Select the desired release
|
```xml
|
||||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
<dependency>
|
||||||
- **Configuration:** Select the configuration source
|
<groupId>org.apache.camel</groupId>
|
||||||
- **Resources:** Set CPU and Memory
|
<artifactId>camel-digitalocean</artifactId>
|
||||||
|
<version>4.10.2</version>
|
||||||
|
</dependency>
|
||||||
|
```
|
||||||
|
|
||||||
## Step 3: Expose
|
## Endpoint Properties
|
||||||
Enable **"Expose"**
|
|
||||||
|
|
||||||
Choose an **API Gateway** (Internal, Public, etc.)
|
| Name | Type | Required | Default | Description |
|
||||||
|
|------|------|----------|---------|-------------|
|
||||||
|
| `operation` | object | | | The operation to perform to the given resource. |
|
||||||
|
| `page` | integer | | `1` | Use for pagination. Force the page number. |
|
||||||
|
| `perPage` | integer | | `25` | Use for pagination. Set the number of item per request. The maximum number of results per page is 200. |
|
||||||
|
| `resource` | object | ✓ | | The DigitalOcean resource type on which perform the operation. |
|
||||||
|
| `lazyStartProducer` | boolean | | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
|
||||||
|
| `digitalOceanClient` | object | | | To use a existing configured DigitalOceanClient as client |
|
||||||
|
| `httpProxyHost` | string | | | Set a proxy host if needed |
|
||||||
|
| `httpProxyPassword` | string | | | Set a proxy password if needed |
|
||||||
|
| `httpProxyPort` | integer | | | Set a proxy port if needed |
|
||||||
|
| `httpProxyUser` | string | | | Set a proxy host if needed |
|
||||||
|
| `oAuthToken` | string | | | DigitalOcean OAuth Token |
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user