# Cockpit CMS and mini multisite

**URL:** <https://discourse.getcockpit.com/t/cockpit-cms-and-mini-multisite/1422>\
**Category:** General\
**Created:** [May 4, 2020, 6:37am UTC](https://discourse.getcockpit.com/t/cockpit-cms-and-mini-multisite/1422 "2020-05-04T06:37:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastian](https://avatars.discourse-cdn.com/v4/letter/s/4da419/32.png) [@Sebastian](https://discourse.getcockpit.com/u/Sebastian)\
**Post date:** [May 4, 2020, 6:37am UTC](https://discourse.getcockpit.com/t/cockpit-cms-and-mini-multisite/1422/1 "2020-05-04T06:37:08Z")

</div>

Hello everyone and congratulations to the whole Cockpit team. I am a front-end developer with experience in html, css, javascript, ajax, php. I would like to use cockpit for a personal project.  
The configuration that I would like to obtain would be this:

- [cms.cockpit.com](http://cms.cockpit.com) (with all my content)
- website1 (in different server)
- website2 (in different server)
- websiteN (in different server)  
These sites would be few pages that take data from [cms.cockpit.com](http://cms.cockpit.com).

Which framework would you recommend? What would be the fastest way to make it happen?  
Create all static sites with JS? Several installations would be needed and maintaining them would not be easy. Am I wrong? I should change my approach to my knowledge …  
Yesterday I tried Gatsby but the plugins didn’t work.

Thanks to everyone who will help me.

---

<div class="post-metadata">

**Author:** ![dejanzombie](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/dejanzombie/32/589_2.png) [@dejanzombie](https://discourse.getcockpit.com/u/dejanzombie)\
**Post date:** [May 5, 2020, 6:24pm UTC](https://discourse.getcockpit.com/t/cockpit-cms-and-mini-multisite/1422/2 "2020-05-05T18:24:22Z")

</div>

> [@Sebastian](#):
>
> approach

If you feed all website content from Cockpit API server (in your example: [cms.cockpit.com](http://cms.cockpit.com)) don’t let frontend of your website to have direct access to API, instead make some gateway on server side (PHP) and serve content to website visitors from website server.  
Here is why I recommend this:

- Most search engines are not quite good in parsing websites that gather main content from Ajax calls
- You can make your own caching mechanism
- Main thing is that you can make extended security by whitening IP address of websites servers on API server via Firewall
- Every website will have it’s own bandwidth

Possible bad thing is that your server response will be slow if your servers are not in the same datacenter or if you didn’t implement some caching mechanism.

---

<div class="post-metadata">

**Author:** ![jasonday](https://avatars.discourse-cdn.com/v4/letter/j/67e7ee/32.png) [@jasonday](https://discourse.getcockpit.com/u/jasonday)\
**Post date:** [May 6, 2020, 8:26pm UTC](https://discourse.getcockpit.com/t/cockpit-cms-and-mini-multisite/1422/3 "2020-05-06T20:26:23Z")

</div>

I’ve been having success with Nuxt JS + Cockpit recently. Nuxt requires less overhead with routes, etc. and getting up and running has been fairly quick.