-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: 'aleph.manage' has no attribute 'app' #3606
Labels
bug
Things that should work, but don’t
Comments
Paradoxxs
added
bug
Things that should work, but don’t
triage
These issues need to be reviewed by the Aleph team
labels
Feb 3, 2024
tillprochaska
added a commit
that referenced
this issue
Feb 4, 2024
I broke the default Dockerfile command in `7cfcb5`. While the Dockerfile did always specify the WSGI app `aleph.manage:app`, this has been incorrect for some time and it should have always been `aleph.wsgi:app`. Previously we never actually ran a container with the default command though and instead specified the command in the `docker-compose.yml` file. I removed the "duplicate" command in the `docker-compose.yml` in the referenced commit and thus the default command in the Dockerfile is now used. I’ve now changed the default command specified in `Dockerfile` to be in line with the command previously set in `docker-compose.yml` (https://github.com/alephdata/aleph/blob/3.15.5/docker-compose.yml#L76). * The WSGI app is now `aleph.wsgi:app` (this is specified in `gunicorn.py` not via a CLI option). * Uses 6 workers by default (instead of 5). Closes #3606
tillprochaska
removed
the
triage
These issues need to be reviewed by the Aleph team
label
Feb 4, 2024
Hi @Paradoxxs, thanks for reporting this problem. Unfortunately the installation guide referenced a configuration template on the unstable In the meantime, until this is merged, you should be able to use the Docker Compose configuration from the |
tillprochaska
added a commit
that referenced
this issue
Feb 5, 2024
* Fix default Dockerfile command I broke the default Dockerfile command in `7cfcb5`. While the Dockerfile did always specify the WSGI app `aleph.manage:app`, this has been incorrect for some time and it should have always been `aleph.wsgi:app`. Previously we never actually ran a container with the default command though and instead specified the command in the `docker-compose.yml` file. I removed the "duplicate" command in the `docker-compose.yml` in the referenced commit and thus the default command in the Dockerfile is now used. I’ve now changed the default command specified in `Dockerfile` to be in line with the command previously set in `docker-compose.yml` (https://github.com/alephdata/aleph/blob/3.15.5/docker-compose.yml#L76). * The WSGI app is now `aleph.wsgi:app` (this is specified in `gunicorn.py` not via a CLI option). * Uses 6 workers by default (instead of 5). Closes #3606 * Update mentions of `master` branch to `main` We recently renamed the `master` branch to `main` and changed the default branch in GitHub to `develop`. Because a branch with the name `master` doesn’t exist anymore, GitHub redirects all links to the default branch which is not `develop`. In some cases this leads to problems, e.g. the installation guide effectively links to the Docker Compose configuration and environment templates on the `develop` branch instead of the stable `main` branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just downloaded Aleph, and changed the configuration file according to the installation guide
And start the container with docker-compose up -d
The problem is with the API container where I get the error of 'aleph.manage' has no attribute 'app' and here after it shutsdown.
Aleph version
3.15.5
Additional context
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/gunicorn/util.py", line 414, in import_app
app = getattr(mod, name)
AttributeError: module 'aleph.manage' has no attribute 'app'
Failed to find attribute 'app' in 'aleph.manage'.
[2024-02-03 08:09:01 +0000] [9] [INFO] Worker exiting (pid: 9)
The text was updated successfully, but these errors were encountered: