Link in the top-left corner of Hyperkitty
Hello,
There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change.
Thanks, Seth
On 5/8/20 7:34 AM, Seth Seeger wrote:
There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change.
You have to edit the display name for the domain in the Django web admin Sites section.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 8, 2020, at 10:58 AM, Mark Sapiro <mark@msapiro.net> wrote:
On 5/8/20 7:34 AM, Seth Seeger wrote:
There is a link to the root of Hyperkitty in the top left corner of my Hyperkitty pages. It links to the correct domain, but the text isn’t right - it’s the first domain name I was using at the beginning of my install for testing. I’d like to update it, but can’t find what to change.
You have to edit the display name for the domain in the Django web admin Sites section.
Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for.
Thanks, Seth
On 5/8/20 8:06 AM, Seth Seeger wrote:
On May 8, 2020, at 10:58 AM, Mark Sapiro <mark@msapiro.net> wrote:
You have to edit the display name for the domain in the Django web admin Sites section.
Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for.
It should show the display name corresponding to the domain name that matches the domain in the URL that you go to. If this doesn't seem correct, perhaps there is some issue with the way you are proxying in your web server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Il 08/05/20 17:13, Mark Sapiro ha scritto:
On 5/8/20 8:06 AM, Seth Seeger wrote:
On May 8, 2020, at 10:58 AM, Mark Sapiro <mark@msapiro.net> wrote:
You have to edit the display name for the domain in the Django web admin Sites section.
Huh. I had it properly set for the domain that is active, but it wasn’t taking affect. I changed it for the (old) test site, and it changed it. So the name that is showing doesn’t match the domain name that I was changing it for.
It should show the display name corresponding to the domain name that matches the domain in the URL that you go to. If this doesn't seem correct, perhaps there is some issue with the way you are proxying in your web server.
Also in debian there is the some problem.
The domain name is that of the installation site (example.com) and does not change if you change the webserver and the domian. It seems to be static. You can change it changing the site name in django admin console, but it doesn't change if you change the webserver name.
Which file does provide it?
Thanks
-- Gelpi ing. Andrea
It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here.
On May 8, 2020, at 12:11 PM, Gelpi Andrea <liste@gelpi.it> wrote:
Also in debian there is the some problem.
The domain name is that of the installation site (example.com <http://example.com/>) and does not change if you change the webserver and the domian. It seems to be static. You can change it changing the site name in django admin console, but it doesn't change if you change the webserver name.
I believe this is what I’m seeing. I was able to change the displayed name by changing the original entry in Django. That name displays no matter what the URL hostname is.
I am running on Debian Stretch.
Seth
On 5/8/20 10:36 AM, Seth Seeger wrote:
I believe this is what I’m seeing. I was able to change the displayed name by changing the original entry in Django. That name displays no matter what the URL hostname is.
This is strictly a Django thing. The HyperKitty template, hyperkitty/templates/hyperkitty/navbar-brand.html, contains this:
<a class="navbar-brand" href="{% url 'hk_root' %}">{{ site_name }}</a>
{{ site_name }} is provided by Django when the template is rendered.
In my case in my test installation, I have three sites in django.Sites:
Domain name Display name example.com example.com msapiro.net msapiro.net msg1.msapiro.net msg1
example.com is a dummy, and it is also referenced in my settings by
SITE_ID = 0
which may have something to do with my success, but if I go to HyperKitty via https://msapiro.net/, I see the site name msapiro.net, and if I go via https://msg1.msapiro.net/ I see the site name msg1.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 8, 2020, at 11:13 AM, Mark Sapiro <mark@msapiro.net> wrote:
It should show the display name corresponding to the domain name that matches the domain in the URL that you go to. If this doesn't seem correct, perhaps there is some issue with the way you are proxying in your web server.
Here is my proxy entry in Nginx:
location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8080; uwsgi_read_timeout 300; }
My uwsgi_params file:
uwsgi_param QUERY_STRING $query_string; uwsgi_param REQUEST_METHOD $request_method; uwsgi_param CONTENT_TYPE $content_type; uwsgi_param CONTENT_LENGTH $content_length;
uwsgi_param REQUEST_URI $request_uri; uwsgi_param PATH_INFO $document_uri; uwsgi_param DOCUMENT_ROOT $document_root; uwsgi_param SERVER_PROTOCOL $server_protocol; uwsgi_param REQUEST_SCHEME $scheme; uwsgi_param HTTPS $https if_not_empty;
uwsgi_param REMOTE_ADDR $remote_addr; uwsgi_param REMOTE_PORT $remote_port; uwsgi_param SERVER_PORT $server_port; uwsgi_param SERVER_NAME $server_name;
Is there something I’ve missed? I followed a tutorial for this (which is no longer available).
Seth
participants (3)
-
Gelpi Andrea -
Mark Sapiro -
Seth Seeger