You can definitely do a plugin. What I would try is, the plugin would import and subclass
yourapp.whatever.controllers.LiteController … and then int he plugin’s load() function you would app.handler.register(AdvancedController, force=True) which forces it to register overtop of the LiteController (of the same label)
(I’m now starting to roadmap the migration to Python 3 and Cement 3)
Simplifying usage
I promise not to hold you to it
I’ve made a few of the major changes already… I’m actually focussig mainly on revamping the site and documentation
I’m hoping for later this year
I’m rewriting SphinxDoc to Markdown… it’s mostly just tedious work right now… then I will button up the major design changes I wanted to roll out
Hi everyone,
I hope this is the right place to ask.
I've started working on a project that is using the Cement framework and I would like to ask a few things.
We are using a plugin that takes a number of config options.
Those options get set in the expected place in:
The question is, what is the most elegant way to retrieve the config options inside a plugin?
I know it is possible to do something like:
Didn't have much luck when reading the docs, so I would appreciate if someone could point me to the right place.
Thanks,
Paul
I hope this is the right place to ask.
I've started working on a project that is using the Cement framework and I would like to ask a few things.
We are using a plugin that takes a number of config options.
Those options get set in the expected place in:
/etc/<project_name>/<project_name>.confThe question is, what is the most elegant way to retrieve the config options inside a plugin?
I know it is possible to do something like:
self.app.config.get('section', 'option') in the _setup function of the plugin but is there a way retrieve that information without invoking app?Didn't have much luck when reading the docs, so I would appreciate if someone could point me to the right place.
Thanks,
Paul
if it is simply because it is annoying to call
self.app.config.get (understandable) you could create a shortcut like using get_section_dict
like
self.config = self.app.config.get_section_dict(‘my_plugin’) … then just use self.config[‘my_key’] through out your plugin
@p3j4p5 ^
actually,
app is passed to the _setup() method … because that is called when the plugin is instantiated during app.setup(). You should set self.app = app in _setup() .. or if you subclass from cement.core.handler.CementHandler just make sure you super() in _setup() and it does that
afte
app.setup() you can access self.app anywhere in the plugin class
Hi! Just getting to grips with the framework although have hit a stumbling block. Using cement 2.10.2 and following the BOSS app creation documentation. Created an app although when I run it it doesnt seem to load the example.py plugin module. Have not modified the BOSS app in anyway. Any thoughts? Can post debug output if that is any use?
Checked for tickets relating to this on both cement and BOSS issue trackers but cannot see anything obvious
Thanks in advance
and I assume you used
boss to create a cement-app and also cement-plugin? You need to configure plugin_config_dir and plugin_dir in a configuration file in order to find plugins..
@derks thabks for getting back to me. I ended up symlinking myapp/config/app.conf created by the boss cement-app to the location you suggested and the same for plugins.d conf directory. All is working well and I can start developing the app now. I mistakenly assumed after running setup.py develop that it would pick up the configs. Thanks for the help!
@derks can you please help me how to create app which we can share to clients without giving source code
you can destribute just Python bytecode (
.pyc, and .pyo) but that is easily reverse-engineerable and or doesn’t completely hide your code if I recall correctly
This is interesting: https://github.com/Falldog/pyconcrete
No connection between “concrete” and “cement” mind you. ;)
though:
pyconcrete is an experimental project, there is always a way to decrypt .pye files, but pyconcrete just make it harder.
One question… are you trying to hide specific code that isn’t necessarily required by the “public” user… like an admin/internal code? If so, I’d suggest putting everything you don’t want to share in a plugin… and just don’t destribute the plugin. That way, the end-user can use the public bits freely, and the internal/admin code is will work just the same after installing/enabling the plugin
Aren't these files supposed to be default values for the project and project plugins respectively?
so you’d need to copy it to
~/.yourapp.conf or /etc/yourapp/yourapp.conf, etc… then modifying the config should take affect
@derks: I just added
app.config.parse_file('%s/config/facetracker.conf' % os.path.dirname(os.path.dirname(os.path.dirname(os.path.realpath(__file__))))) before app.run() and it worked... I'd like default values in the project that can be superseded by the values in system and user configurations.