I couldn’t find answer for my scheme here. Can you help with my task?
I think that this info may be userful for those members who are not familiar with programmings, hosting moments and used to have file manager, MySQL and phpMyAdmin to serve Wordpress websites.
I found that it’s better to have a separate hosting for Wordpress with it’s own domain and a special dedicated hosting for a Discourse instance.
What I have:
Discourse (hosting1, domain1) + Wordpress (hosting2, domain2).
- Discourse is a main site, that is promoted. Now it’s on digitalocean server1, within a domain1.
- Wordpress will be used only as a membership platform and payments gateway.
WP is installed on the server2 with another hosting provider. Now it has its’ own domain2.
- open Wordpress site as a subdomain of Discourse domain (wordpress.discourse.site), but host WP and Discourse separatly as it is now.
- give user ability to login once in Discourse and stay loged in Wordpress instantly) - I think that it is another way to “make wordpress sso provider for discourse” or I’m mistaken here?
The logic is following:
- User visits main Discourse site. Signup at Discourse site (Important), because Discourse is a main entrance.
- When the user wants to pay for a membership the user goes to the subdomain Wordpress.Discourse.site. this site is used ONLY to serve memberships.
- The user doesn’t need to login Wordpress, because he is logged in Discourse already.
- User pays and WP membership plugin adds him to a specific group, granting necessary access.
- User is redirected to the main Discourse.site.
Please, give me your thoughts on
what is possible and what is not,
how can I do this DNS redirect,
may be your ideas.