Sidebar + Navbar Template

[srcarvalho12]

It would be interesting to have the option to change the general template of the application, for example: Template with Sidebar + Navbar and Template with Navbar only

[lovasoa]

Hello and welcome to SQLPage!
The general template of the application is defined in the shell component, that already has quite a few options available.
However, creating a sidebar is currently not possible. Would you be interested in implementing this feature ? It shouldn't be too hard, because all the pieces are already in place. And I'll be here if you need help !

To get started, here are:

• the shell component source code: https://github.com/lovasoa/SQLpage/blob/main/sqlpage/templates/shell.handlebars
• an example of how to create a side menu with tabler, the css framework used in sqlpage: https://tabler.io/docs/layout/page-layouts

[srcarvalho12]

Wonderful, go ahead, I'll help you create a sidebar in the next few days

[lovasoa]

That's fantastic! I appreciate your willingness to collaborate. If you have any questions or encounter any challenges while working on it, feel free to reach out. You can open a "draft" pull request as soon as you have something, and I'll be happy to review it and give you pointers if you get stuck.

[srcarvalho12]

I managed to create a small sidebar draft #265 .
I had problems with "scrollbar-color", as it has a predefined style and I would like to use transparent, for example:
scrollbar-color: rgba(var(--tblr-scrollbar-color, var(--tblr-body-color-rgb)), .16) transparent;

[srcarvalho12]

I'm trying to configure nginx to use the reverse proxy on a VPS which works normally when pointing to "/", but if I try to access any endpoint like "/user.sql" it downloads the .sql file instead of opening the page, what can I do? Here is my vhost:

server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
{{ssl_certificate_key}}
{{ssl_certificate}}
server_name www.my-url.com;
return 301 https://my-url.com$request_uri;
}

server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
{{ssl_certificate_key}}
{{ssl_certificate}}
server_name my-url.com www1.my-url.com;
{{root}}

{{nginx_access_log}}
{{nginx_error_log}}

if ($scheme != "https") {
rewrite ^ https://$host$uri permanent;
}

location @reverse_proxy {
proxy_pass {{reverse_proxy_url}};
proxy_http_version 1.1;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_pass_request_headers on;
proxy_max_temp_file_size 0;
proxy_connect_timeout 900;
proxy_send_timeout 900;
proxy_read_timeout 900;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
proxy_temp_file_write_size 256k;
}

{{settings}}

add_header Cache-Control no-transform;

index index.html;

location ^~ /.well-known {
auth_basic off;
allow all;
try_files $uri @reverse_proxy;
}

location / {
try_files $uri @reverse_proxy;
}
}

[lovasoa]

The try_files directive in Nginx specifies the files to attempt to serve before falling back to a specified URI or passing the request to a proxy server. It's typically used within a location block to define the behavior when a request matches that location.

In the provided configuration, the try_files directive is used within the location blocks to attempt to serve a file based on the specified URI. If the file is not found, it falls back to the @reverse_proxy location block, which proxies the request to another server.

When a request is made for an endpoint like "/user.sql," Nginx interprets it as a file request and attempts to serve the file directly if it exists in the specified root directory. If the file exists, Nginx serves it, which is not the desired behavior.

Therefore, you must ensure that Nginx doesn't serve files directly when handling requests meant for the reverse proxy. Adding a specific location block to handle requests for certain file extensions, like ".sql" in this case, can prevent Nginx from serving them directly and instead passing them to the reverse proxy.

[srcarvalho12]

Wonderful, thank you. Is it possible to forward endpoints like "/usar.sql" to "/user" using rewriting in nginx?

[lovasoa]

location ~ \.sql$ {
    include my/proxy/conf;
}

location / {
    try_files $uri @reverse_proxy;
}

location @reverse_proxy {
    include my/proxy/conf;
}

[srcarvalho12]

I sincerely thank you for your help!

[lovasoa]

possible to forward endpoints like "/user.sql" to "/user" using rewriting in nginx?

Yes, it's possible. See this previous discussion: #231

[srcarvalho12]

Incredible! I sincerely thank you for your great help.

[srcarvalho12]

I use nginx served through CloudPanel, its vhost comes in this standard that I sent above, but I tried to add these configuration lines:

location ~* ^(.).sql$ {
rewrite ^(.).sql$ $1 permanent;
}

It redirects to the page without the .sql, but gives a 404 error

[lovasoa]

What you want is the opposite, isn't it? You want nginx to receive requests without .sql, and rewrite then to add .sql before forwarding them to SQLPage.