Research and implement deployment script #701
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#701
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
We need to have some sort of standard to deploy the application to the server, this is often done with a deployment script which clones the repository and installs the application
https://dev.to/primocrypt/building-an-automated-docker-deployment-script-a-complete-beginners-guide-2b0f
Research from this source has been done.
What seems necessary?
Clean up of the previous docker containers each deployment seems like a good idea, a lot of unnecessary storage would otherwise be used.
Updating of the server system each deployment to ensure that it is running on viable versions.
Deployment script that automates the installation script to not make manual mistakes.
Questions for management/leaders
Integrate to work with Actions (This will make the deployment automatic whenever Main is being updated)
Configure reverse proxy to enable HTTPS
Forgejo actions
After discussion with the customer its been brought to attention that the issues regarding the web server should be minimized.
Points that wont be fixed:
Requesting review from @f21marfo
Review on #701
Whats done
What needs to be done
Conclusion
Summary of research and decisions
The deployment script has been implemented for both Unix and Windows, removes containers aswell as updating the server each time we run it. Since the server is remote, the output of the script is saved in a directory called logs. See more here
https://git.webug.se/Andras/BoundlessFlowCampus2K/wiki/Server-Deployment.-
(The windows instructions will be created soon)
What this means is there will not be an automated execution of our scripts on changes in the repository. This is because it would need Forgejo Actions with the SSH-key, prefferrebly with the use of https://forgejo.org/docs/next/user/actions/basic-concepts/#secrets. However, the customer is very careful about the usage of the SSH-key and prefers that we run the script manually.
At the time of research for this issue it was decided to not have any monitoring, this was until #959 suggested we should have a grip over the webpage availability,
the issue on monitoring can be found here #1085
Conclusion
These are the final most important points regarding this issue, i hope it will satisfy the reviewer.
Much clearer, excellent summary!
Great job, I will close this research issue!