Stirling-Tools
Optimize Docker image build
Description of Changes
The system-intensive installation steps take place before the application files are copied. This means that they remain cached - even if the application source code changes - and packages do not have to be downloaded again with every docker-compose up.
Checklist
General
- [x] I have read the Contribution Guidelines
- [x] I have read the Stirling-PDF Developer Guide (if applicable)
- [x] I have read the How to add new languages to Stirling-PDF (if applicable)
- [x] I have performed a self-review of my own code
- [x] My changes generate no new warnings
Documentation
- [ ] I have updated relevant docs on Stirling-PDF's doc repo (if functionality has heavily changed)
- [ ] I have read the section Add New Translation Tags (for new translation tags only)
UI Changes (if applicable)
- [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR)
Testing (if applicable)
- [ ] I have tested my changes locally. Refer to the Testing Guide for more details.
🚀 PR Test Deployment
Your PR has been deployed for testing!
🔗 Test URL: http://185.252.234.121:2913
This deployment will be automatically cleaned up when the PR is closed.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Seems like this PR increases docker size slightly? maybe caused by additional run commands?
Seems like this PR increases docker size slightly? maybe caused by additional run commands?
I think this is expected as things are cached. But it can shrink down diskusage I have some experience from the wg-easy project.
🚀 PR Test Deployment
Your PR has been deployed for testing!
🔗 Test URL: http://185.252.234.121:2913
This deployment will be automatically cleaned up when the PR is closed.