What does it take to use Surfer as a “real” multidomain surfer?

[luckow]

www.example.com -> /app/data/public/example.com/index.html
www.example.org -> /app/data/public/example.org/index.html

Both on the same app instance. Will it work?

[james]

Hello @luckow
Indeed, I found nothing in the documentation for surfer https://docs.cloudron.io/packages/surfer/ regarding "real" multidomain hosting.
I will relay this question, and hopefully it can be answered soon.

[girish]

I guess we have to implement this . In conversation in the past, @nebulon was reluctant to make surfer as some advaced Apache/nginx. I think he thought it was slippery slope to add vhost to Surfer and then we have to implement all the apache/nginx vhosting options .

If you want vhosting, have you considered LAMP app? You can then set up a apache config to route serving of pages to whichever subdirectory you want . I think @robi had a config for this some time ago.

[luckow]

I really like using Surfer for static websites. It's a nice little thing that does one job brilliantly. The reality is that I have a lot of domains with few pages and little traffic. Installing an instance of Surfer for each domain is not viable. If there is currently no option for multidomain, I will temporarily switch to LAMP because of the configuration options with RewriteEngine. The moment Surfer has the multidomain feature built in, I'll switch back (because of the fat stack in LAMP, which I don't need).

[andreasdueren]

@luckow +1. Use surfer for lots of static, low traffic sites. It's great!