# myowndomain.net
server {
  listen 80;
  server_name myowndomain.net;
  location / {
    proxy_pass http://127.0.0.1/myuser$request_uri;
    # proxy_pass http://writeDomain.social/myuser$request_uri;
    proxy_set_header Host example.com;
  }
}

# myowndomain.net
server {
  listen 80;
  server_name myowndomain.net;
  location / {
    proxy_pass http://127.0.0.1/myuser$request_uri;
    # proxy_pass http://writeDomain.social/myuser$request_uri;
    proxy_set_header Host myowndomain.net;
  }
}

In reply to @dannekrose:matrix.org
Simple answer is that it's not something in write-freely itself, but something to be set up via Nginx which serves the HTTP traffic to and from the wider-web and the internal server.

Would it make it possible to write texts and publish them as:

mydomain.net/one-permalink
mydomain.net/another-permalink

In reply to@mltemlte:matrix.org

Would it make it possible to write texts and publish them as:

mydomain.net/one-permalink
mydomain.net/another-permalink

In reply to @dannekrose:matrix.org
Sure, but I'm not sure what the purpose of the original one-permalink is. If you're talking about the name of the blog, you can create a blog with the name of the permalink you want to use, and then after it's created, you can edit the name of the blog/description and the path portion (/one-permalink) will not change.

With that said, I think seeing some concrete examples of exactly what the end goal is would be useful since it almost sounds like you're looking for WordPress-level of functionality.

Here's an example of what I'm looking for:

Custom domain: https://thekjd.net/
One blog with a permalink including the custom domain: https://thekjd.net/december-7-2023
Another blog: https://thekjd.net/december-6-2023
Etc.

In reply to @dannekrose:matrix.org
Sure, but I'm not sure what the purpose of the original one-permalink is. If you're talking about the name of the blog, you can create a blog with the name of the permalink you want to use, and then after it's created, you can edit the name of the blog/description and the path portion (/one-permalink) will not change.

With that said, I think seeing some concrete examples of exactly what the end goal is would be useful since it almost sounds like you're looking for WordPress-level of functionality.

Here's an example of what I'm looking for:

Custom domain: https://thekjd.net/
One blog post with a permalink including the custom domain: https://thekjd.net/december-7-2023
Another blog post: https://thekjd.net/december-6-2023
Etc.

In reply to @dannekrose:matrix.org
You can handle that a number of ways with Nginx and rewrite configurations. If whomever is providing your writeFreely (not Write.as) instance services is not well-versed in Nginx, if they find someone to help guide them or find good resources, they should be able to get up to speed on how to do this with Nginx server blocks and related configuration.