Trouble getting Eden to run under Web2Py

[Andrea Jans]

Hello everyone,

I got the initial run done, but now when I try to start Eden, I get the following output:

web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2025
Version 2.27.1-stable+timestamp.2023.11.15.23.33.20
Database drivers available: sqlite3, imaplib, pymysql, pyodbc
2025-10-29 08:04:27 S3LOG WARNING: Ambiguous link/component alias (asset_asset.human_resource)
2025-10-29 08:04:27 S3LOG WARNING: Ambiguous link/component alias (req_req.job)
2025-10-29 08:04:27 S3LOG WARNING: Ambiguous link/component alias (sync_repository.job)

What step did I miss?

Thank you,

Andrea

[Andrea Jans]

This is the command I'm running:

python web2py.py -S eden -M -R applications/eden/static/scripts/tools/noop.py

---

From: eden...@googlegroups.com <eden...@googlegroups.com> on behalf of Andrea Jans <and...@jans.org>
Sent: Wednesday, October 29, 2025 8:11 AM
To: Eden ASP <eden...@googlegroups.com>
Subject: [Eden ASP] Trouble getting Eden to run under Web2Py

 

--
You received this message because you are subscribed to the Google Groups "Eden ASP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eden-asp+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/eden-asp/2acff474-702b-422b-b59d-090010d9f920n%40googlegroups.com.

[Dominic König]

You didn't miss a step.

These warnings concern potentially problematic data model details in some
modules - which though do not cause any immediate trouble. The intention is to
alert developers of these modules so that they can improve upon their
implementation.

If you are not working on these modules, you can safely ignore the warnings.

Is everything else working? Are you able to access Eden in the browser?

Dominic

[Dominic König]

onsdag 29 oktober 2025 19:22:47 CET skrev du:
> These warnings concern potentially problematic data model details in some
> modules - which though do not cause any immediate trouble. The intention is
to
> alert developers of these modules so that they can improve upon their
> implementation.

P.S. it is the CRUD framework that catches these problematic configurations and
issues the warnings. However, CRUD itself has a built-in workaround, so they
won't cause any trouble there.

However, they may cause problems in custom functionality using these modules,
and then it can be difficult to identify the root cause - which is why CRUD
provides these warnings in a place where this can easily be detected.

So, this is a debugging feature - and hence, if you turn of debug (in
000_config.py), these warnings will no longer be issued. That said, while
you're working on the code, of course you would leave debug on ;)

Dominic