appwrite / appwrite/integration-for-digitalocean

๐Ÿ› Bug Report: 1.6 one click starts server without appwrite directory and without docker initialized

Open
#38 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
20
Forks
4
PR merge metrics
No merged PRs in 30d

Description

### ๐Ÿ‘Ÿ Reproduction steps

Spin up droplet with appwrite from marketplace.
ls in home dir - no appwrite

### ๐Ÿ‘ Expected behavior

appwrite dir should be in home directory, appwrite docker images should be up and running.

### ๐Ÿ‘Ž Actual Behavior

no appwrite directory inside home dir inside droplet, no appwrite images running

### ๐ŸŽฒ Appwrite version

Version 1.6.x

### ๐Ÿ’ป Operating system

MacOS

### ๐Ÿงฑ Your Environment

_No response_

### ๐Ÿ‘€ Have you spent some time to check if this issue has been raised before?

- [x] I checked and didn't find similar issue

### ๐Ÿข Have you read the Code of Conduct?

- [x] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the DigitalOcean Marketplace 1-click setup for Appwrite 1.6.x and inspect the shell provisioning entry points responsible for creating the home-directory appwrite checkout and starting Docker. Done means a fresh droplet contains the appwrite directory and its Appwrite Docker images are running.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.