Run alone: a standalone application attempt by Gabriel Sor
1 like454 views
The document discusses the challenges and methodologies involved in creating and deploying a minimal Pharo image for standalone applications, including issues related to memory consumption, packaging, and code loading. It covers the 'minimal image approach,' which emphasizes starting with a clean image and only including necessary components, as well as practical steps for preparing the image for deployment across different platforms. Additionally, it highlights tools and scripts needed for successful deployment, along with error handling and future work considerations.
![SmalltalkZen
“There are two schools of
thought, as far as
preparing a Smalltalk
image for deployment[...]”
Dmitri Zagidulin
12](https://image.slidesharecdn.com/sorrunalone-171122040128/85/Run-alone-a-standalone-application-attempt-by-Gabriel-Sor-12-320.jpg)
![Metacello
baseline: spec
<baseline>
spec
for: #common
do: [ self setUpDependencies: spec.
Specpackage: 'Seaside-Examples' with:
[ spec requires: #('Grease-Core' 'JQuery-Core' ‘Javascript-Core’
‘Seaside-Core’ ‘Seaside-Canvas’ ‘Seaside-Componente’
‘Seaside-Tools’ ‘Seaside-Development’) ]]
25](https://image.slidesharecdn.com/sorrunalone-171122040128/85/Run-alone-a-standalone-application-attempt-by-Gabriel-Sor-25-320.jpg)
Run alone: a standalone application attempt by Gabriel Sor
- 1. Gabriel Sor
- 2. Run Alone: A Pharo standalone application attempt
- 3. Deployment Issues ▪ Memory Consumption ▪ Packaging 3
- 5. Amount of Classes Amount of Packages Tools for load Code Size Full Image 6400 488 Metacello 52MB Fuel Config CommandLineHan dler Monticello Clean Image
- 6. How many files are necessary for deploy? 6
- 10. Option 4 10
- 11. How To Prepare a Deployment Image on Pharo 11
- 12. SmalltalkZen “There are two schools of thought, as far as preparing a Smalltalk image for deployment[...]” Dmitri Zagidulin 12
- 13. “ “Take your development image, and strip out unnecessary applications, GUIs, and the development environment itself” Dmitri Zagidulin
- 14. Deploy anywhere approach Deploy Anywhere Packaging a customer ready application for Windows, Mac and Linux. Maximiliano Tabacman In Smalltalks 2015, UBA, Argentina.
- 15. Deploy anywhere result ▪ A image and a Directory structure ready to deploy
- 16. Amount of Classes Amount of Packages Tools for load Code Size Seaside Image 7364 543 Metacello 85.1MB Fuel Config CommandLineHa ndler Monticello Image with Seaside with tests and everything
- 17. “ “Start with a minimal clean image, and only load the libraries and classes that you’re actually using to run your application.” Dmitri Zagidulin 17
- 18. The minimal image approach Create a deployable image loading the application on the minimal image and disabling the command line handlers.
- 19. The minimal image approach Create a deployable image loading the application on the minimal image and disabling the command line handlers.
- 20. Stateless Image The application closed to modification 20
- 21. What is the Minimal Image? “Kernel image (Shrinked/bootstraped) +Monticello +Network Support (Zinc, Sockets) +Remore repository support +Metacello +CommandLineHandlers (except FuelCommandLineHandler)” Mission Pharo Kernel 1. 1. Mission Pharo Kernel ESUG 2016, Prague Pavel Krivanek and Christophe Demarey 21
- 22. Tools necessaries for this approach ▪ Dependency Analyser ▪ Minimal Image ▪ Metacello ▪ ConfigurationOf or BaselineOf is needed ▪ ConfigurationCommandLineHandler ▪ Smalltalk scripts
- 23. ““Is slightly more difficult but very rewarding, especially if you’re going to go the Continuous Integration route (via Hudson/Jenkins), because it requires you to know exactly which packages you’re using, what they depend on, the load order, and so on.” Dmitri Zagidulin
- 25. Metacello baseline: spec <baseline> spec for: #common do: [ self setUpDependencies: spec. Specpackage: 'Seaside-Examples' with: [ spec requires: #('Grease-Core' 'JQuery-Core' ‘Javascript-Core’ ‘Seaside-Core’ ‘Seaside-Canvas’ ‘Seaside-Componente’ ‘Seaside-Tools’ ‘Seaside-Development’) ]] 25
- 26. The minimal image process ▪ Create an entry point object ▪ Create a BaselineOf or ConfigurationOf (Using the Dependency Analyser) ▪ Disable code loading ▪ Remove the changes file ▪ Remove the sources file
- 27. Create an entry point object MyApplication MyApplic ationEntr yPoint Starts Click on
- 28. Registering Entry Point Object MyApplicationEntryPoint class>>#initialize SessionManager default register: (ClassSessionHandler forClassNamed: self name) inCategory: SessionManager default userCategory 28
- 29. StartUp and ShutDown MyApplicationEntryPoint class>>startUp: arg1 MyApplicationManager instance startAlgorithm MyApplicationEntryPoint class>>shutDown: arg1 MyApplicationManager instance stopAlgorithm 29
- 30. Get the minimal image
- 31. Just the minimal image Amount of Classes Amount of Packages Tools for load Code Size Minimal Image 1429 119 Metacello 8,3MB Monticello Config CommandLineHan dler
- 32. In linux doesn’t work curl get.pharo.org/64/ | bash curl get.pharo.org/61-minimal ./pharo Pharo-minimal.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit... 32
- 33. Uses the 32 VM Minimal Image doesn’t work with 64 bits VM 33
- 34. In linux this works curl get.pharo.org/vm61 | bash curl get.pharo.org/61-minimal | bash ./pharo Pharo-minimal.image eval “its works” 34
- 35. Order your ideas Create a development directory Create a exe-factory directory Create the deploy directory Save the minimal image Save the 32 bits VM Proof that all works 35
- 39. veggie:~$./pharo Pharo-minimal.image config repositoryOfMyApplication BaselineOfMyApplication --install=baseline Just works with SmalltalkHub Load application :linux
- 40. C: PharoConsole.exe Pharo-minimal.image config repositoryOfMyApplication BaselineOfMyApplication --install=someVersion Never works Load application: Windows
- 41. C: PharoConsole.exe Pharo-minimal.image loadMyApplication.st Load application: Windows
- 42. loadMyApplication.st Metacello new baseline: 'MyApplication'; filetreeDirectory:'pathToMyApplication'; load. SmalltalkImage current saveImageInFileNamed:'myApp.image'. SmalltalkImage current snapshot: true andQuit: true 42
- 43. Error MCFileTreeRepository uses STON STON is not in the minimal image. 43
- 44. So, load STON before Gofer new smalltalkhubUser: 'SvenVanCaekenberghe' project: 'STON'; configurationOf: 'Ston'; loadStable. loadMyApplication code 44
- 46. The solution? scriptToLoadSTON cleanAfterNB.st scritpToLoadMyApp pharo-project/pharo-minimal-scripts Thanks Pavel Krivanek!!! 46
- 49. But…. MessageNotUnderstood: receiver of "addTo:" is nil 49
- 50. Nor github nor filetree You just can load code from: ▪ Metacello directory ▪ SmalltalkHub repository 50
- 51. Possible solution Load MCGitHubRepository and its dependencies: ▪ Metacello-GitHub ▪ Metacello-GitBasedRepository ▪ MonticelloFileTree-Core 51
- 52. Good luck!!! 52
- 53. veggie:~$./pharo Pharo-minimal.image disableSourceFileAndChanges.st Disable calls to sources and changes files
- 54. didisableSourceFileAndChanges.st ChangesLog subclass:'NoChangesLog '. PharoFilesOpener subclass:'NoPharoFilesOpener'. NoChangesLog install. NoPharoFilesOpener install. Smalltalk snapshot:true andQuit:true. Sven Van Caekenberghe :http://forum.world.st
- 56. The minimal image spected result ▪ An immutable image. ▪ Low memory consumption. ▪ Non UI ▪ Just one click execution (in windows)
- 57. The minimal image actual result ▪ An immutable image. ▪ Low memory consumption. ▪ Non UI ▪ Just one click execution (in windows)
- 58. With Seaside with tests and everything Amount of Classes Amount of Packages Tools for load Code Size Minimal Seaside +STON 2156 175 Metacello 28.4MB Monticello Config CommandLineHan dler
- 59. Run Alone: A Pharo standalone application Ex e m Con es In h p ://gi b.co /de t e d a
- 60. Future Work Try to Build a deployable image Ready to load the necessary packages using github,gitlab,filetree and then unload all unnecessary objects
- 61. 61