autoreload

New in version 1.1.0.

Automatically reload processes when components are updated.

Reloads modules and configuration files.

Configuration parameters

smisk.autoreload

Enable automatic reloading of modules and configuration files upon modification.

Acts as the default value for the smisk.autoreload.modules and smisk.autoreload.config parameters.

In this case, where only smisk.autoreload is set and defined as True, both modules and configuration files will be monitored for changes:

"smisk.autoreload": true

In this case, both modules and configuration files will be monitored for changes, because smisk.autoreload.modules will inherith the value true:

"smisk.autoreload": true,
"smisk.autoreload.config": true

In this case, only configuration files will be monitored since smisk.autoreload.modules will inherit the value false from smisk.autoreload (it’s not explicitly defined and therefore falls back to its default value, which smisk.autoreload.modules inherit):

"smisk.autoreload.config": true
Default:False
Type:bool
smisk.autoreload.modules

Enable automatic reloading of modules upon modification.

If True when calling smisk.util.main.Main.run(), a new Autoreloader is created and activated.

Default:False
Type:bool
smisk.autoreload.config

Enable automatic reloading of configuration files upon modification.

If True when calling smisk.util.main.Main.run(), a new Autoreloader is created and activated.

Default:False
Type:bool

Classes

class smisk.autoreload.Autoreloader(smisk.util.threads.Monitor)

In the context of FastCGI applications, this should mean that the application is reloaded. Future versions might change this behaviour and add “real” reloading of modules.

Subclass of smisk.util.threads.Monitor

__init__(frequency=1, match=None)
run()
Reload the process if registered files have been modified.
setup()
start()
Start our own perpetual timer thread for self.run.