Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](https://github.com/nodeca/js-yaml/compare/4.1.0...4.1.1) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 4.1.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dokploy
Developer-friendly & type-safe Typescript SDK specifically catered to leverage dokploy API.
Important
This SDK is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this section before > publishing to a package manager.
Summary
Dokploy API: Endpoints for dokploy
More information about the API can be found at http://app.dokploy.com/api/settings.getOpenApiDocument
Table of Contents
SDK Installation
Tip
To finish publishing your SDK to npm and others you must run your first generation action.
The SDK can be installed with either npm, pnpm, bun or yarn package managers.
NPM
npm add https://github.com/LukeHagar/Dokploy-ts-sdk
PNPM
pnpm add https://github.com/LukeHagar/Dokploy-ts-sdk
Bun
bun add https://github.com/LukeHagar/Dokploy-ts-sdk
Yarn
yarn add https://github.com/LukeHagar/Dokploy-ts-sdk
Note
This package is published with CommonJS and ES Modules (ESM) support.
Requirements
For supported JavaScript runtimes, please consult RUNTIMES.md.
SDK Example Usage
Example
import { Dokploy } from "dokploy";
const dokploy = new Dokploy({
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
const result = await dokploy.admin.getOne();
console.log(result);
}
run();
Authentication
Per-Client Security Schemes
This SDK supports the following security scheme globally:
| Name | Type | Scheme | Environment Variable |
|---|---|---|---|
authorization |
http | HTTP Bearer | DOKPLOY_AUTHORIZATION |
To authenticate with the API the authorization parameter must be set when initializing the SDK client instance. For example:
import { Dokploy } from "dokploy";
const dokploy = new Dokploy({
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
const result = await dokploy.admin.getOne();
console.log(result);
}
run();
Available Resources and Operations
Available methods
admin
application
- create
- getOne
- reload
- delete
- stop
- start
- redeploy
- saveEnvironment
- saveBuildType
- saveGithubProvider
- saveGitlabProvider
- saveBitbucketProvider
- saveDockerProvider
- saveGitProdiver
- markRunning
- update
- refreshToken
- deploy
- cleanQueues
- readTraefikConfig
- updateTraefikConfig
- readAppMonitoring
auth
- createAdmin
- createUser
- login
- getOne
- logout
- update
- generateToken
- get
- generate2FASecret
- verify2faSetup
- verifyLogin2FA
- disable2FA
- sendResetPasswordEmail
- resetPassword
- confirmEmail
backup
- create
- get
- update
- remove
- manualBackupPostgres
- manualBackupMysql
- manualBackupMariadb
- manualBackupMongo
bitbucket
certificates
cluster
compose
- create
- getOne
- update
- delete
- cleanQueues
- fetchSourceType
- randomizeCompose
- getConverted
- deploy
- redeploy
- stop
- getDefaultCommand
- refreshToken
- deployTemplate
- getTemplates
- getTags
deployment
destination
docker
domain
github
gitlab
gitProvider
mariadb
mongo
mounts
mysql
notification
- createSlack
- updateSlack
- testSlackConnection
- createTelegram
- updateTelegram
- testTelegramConnection
- createDiscord
- updateDiscord
- testDiscordConnection
- createEmail
- updateEmail
- testEmailConnection
- remove
- getAll
notifications
port
postgres
project
redirects
redis
registry
security
server
servers
settings
- reloadServer
- reloadTraefik
- toggleDashboard
- cleanUnusedImages
- cleanUnusedVolumes
- cleanStoppedContainers
- cleanDockerBuilder
- cleanDockerPrune
- cleanAll
- cleanMonitoring
- saveSshPrivateKey
- assignDomainServer
- cleanSshPrivateKey
- updateDockerCleanup
- readTraefikConfig
- updateTraefikConfig
- readWebServerTraefikConfig
- updateWebServerTraefikConfig
- readMiddlewareTraefikConfig
- updateMiddlewareTraefikConfig
- checkAndUpdateImage
- updateServer
- getDokployVersion
- readDirectories
- updateTraefikFile
- readTraefikFile
- getIp
- getOpenApiDocument
- readTraefikEnv
- writeTraefikEnv
- haveTraefikDashboardPortEnabled
- readStats
- getLogRotateStatus
- toggleLogRotate
- haveActivateRequests
- toggleRequests
- isCloud
- health
sshKey
sshKeys
stripe
user
Standalone functions
All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.
To read more about standalone functions, check FUNCTIONS.md.
Available standalone functions
adminAssignPermissionsadminCreateUserInvitationadminGetOneadminGetUserByTokenadminRemoveUserapplicationCleanQueuesapplicationCreateapplicationDeleteapplicationDeployapplicationGetOneapplicationMarkRunningapplicationReadAppMonitoringapplicationReadTraefikConfigapplicationRedeployapplicationRefreshTokenapplicationReloadapplicationSaveBitbucketProviderapplicationSaveBuildTypeapplicationSaveDockerProviderapplicationSaveEnvironmentapplicationSaveGithubProviderapplicationSaveGitlabProviderapplicationSaveGitProdiverapplicationStartapplicationStopapplicationUpdateapplicationUpdateTraefikConfigauthConfirmEmailauthCreateAdminauthCreateUserauthDisable2FAauthGenerate2FASecretauthGenerateTokenauthGetauthGetOneauthLoginauthLogoutauthResetPasswordauthSendResetPasswordEmailauthUpdateauthVerify2faSetupauthVerifyLogin2FAbackupCreatebackupGetbackupManualBackupMariadbbackupManualBackupMongobackupManualBackupMysqlbackupManualBackupPostgresbackupRemovebackupUpdatebitbucketCreatebitbucketGetbitbucketGetBranchesbitbucketGetRepositoriesbitbucketProvidersbitbucketTestConnectionbitbucketUpdatecertificatesAllcertificatesCreatecertificatesGetcertificatesRemoveclusterAddManagerclusterAddWorkerclusterGetNodesclusterRemoveWorkercomposeCleanQueuescomposeCreatecomposeDeletecomposeDeploycomposeDeployTemplatecomposeFetchSourceTypecomposeGetConvertedcomposeGetDefaultCommandcomposeGetOnecomposeGetTagscomposeGetTemplatescomposeRandomizeComposecomposeRedeploycomposeRefreshTokencomposeStopcomposeUpdatedeploymentAllByComposedeploymentAllByServerdeploymentGetdestinationCreatedestinationGetdestinationGetOnedestinationRemovedestinationTestConnectiondestinationUpdatedockerGetConfigdockerGetContainersdockerGetContainersByAppLabeldockerGetContainersByAppNameMatchdockerRestartContainerdomainByApplicationIddomainByComposeIddomainCreatedomainDeletedomainGenerateDomaindomainGetdomainUpdategithubGetBranchesgithubGetProvidersgithubGetRepositoriesgithubOnegithubTestConnectiongithubUpdategitlabCreategitlabGetGitlabBranchesgitlabGetGitlabRepositoriesgitlabOnegitlabProvidersgitlabTestConnectiongitlabUpdategitProviderGetAllgitProviderRemovemariadbChangeStatusmariadbCreatemariadbDeploymariadbGetmariadbReloadmariadbRemovemariadbSaveEnvironmentmariadbSaveExternalPortmariadbStartmariadbStopmariadbUpdatemongoChangeStatusmongoCreatemongoDeploymongoGetmongoReloadmongoRemovemongoSaveEnvironmentmongoSaveExternalPortmongoStartmongoStopmongoUpdatemountsCreatemountsGetmountsRemovemountsUpdatemysqlChangeStatusmysqlCreatemysqlDeploymysqlGetmysqlReloadmysqlRemovemysqlSaveEnvironmentmysqlSaveExternalPortmysqlStartmysqlStopmysqlUpdatenotificationCreateDiscordnotificationCreateEmailnotificationCreateSlacknotificationCreateTelegramnotificationGetAllnotificationRemovenotificationsGetnotificationTestDiscordConnectionnotificationTestEmailConnectionnotificationTestSlackConnectionnotificationTestTelegramConnectionnotificationUpdateDiscordnotificationUpdateEmailnotificationUpdateSlacknotificationUpdateTelegramportCreateportDeleteportGetportUpdatepostgresChangeStatuspostgresCreatepostgresDeploypostgresGetpostgresReloadpostgresRemovepostgresSaveEnvironmentpostgresSaveExternalPortpostgresStartpostgresStoppostgresUpdateprojectAllprojectCreateprojectGetprojectRemoveprojectUpdateredirectsCreateredirectsDeleteredirectsGetOneredirectsUpdateredisChangeStatusredisCreateredisDeployredisGetredisReloadredisRemoveredisSaveEnvironmentredisSaveExternalPortredisStartredisStopredisUpdateregistryCreateregistryGetregistryGetAllregistryRemoveregistryTestRegistryregistryUpdatesecurityCreatesecurityDeletesecurityGetsecurityUpdateserverAllserverCreateserverRemoveserverSetupserversGetserverUpdateserverWithSSHKeysettingsAssignDomainServersettingsCheckAndUpdateImagesettingsCleanAllsettingsCleanDockerBuildersettingsCleanDockerPrunesettingsCleanMonitoringsettingsCleanSshPrivateKeysettingsCleanStoppedContainerssettingsCleanUnusedImagessettingsCleanUnusedVolumessettingsGetDokployVersionsettingsGetIpsettingsGetLogRotateStatussettingsGetOpenApiDocumentsettingsHaveActivateRequestssettingsHaveTraefikDashboardPortEnabledsettingsHealthsettingsIsCloudsettingsReadDirectoriessettingsReadMiddlewareTraefikConfigsettingsReadStatssettingsReadTraefikConfigsettingsReadTraefikEnvsettingsReadTraefikFilesettingsReadWebServerTraefikConfigsettingsReloadServersettingsReloadTraefiksettingsSaveSshPrivateKeysettingsToggleDashboardsettingsToggleLogRotatesettingsToggleRequestssettingsUpdateDockerCleanupsettingsUpdateMiddlewareTraefikConfigsettingsUpdateServersettingsUpdateTraefikConfigsettingsUpdateTraefikFilesettingsUpdateWebServerTraefikConfigsettingsWriteTraefikEnvsshKeyGeneratesshKeyGetsshKeyRemovesshKeysAllsshKeysCreatesshKeyUpdatestripeCanCreateMoreServersstripeCreateCheckoutSessionstripeCreateCustomerPortalSessionstripeGetProductsuserByAuthIduserByUserIduserGetAll
Retries
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:
import { Dokploy } from "dokploy";
const dokploy = new Dokploy({
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
const result = await dokploy.admin.getOne({
retries: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
});
console.log(result);
}
run();
If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:
import { Dokploy } from "dokploy";
const dokploy = new Dokploy({
retryConfig: {
strategy: "backoff",
backoff: {
initialInterval: 1,
maxInterval: 50,
exponent: 1.1,
maxElapsedTime: 100,
},
retryConnectionErrors: false,
},
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
const result = await dokploy.admin.getOne();
console.log(result);
}
run();
Error Handling
DokployError is the base class for all HTTP error responses. It has the following properties:
| Property | Type | Description |
|---|---|---|
error.message |
string |
Error message |
error.statusCode |
number |
HTTP response status code eg 404 |
error.headers |
Headers |
HTTP response headers |
error.body |
string |
HTTP body. Can be empty string if no body is returned. |
error.rawResponse |
Response |
Raw HTTP response |
Example
import { Dokploy } from "dokploy";
import * as errors from "dokploy/models/errors";
const dokploy = new Dokploy({
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
try {
const result = await dokploy.admin.getOne();
console.log(result);
} catch (error) {
if (error instanceof errors.DokployError) {
console.log(error.message);
console.log(error.statusCode);
console.log(error.body);
console.log(error.headers);
}
}
}
run();
Error Classes
Primary error:
DokployError: The base class for HTTP error responses.
Less common errors (6)
Network errors:
ConnectionError: HTTP client was unable to make a request to a server.RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.RequestAbortedError: HTTP request was aborted by the client.InvalidRequestError: Any input used to create a request is invalid.UnexpectedClientError: Unrecognised or unexpected error.
Inherit from DokployError:
ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. Seeerror.rawValuefor the raw value anderror.pretty()for a nicely formatted multi-line string.
Server Selection
Override Server URL Per-Client
The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:
import { Dokploy } from "dokploy";
const dokploy = new Dokploy({
serverURL: "http://your-dokploy-instance.com/api",
authorization: process.env["DOKPLOY_AUTHORIZATION"] ?? "",
});
async function run() {
const result = await dokploy.admin.getOne();
console.log(result);
}
run();
Custom HTTP Client
The TypeScript SDK makes API calls using an HTTPClient that wraps the native
Fetch API. This
client is a thin wrapper around fetch and provides the ability to attach hooks
around the request lifecycle that can be used to modify the request or handle
errors and response.
The HTTPClient constructor takes an optional fetcher argument that can be
used to integrate a third-party HTTP client or when writing tests to mock out
the HTTP client and feed in fixtures.
The following example shows how to use the "beforeRequest" hook to to add a
custom header and a timeout to requests and how to use the "requestError" hook
to log errors:
import { Dokploy } from "dokploy";
import { HTTPClient } from "dokploy/lib/http";
const httpClient = new HTTPClient({
// fetcher takes a function that has the same signature as native `fetch`.
fetcher: (request) => {
return fetch(request);
}
});
httpClient.addHook("beforeRequest", (request) => {
const nextRequest = new Request(request, {
signal: request.signal || AbortSignal.timeout(5000)
});
nextRequest.headers.set("x-custom-header", "custom value");
return nextRequest;
});
httpClient.addHook("requestError", (error, request) => {
console.group("Request Error");
console.log("Reason:", `${error}`);
console.log("Endpoint:", `${request.method} ${request.url}`);
console.groupEnd();
});
const sdk = new Dokploy({ httpClient: httpClient });
Debugging
You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass a logger that matches console's interface as an SDK option.
Warning
Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.
import { Dokploy } from "dokploy";
const sdk = new Dokploy({ debugLogger: console });
You can also enable a default debug logger by setting an environment variable DOKPLOY_DEBUG to true.
Development
Maturity
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
Contributions
While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.