https://github.com/lizheming/drone-deta

Deploying to Deta with Drone CI
https://github.com/lizheming/drone-deta

cd ci deployment drone drone-ci drone-plugin

Last synced: about 2 months ago
JSON representation

Deploying to Deta with Drone CI

• Host: GitHub
• URL: https://github.com/lizheming/drone-deta
• Owner: lizheming
• License: mit
• Created: 2021-11-07T12:29:23.000Z (about 3 years ago)
• Default Branch: master
• Last Pushed: 2024-02-17T02:40:58.000Z (11 months ago)
• Last Synced: 2024-10-12T19:26:56.670Z (3 months ago)
• Topics: cd, ci, deployment, drone, drone-ci, drone-plugin
• Language: Shell
• Homepage:
• Size: 20.5 KB
• Stars: 2
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# drone-deta

[![BuildStatus](https://cloud.drone.io/api/badges/lizheming/drone-deta/status.svg)](https://cloud.drone.io/lizheming/drone-deta)

[![Docker Pulls](https://img.shields.io/docker/pulls/lizheming/drone-deta.svg)]()



Deploying to [Deta](https://deta.space) with Drone CI

## Environment

- `SPACE_ACCESS_TOKEN`: Deta access token. [How to get Deta access token?](https://deta.space/docs/en/basics/cli#authentication)

- `SPACE_ID`: project id of an existing project

- `SPACE_TAG`: tag to identify this push

- `SPACE_DIR`: src of project to push (default "./")

- `SPACE_LISTED`: listed on discovery

- `SPACE_NOTES`: release notes

- `SPACE_RID`: revision id for release

- `SPACE_VERSIION`: version for the release

- `SPACE_RELEASE`: set `false` if you just want push and don't want release action

## Usage

```

docker run --rm \

  -e SPACE_ACCESS_TOKEN=access_token \

  -e SPACE_ID=id \

  lizheming/drone-deta

```

## Drone configuration examples

```yml

steps:

- name: deta

  image: lizheming/drone-deta

  settings:

    access_token:

      from_secret: space_access_token

    id: test-id

```