-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Comments
@jack9603301, thanks for raising this issue! 馃檹馃徏 We document a more manual approach here. What else were you looking for? |
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. |
This issue has been closed due to inactivity. If you still require assistance, please provide the requested information. |
馃挱 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?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: