Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摎 Documentation: Support manual deployment #8181

Closed
2 tasks done
jack9603301 opened this issue May 22, 2024 · 3 comments
Closed
2 tasks done

馃摎 Documentation: Support manual deployment #8181

jack9603301 opened this issue May 22, 2024 · 3 comments
Assignees
Labels
product / self-hosted Issues only found when self-hosting Appwrite question Further information is requested stale

Comments

@jack9603301
Copy link

馃挱 Description

Yesterday, I officially started to provide appwrite deployment services to customers. At the beginning, I chose 1-minute deployment (using docker) because it was the fastest and I was busy at the time. Later, the customer asked how to do database backup of this thing, whether it was convenient and safe. Then I thought about the following, I am still used to lxd (I have been providing lxd-based deployment for customers before, and the customer and I think it is easy to use), and the maintenance of lxd , The backup migration program is quite easy, and can easily perform data backup and migration of stateful containers. I reviewed Docker and docker-compose.yaml and thought it would work, so I decided to start this new deployment today. Just after I did everything, I found that port 80 could not return data. I didn't know what I did wrong. I saw a line of instructions from Docker - copy app/console/build to console. I think I made a mistake. Make corrections. This deployment took relatively longer than expected. I worked for the customer for a full 4 hours, although it was still within the normal range. I think it's worth sinking this experience now and maybe we can improve the documentation to guide others on how to deploy them manually?

馃憖 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

馃彚 Have you read the Code of Conduct?

@stnguyen90
Copy link
Contributor

@jack9603301, thanks for raising this issue! 馃檹馃徏 We document a more manual approach here. What else were you looking for?

@stnguyen90 stnguyen90 self-assigned this May 29, 2024
@stnguyen90 stnguyen90 added question Further information is requested product / self-hosted Issues only found when self-hosting Appwrite labels May 29, 2024
Copy link

github-actions bot commented Jun 6, 2024

This issue has been labeled as a 'question', indicating that it requires additional information from the requestor. It has been inactive for 7 days. If no further activity occurs, this issue will be closed in 14 days.

@github-actions github-actions bot added the stale label Jun 6, 2024
Copy link

This issue has been closed due to inactivity. If you still require assistance, please provide the requested information.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product / self-hosted Issues only found when self-hosting Appwrite question Further information is requested stale
Projects
None yet
Development

No branches or pull requests

2 participants