$ akara start
Apr 14 11:40:44 akara[8993]: [CRITICAL] Could not read from Akara
configuration file '/home/lm/.config/akara.conf': File contains no
section headers.
file: /home/lm/.config/akara.conf, line: 29
'class Akara:\n'
Cannot start Akara. Exiting.
Regards,
-- luismiguel
--
You received this message because you are subscribed to the Google Groups "Akara Developers" group.
To post to this group, send email to akar...@googlegroups.com.
To unsubscribe from this group, send email to akara-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akara-dev?hl=en.
I've just discovered new akara setup command ;-)
-- luismiguel
2011/4/14 Uche Ogbuji <uc...@ogbuji.net>:
class Akara:
Listen = 8880
ConfigRoot = "/home/lm/src/iaaa/src/"
PidFile = "logs/akara.pid"
ModuleDir = "modules"
[...]
I use the akara -f new_config.conf start command. Logs go ok, but
akara doesn't find the modules I'm saving at new modules dir
("/home/lm/src/iaaa/src/modules") Discover only shows this:
$ curl http://localhost:8880
<?xml version="1.0" encoding="utf-8"?>
<services><service
ident="http://purl.org/xml3k/akara/services/registry"><path
template="http://localhost:8880/?service={service?}"></path><description></description></service></services>
I'm I doing something wrong?
-- luismiguel
2011/4/15 Luis Miguel Morillas <mori...@gmail.com>:
Modules are enabled using the akara.conf MODULES declaration now,
rather than by placement in a modules directory, e.g.
MODULES = ["akara.demo.sysinfo"]
Mark.
Sure, but akara loads by default modules stored at
$HOME/.local/lib/akara/modules. Thanks, modules directory works fine
when modules are added to PYTHONPATH.
Regards,
-- lm
> Mark.
Ah, I didn't realize the modules directory was used at all anymore.
I've been using MODULES exclusively recently, since it simplified the
deployment process by removing the need to copy the modules.
Mark.