On my local install (non-functional now because of this), I would like to use different domains for different blogs. How to accomplish that?
1 Like
As it is today, you’d need to create an entirely new single-user instance (including a database) for each of those domains.
But could you explain your use case more? Maybe we could support this. I’m assuming you’d like to do this using one login with multiple blogs?
No really looking for one login for multiple logs, but to allowing wife, child, and a couple of closed friends to have their blogs while using their own domains (similarly to write.as).
1 Like
I figured I could add aliases to the main server, with my wife, child, and friends domains. It works, but at certain point (haven’t figured out where) the main domain “comes afloat,” and the users get logged out.
Update: Figured it out. The main domain “comes afloat” after an edit.
Hmm yeah, if we added support for path installations you might be able to point each to an alias on your server.
But what do you mean by “comes afloat”?
Comes afloat, as it it shows on the address bar. Aliased domains can be used (https://domaina.com/user/, https://domainb.com/user/), but as soon as edits are made, it shows https://maindomain.com/user/.
1 Like
@matt Could you please kindly update us on the status of this.
I also would like to have a single login account and use multiple domains as follows:
• DLKR.me for my blog about content creation and related tech
• DLKR.art for my blog sharing my art
• DLKR.photos for my blog sharing my photography
• DLKR.jp for my Japanese business blog
• DLKR.tokyo for the same, but in English
• DLKR.co for the same, but in English and targeting a global audience
And, I’d like to have at least one static page per blog/domain.
Is this possible or do I need a separate Pro account for each domain? As you can imagine, that would be very expensive for me, and I’d be better off staying on Strikingly.com for the time being…
I have three blogs under my sinlge Pro user, each at its own custom domain. Setup was simple and quick and painless. You can see them here:
Great job, Matt!
3 Likes
My original post is about Writefreely, not write.as (self hosted, not “pro” hosted). I haven’t tried, but is this still an existing limitation, @matt?
Yes, for now there’s no support for multiple custom domains on a single WriteFreely instance. Here’s a full list of the differences between WriteFreely and Write.as: Differences between Write.as and WriteFreely
Subdomain and custom domain support. Right now this isn’t in WF because it adds more administrative work configuring a server, instructing users, generating SSL certificates, etc. We may support it eventually.
Any plans towards changing this? I’m happy to do the extra admin effort, but I’d like to run an instance that lets my friends bring their own domains.
2 Likes
Hi @Fastidious,
did you tried to use a reverse proxy to redirect https://maindomain.com/user1 to https://user1.com and /user2 to https://user2.com?
So each user maybe could have a custom domain and redirected from main domain to the users domain?
That would be nice for a planned site I would give WriteFreely a try… But I would need custom domains for users and custom stylesheets too…
Maybe search feature could be a problem if search results include user users content…?
I was actually quite excited to use WriteFreely to replace the hosting of a few of the blogs that I have hosted for myself and friends/family over the years. This issue seems to be a bit of a showstopper at the moment. Each blog has its own domain and I do not want to move them. If anyone has figured out a reasonable workaround or if this feature could be implemented I would be very interested!
I wonder how much extra work is involved in this feature. The main changes appear to be in routing and the automatic creation of certificates, but I would imagine it is a minimal extension. Is this something for which WriteFreely might be looking for contributions?