Andras/BoundlessFlowCampus2K

Fork 0

Research and implement deployment script #701

New issue

Open

opened 2026-05-04 11:02:35 +00:00 by b24johka · 5 comments

b24johka commented

2026-05-04 11:02:35 +00:00

Collaborator

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

b24johka was assigned by a24julot

2026-05-04 11:18:20 +00:00

a24julot added the

Team 1

research

labels

2026-05-04 11:23:17 +00:00

b24johka commented

2026-05-04 12:07:08 +00:00

Author

Collaborator

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

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

b24johka commented

2026-05-04 12:41:47 +00:00

Author

Collaborator

Forgejo actions

Deployment on main pushes is possible with forgejo.
SSH keys can be securely managed through https://forgejo.org/docs/next/user/actions/basic-concepts/#secrets
Requires that we enable Forgejo runner (Might be an issue of its own)

## Forgejo actions ## - Deployment on main pushes is possible with forgejo. - SSH keys can be securely managed through https://forgejo.org/docs/next/user/actions/basic-concepts/#secrets - Requires that we enable Forgejo runner (Might be an issue of its own)

b24johka commented

2026-05-08 08:35:43 +00:00

Author

Collaborator

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:

Forgejo actions is not relevant right now, because handling of SSH-key is sensitive.
Clean up of previous docker containers are minimal. (Expected to bloat the server over time)
Firewall of server has not been enhanced.
No automated continuous deployment
No monitoring tools of server (Downtime notifications, prometheus and grafana)

## 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: - Forgejo actions is not relevant right now, because handling of SSH-key is sensitive. - Clean up of previous docker containers are minimal. (Expected to bloat the server over time) - Firewall of server has not been enhanced. - No automated continuous deployment - No monitoring tools of server (Downtime notifications, prometheus and grafana)

b24johka referenced this issue

2026-05-08 08:40:06 +00:00

Enhance logging of deployment script #838

b24johka added the

needs review

label

2026-05-11 09:48:31 +00:00

a24julot commented

2026-05-21 09:05:57 +00:00

Collaborator

Requesting review from @f21marfo

f21marfo commented

2026-05-21 10:26:31 +00:00

Collaborator

Review on #701

Whats done

Read through comments.
Read through links.

What needs to be done

The question asked with this issue, so to speak, was to establish a standard for deploying the application to server, but what is the conclusion? Are we using a deployment script of any kind, or not? This needs clarification.
Needs a summary/final report/conclusion.

Conclusion

I found this research notes a bit difficult to follow, especially towards the end. For instance, a point that "wont be fixed" was "no automated continuous deployment", which sounds a bit ambigous. What does that mean in this context? No automated deployment at all? As noted, there needs to be a clear and concise summary of the findings.

# Review on #701 ## Whats done + Read through comments. + Read through links. ## What needs to be done + The question asked with this issue, so to speak, was to establish a standard for deploying the application to server, but what is the conclusion? Are we using a deployment script of any kind, or not? This needs clarification. + Needs a summary/final report/conclusion. ## Conclusion + I found this research notes a bit difficult to follow, especially towards the end. For instance, a point that "wont be fixed" was "no automated continuous deployment", which sounds a bit ambigous. What does that mean in this context? No automated deployment at all? As noted, there needs to be a clear and concise summary of the findings.