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.
do you think this is this an elegant solution?
@derks when I was testing the example in Extending CementApp I noticed that if I attempted to access the "api" configurations in the "load" function they weren't there yet, but they were their at "pre_run". This was confusing to me, as the config must have been read to run the "load" function (as that is contingent on "enable_plugin" being true) at that time. Is this an intentional state? please explain.
The
load() function is called durint app.setup() … so, you shouldn’t expect things to be ready to use in load()
Some will work, some won’t… because it depends on the load order
You want to do a
post_setup or pre_run hook
@derks Without looking too hard I wanted to ask you if you've already implemented somewhere (or plan to do so in the future) an dependency injector service for cement. I've located dependency_injector on pypi and it looks like a somewhat reasonable package at first glance, just didn't want to blaze down old roads. Thanks.
@all just a note to let everyone know that I will be retiring this Gitter channel in the near future and will be using Slack instead. Everything I do elsewhere including work, etc is all in Slack and so it really makes sense for me to have everything in one place (and easier to keep up with responses when necessary). Please let me know if you have any questions… you can join here: https://join.slack.com/t/cementframework/shared_invite/enQtMzUzOTIzMDQwNjEwLThkY2FiYWU5ZmQ5ZmEzNGMzMTkyMDgzNTk2MWI0MGU1YWNmNTVmODgxYWNlZjJkZDBmODc0ZjM2MDg5ZmYyOTA
I want to add command line optional -c to set up config path. what should I do
@x007007007 this is difficult because config file parsing happens before command line arguments are
It’s come up before, and I’ve tried to solve it before, but never to completion
That said… since then, there have been new features added like
app.reload() which could be called after if -c was passed. I would start by trying to add a pre_run hook that looks for -c and if passed, do app.config.parse_file() (that file), then app.reload() … but there are plenty of logistical issues that might arrise.
@/all just a reminder that this channel has moved to Slack. Please join if you are interested in staying connected. Once Cement 3 is released this channel will go away completely. https://join.slack.com/t/cementframework/shared_invite/enQtMzU0OTc5MDQ4NDA0LWMwMzZiOTczZjM4ZjFiZDE3MDk4MzA5ZmYxNmZjNTk4NzUwMzcyN2VlMDc5NzIxYjQ1NzlmNzgyNDFjMWJmMWY