Landing Page

[vifyirusti]

I don’t know how to do this. I searched a lot but couldn’t find it.

discourse.domain.com >> Discourse Forum >> I did this.

domain.com >> HTML CSS JS Landing Page >> I don’t know how to do this.

My knowledge of Ngix and docker is limited. I’m waiting for your help.

Respects.

[HAWK]

Are you asking for support for something that is outside of Discourse? Your question is a little unclear. Can you elaborate?

[pfaffman (Jay Pfaffman)]

@vifyirusti

HTML CSS JS Landing Page >> I don’t know how to do this.

The recommended solution is typically to make your landing page on another server (and use www subdomain). If you want to run both on the same server you can look at Set up Discourse on a server with existing Apache sites. There is a similar topic for nginx. Both assume that you know how to create your html landing page.

[vifyirusti]

Thank you for your help, sir.

Respects.

[vifyirusti]

In fact, a second server can be costly. So I am looking for a different solution.

Is it possible for me to implement a solution like the example below?

discourse.domain.com/specific_page.html

[Canapin (Coin-coin le Canapin)]

@vifyirusti

In fact, a second server can be costly. So I am looking for a different solution.

Could you detail what would be the purpose of this page, and what it would contain? You mention an HTML page, so it would be static, which can make things easier…

You could have a look at Page Publishing, or make use of CSS to remove unused elements from a page to make it appear as different from your Discourse forum, for example based on this: Page Publishing - #145 by denvergeeks

[vifyirusti]

Hello,
I can share a static html page as an example.

W3Schools online HTML editor

I want to add a page like this. This is my aim. Some html, some css, some js. That’s all.

Respects.

[Canapin (Coin-coin le Canapin)]

Though you could find some workarounds like my examples to have a page that differs from your Discourse’s appearance, making it look like it doesn’t belong to Discourse, the JS part would be tricky.

I think the most proper way would be either to have a web server along Discourse on your server. There’s documentation about this:

Run other websites on the same machine as Discourse

If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will need to copy and edit samples/standalone.yml with your favorite tex…

Set up Discourse on a server with existing Apache sites

It’s not as daunting as it sounds! While this may sound a bit intimidating at first, it’s really not all that bad. You basically need to do two things: Install HAProxy (or an alternative) which will take over port 80 and then divert your Discourse traffic to your docker container, and all your other sites to your usual Apache set-up. Let Apache know which port to listen for. While this is only a rough guide, it should do a good job of pointing you in the right direction. Let’s get star…

Or to host your website on a different server, which is much easier. A low-specs, cheap one would perfectly do the job.

You can find such hosting plans at about 2$/month. You can even have a free 100 MB plan on OVH, but I think the domain must be registered on their site.