[Infrastructure] Deployment - Nginx, Systemd, Subdomain #12
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
Create deployment documentation and templates for deploying the application to a production server with Nginx, systemd, and subdomain configuration.
Approach
Instead of directly configuring the server, this issue creates version-controlled deployment documentation and reusable templates that can be reviewed and applied when ready.
Deliverables
/deployment/DEPLOYMENT.mdComprehensive documentation covering:
/deployment/scripts/foldernginx-template.conf- Nginx site configuration templatesystemd-template.service- Systemd service templatedeploy.sh- Optional automated deployment scriptDependencies
Status
This issue creates documentation and templates that can be prepared independently but finalized when dependencies are resolved.
for this issue, I'd like you to create a documentation, let's say DEPLOYMENT.md and put everything there. if there is any script or template script, put them as well. maybe a folder /deployment at root level and then we will have DEPLOYMENT.md and folder scripts for any scripts needed during deployment
@han Thanks for the guidance! I agree this approach makes more sense.
Proposed changes to the issue:
Instead of directly configuring the server via SSH, I will create:
/deployment/DEPLOYMENT.md- Full documentation covering:/deployment/scripts/folder with:nginx-template.conf- Nginx site configuration templatesystemd-template.service- Systemd service templatedeploy.sh- Optional automated deployment scriptThis approach is better because:
Does this sound good to you? Should I proceed with this approach?
this is sounds good to me, can you update the issue description as well? also does it need another issue to complete first? or this issue can be finished independently?
@han Good questions!
Updating issue description: Yes, I will update the issue description to reflect the new approach (creating deployment docs/scripts instead of direct server setup).
Dependencies: Looking at the current status:
This issue cannot be fully completed independently because it depends on:
However, I can prepare all the documentation and templates now based on what we know about the project structure. The templates can be created and refined, then applied when the backend/frontend are ready.
Should I proceed with creating the documentation and templates as much as possible? I can make the deployment docs comprehensive enough that they just need minor adjustments when the dependencies are resolved.