-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integrate gsApplicationTools and GsDevKit/zinc #2
Comments
Taking approach where instead of subclassing GemServerStarter, subclass GemServer ... then we can do direct customization of the various bits and pieces that need customization on run ... and pass any interesting state via the script call ... script location etc. can be specified by the subclass ... Added tests for validating the basic api
Going towards a GemServer-centric desing ... it seems that if we allow customization of the GemServer subclass on a per server basis, we can really shrink down the size of the script needed to launch the gem ... port and Gem name are all that are needed to distinguish a particular executable ... perhaps gem-status can be shared somehow as well ... lots of food for thought ... anyway I will make a pass at the GemServer-centric approach and see if things can be adapted for maintenance vm, fastCGI seaside, zinc seaside, zinc webserver and service vms ... |
…tartSeaside30_Adaptor ... push a bunch of stuff around ...
…ic to send startGems, restartGems and stopGems directory to the GemServer instance ... return GemServer instance when created, so that inline start and stop logic can be done without requiring lookup...
|
…Server class>>register:for:on: as the center piece
…he level of feedback ... need status command that looks at pid and verifies that pid is there and perhaps some other status information...
… 3.x packages ... add new packages and update baseline
…s GemServer class, so that subclasses in different projects can still find the script
I thin those changes are great! Thank you Dale. I'll try to merge my changes into it later on. Let's keep this as the new master.
pull out pieces that should be part of zinc project and create zinc http-server and web-socket-server support scripts for zinc ... next part of Zinc Issue 58
The text was updated successfully, but these errors were encountered: