Skip to content
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

To check: Additional Control Script debug, console and run Commands #117

Closed
svx opened this issue Sep 5, 2014 · 1 comment
Closed

To check: Additional Control Script debug, console and run Commands #117

svx opened this issue Sep 5, 2014 · 1 comment

Comments

@svx
Copy link
Member

svx commented Sep 5, 2014

cheap copy and paste from:
https://github.com/plone/plone.recipe.zope2instance/pull/14/files#diff-88b99bb28683bd5b7e3a204826ead112R508

thanks @do3cc for his tweet about it :)

we should check if we already have that in the docs !


+Additional Control Script debug, console and run Commands
+---------------------------------------------------------------

The extended Zope 2 control script installed by this recipe, usually
bin\instance by convention, offers a debug command and another
@@ -505,6 +505,15 @@ with following options::
Note that these options must come before the script name,
e.g. bin/instance -RLOPlone/front-page debug

+The console command is similar to the fg command, but it does not
+create a subprocess to start up Zope 2. This is useful for two
+use cases. First, the supervisor program, to supervise long running
+processes like a Zope, require the process not to fork away, so that
+supervisor can control it.
+Second, IDEs like WingIDE and PyCharm support debugging running
+processes from within. For this to work, the process should also
+not fork away.
+
Additional control script commands


@stevepiercy
Copy link
Contributor

We're up to Zope 5. Closing as won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants