Selfhosted

60093 readers

1151 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Self-hosting journey update, and WordPress: latest development from a super-newbie (poliversity.it)

submitted 2 weeks ago by elettrona@poliversity.it to c/selfhosted@lemmy.world

7 comments fedilink hide all child comments

Self-hosting journey update, and WordPress: latest development from a super-newbie

@selfhosted

I must recap as I set my instance to delete 2-weeks-old posts.

Months ago, I talked about my very first journey with self-hosting my digital services, including my website.
As I'm not very skilled with sysadmin stuff, I use a YunoHost installation with all its pros and cons.

Having severe accessibility needs (I'm totally blind) I have limited choices for what concerns CMS software with related extensions if any. So after months of exploration and test, I've come back home. To WordPress.

Last time I updated Fediverse about my experience, I was struggling with multisite network giving an unpleasant error in the non-main site, such as "too_many_redirects"
Making it short, I discovered that YunoHost doesn't let me run a multisite properly when installed in a subdomain such as blog.domain.tld
So I had forcefully to install it in the main domain, and a subdirectory such as domain.tld/wp

Now I'm concentrating on my theme, I will clone it with the plugin "CreateBlockTheme" then activate it network-wide.
I need a multisite for multilingual, as all current multilingual plugins have poor accessibility support, and are mostly paid.

Then I may need a new taxonomy registered to organize stories, the glossary plugin, SEO plugin, ActivityPub, and I should be all set!

The last, hard, challenge I have, is the fact that now my site runs into "domain.tld/permalink-post" for Italian, and "domain.tld/english" for English
The new one should run "domain.tld/wp/post" and "domain.tld/wp/english/post"

YunoHost doesn't let me build a WordPress site in the root directory with multisite installed, so I must find the way to tell nginx I want the product to be physically on /wp/ but browser can point to domain.tld/post or domain.tld/english/post...

And if possible, this change to be in a file on its own, in order to be able to delete it without damaging the whole nginx conf.

Last detail, I'm on hostinger, kvm2 package. vps.

#experience #multisite #nginx #SelfHosting #WordPress #YunoHost

you are viewing a single comment's thread
view the rest of the comments

[–] Jayjader@jlai.lu 1 points 1 week ago* (last edited 1 week ago)

No idea how easy this will be to follow if you're forced to rely on text-to-speech and/or other assistive technologies, but here goes:

to tell nginx the product is physically on /wp/, you probably want a root /wp directive
to tell nginx the browser can point to domain.tld/post or domain.tld/english/post, you probably want two location blocks (one for each url) that each contain a rewrite directive that massages the url requested by the browser into pointing to the correct post or page location.
for this to be in a file on it's own, and assuming your nginx setup is pretty standard, you probably want to have the entire server block be in a file that lives in the sites-available directory and symbolically linked ("symlinked") into the sites-enabled directory.

For the rewrites, here is the link to the relevant documentation page: https://nginx.org/en/docs/http/ngx_http_rewrite_module.html . You will need to understand the basics of how to write a Regular Expression, or get someone to write it for you. If you can't find a human that's available and willing to help, maybe a back-and-forth with an L.L.M. can get you to what you need (I don't like suggesting L.L.M.s but being sighted myself I don't really know if they're better or worse than recommending you just work at learning how to do this on your own, given the current state of the web).