-
Notifications
You must be signed in to change notification settings - Fork 174
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
No documention for embedded web server configuration #547
Comments
I would like to know how did you manage to access the web ui from outside the server. |
Hi, could you explain what kind of documentation you are expecting ? We can improve it. For now, there is the README: https://github.com/ansible-community/ara?tab=readme-ov-file#requirements and the docs: https://ara.readthedocs.io/en/latest/api-configuration.html |
I don’t know why, but the documentation refers to different variables by name compared to variables in settings.yml inside the container, e.g. ARA_DATABASE_ENGINE vs. DATABASE_ENGINE. Also, the name ALLOWED_HOSTS is misleading. I had to do a lot of googling until I realized, that it refers to the server itself, not the host trying to access it. |
I think I got confused with 'API server', but as stated in the documentation, the api server contains a REST API and web interface. I thought I had to start the web server myself. I did a second installation on Rocky Linux 9.4 minimal with podman, started the api-server and opened port 8000/tcp. |
On my first attempt with podman I could not access the web ui, because I did not know about the settings file.
After adding '*' to ALLOWED_HOSTS in |
What is the issue ?
How do I correctly configure the
ara
web interface? At least the embedded server should be documented. There appears to be only documention for configuring the web server for the 0.x version of ara. Maybe I missed that part in the documentation?ara-manage runserver
did not work for me because of missing python dependencies.After installing some python dependencies, fixing some imports and configuring the settings.yaml file, I got it to work at last.
What should be happening ?
Update documention for quick configuration.
The text was updated successfully, but these errors were encountered: