Explore >> Select a destination
|
You are here 
|
oct8l.gitlab.io | ||
| | | | |
blog.m5e.de
|
|
| | | | | In this Guide, I want to cover installing ZITADEL with PostgreSQL on a Linux system. Please be aware that PostgreSQL support is still in Beta at the time of this writing, and you will need a PostgreSQL installation with Version 14 or higher. NGINX Proxy Create a new subdomain and point it to your server. Use certbot -d domain.name for creating a new SSL Cert. Create a new file in /etc/nginx/sites-available/domainname | |
| | | | |
www.hallada.net
|
|
| | | | | I've been meaning to add a commenting system to this blog for a while, but I couldn't think of a good way to do it. I implemented my own commenting system on my old Django personal site. While I enjoyed working on it at the time, it was a lot of work, especially to fight the spam. Now that my blog is hosted statically on Github's servers, I have no way to host something dynamic like comments. | |
| | | | |
www.tyil.nl
|
|
| | | | | ||
| | | | |
joshuarogers.net
|
|
| | | Just over a year ago we went over how to setup a reverse proxy that would require our users to authenticate. In our original proxy article, we generated some NGinx configuration that looked a bit like... location / { proxy_pass http://jira; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } And it worked. And everyone was happy. Until the day the request came in that NGinx should add a fixed set of credentials to all upstre... | ||
