Page 2 of 2

Re: Bludit multi-server

Posted: Fri May 31, 2019 6:51 am
by bozodev
I have also updated my Pi Lab Setup post with some changes that I have made to my "promote" script. I found some issues with the RSS and Sitemap plugins. Basically the dev url was being transferred to production.

Re: Bludit multi-server

Posted: Fri May 31, 2019 10:05 am
by diego
About the sticky session, if the user is not logged Bludit doesn't create a sessions so at the end the user is not sticky to a node and is balanced between the nodes.

If NFS is slow (I mention as simple solution) you can try GlusterFS, another way is sync the content with Git with the plugin Remote Content, I use this for the blog. https://github.com/bludit/blog

You can use HTML Code plugin to set some bottom bar like I did in https://demo.bludit.com

Nice project! Cheers

Re: Bludit multi-server

Posted: Fri May 31, 2019 2:51 pm
by bozodev
diego wrote: Fri May 31, 2019 10:05 am About the sticky session, if the user is not logged Bludit doesn't create a sessions so at the end the user is not sticky to a node and is balanced between the nodes.

If NFS is slow (I mention as simple solution) you can try GlusterFS, another way is sync the content with Git with the plugin Remote Content, I use this for the blog. https://github.com/bludit/blog

You can use HTML Code plugin to set some bottom bar like I did in https://demo.bludit.com

Nice project! Cheers
Thank you very much for your interest and feedback.

The NFS solution was definitely a consideration since it would simplify quite a bit. I just didn't want to lose the full benefit of load balancing.

I haven't given GlusterFS a full look yet, but since this is a project for learning I am sure I will.

There is one other benefit to the way I am doing things that I don't think sicky sessions would give me. If I used sticky sessions and logged in to the admin panel and made a change it would only be on one of the nodes. So visitors would sometimes see the change depending on the node they hit. The way I have it setup it is more like having a dev node and 3 prod nodes. The dev node just happens to reside on the primary prod node.

This gives me the ability to make changes or test new features without ever touching prod. I actually kinda want to build out a staging node as well. That way I could push things to staging that are ready to go to prod and continue to test new things in dev.That is probably overkill at this stage however.

I also looked into using things like lsyncd, but I didn't like having it happen fully automated. Since I have to edit files for the URL I decided the syncing could just be in the same promote script.

I do want to say that I am really enjoying working with Bludit. It is a very well together CMS.

Thanks

Re: Bludit multi-server

Posted: Sun Jun 02, 2019 6:58 am
by bozodev
I have just setup the plugins that I have put together for Pi Lab.

Check them out here: https://pilab.dev/plugins

Re: Bludit multi-server

Posted: Sat Jun 08, 2019 11:43 pm
by bozodev
I have added another plugin to my Pi Lab Plugins page.

It is let's you easily add your favorite web analytics code to your site. This is similar to the HTML Code plugin, but it allows you to specify a port for your "dev" node so that stats code will not be used on that node. This was a specific need for Pi Lab.

Re: Bludit multi-server

Posted: Wed Jun 12, 2019 6:18 am
by bozodev
Checkout my latest post showing off the Bludit API: https://pilab.dev/bludit-api-php-example

Re: Bludit multi-server

Posted: Mon Jun 24, 2019 5:51 pm
by bozodev
I have just upgraded Pi Lab with new 32 GB SD cards.

I wrote a post on how I did it with zero downtime for Pi Lab.

https://pilab.dev/pi-lab-sd-card-upgrade