Setup for the whole seosnap stack including dashboard, cache server and cache warmer used for prerendering and full page caching PWA's.

Installation

For usage

• Download and Extract release.zip from
  • Releases
  • Development Build
• Run ./install.sh or create a .env file manually
• Start the Seosnap stack with docker-compose up

For development

# Clone
cd ~
git clone --recursive [email protected]:experius/SeoSnap.git seosnap
# Configure
make install
# Start server
make up

Usage

• Dashboard: http://127.0.0.1:8080/ (default login: snaptron/Sn@ptron1337)
• API Docs: http://127.0.0.1:8080/docs
• Rendertron Server: http://127.0.0.1:3000/render/\<your url>

Logs directory ./logs

Cache directory ./cache

Run cache warmer

Make sure you have created a website via dashboard http://127.0.0.1:8080/seosnap/website/add/

make cachewarmer 
make warm A="cache <website id>"

Sync pages

To sync the sitemap pages to the SeoSnap database

make warm A="sync <website id>"

Multithreading

To run the cache warmer multiple time

make thread A="cache <website id>"

Nginx

Check the nginx.conf in the example folder

Crontab

check the crontab.txt the example folder and use the cachewarmer.sh & healthchecks.sh

• cachewarmer - create your own cachewarmer.sh and update the healthchecks url and the website ids
• healthchecks - Just replace the https://hc-ping.com/xxxx with your ping URL & change https://galaxy.experius.nl/ to your PWA homepage
• backups - there is an example cron which will make a backup of the cache files
• docker volumes cleanup - as you can see in the cachewarmer.sh the rendertron container will be restarted for performance so we need to clean that up

How it works

Dashboard

In the dashboard you add the website url along with the website sitemap that you want to make 'SeoSnaps' off.

Crawler / Cache Warmer

When the crawler is started it connects with the dashboard api. It uses scrapy to crawl the sitemap. The scrapy results are send to the administration/dashboard. Scrapy requests are send to the cache server. In a similar way that you would do a request to rendertron.

DEPRECATED - Cache Server

The cache server is a simple file caching server. If a file exist with the content of the page it serves the html from the file. If not, it renders the requested url with rendertron and saves the html output in a file. To refresh the cache the cache-warmer uses PUT requests instead of GET. This will force update from the cache file.

Rendertron Server

Rendertron + Cache is added and will replace the SeoSnap Cache Server

Recommended Rendertron config has been set in rendertron-config.json

Built with