Viktor Levytskyi

I am the SysAdmin for a self-host UK forum for self-builders. We are currently doing a platform refresh from a 4-core to a 6-core VPS (mainly because the latter bundle rebaselines to a currently supported Ubuntu LTS version and doubles the SSD storage available).  I am moving to using Docker for both production and test on the new server.  
Here is the announcement topic: BuildHub – Moving to New Server and Github. Here is the Github repo for the project: https://github.com/TerryE/docker-buildhub. I don't have any assistance to request, ATM.   The project is pretty much self documented.  You just need a host server with docker-compose, docker.io and git installed (I have a local RPi4  with 256Gb NVMe SSD running Raspbian 64bit Lite and it runs fine on it).  Set up your project directory and git init it, git pull this repo. Set up your environment and secrets according to the env.default-template.  Run extensions/build-all to build the extension images and run the docker-compose to build and bring the forum up.  This will bring up 5 containers for the stack: httpd, php, mysql, redis and hk (cron-based housekeeping).  Note that the build supports two separate instance stacks: forum (on 80 and 443) and test (on 8080 and 4443).
This is a work-in-progress, but about 90% complete.  Anyone is free to copy / clone / raise issues through the GitHub issues system.  Enjoy. 😊

I'm afraid you shouldn't expect an update:
 

Using it with IPS v4.7.4 without any issue ATM 🙂 

Any updates? 

To create a new language based off of the default language that comes with our software, you would simply create a new language in ACP -> Customization -> Languages. It will be based off of the default language. This won't impact any existing third party applications/plugins other than their language string getting reverted to their defaults as well.

The same question... What about 4.6?

Has anyone tested it on 4.6 as yet? 
We really need this mod.

Hello,
I guess you can use conditions + css
{{if request.page > 2}} <style> #nbPinnedSeparatorTop, #nbPinnedSeparatorBottom, .cNbPinnedPost { display: none; } </style> {{endif}}  

A feature in the admin cp somewhere that lists all active widget blocks giving each a drop-down forums selector to check off which sub-forums the block would be visible on, would be very convenient.  It would allow for completely custom block and page layouts per sub-forum, increasing the software's layout versatility substantially with a relatively small addition. 

Correct - it's a warning reference. It contains data pertaining to the last item you were viewing to store with the warning if you issue one.

This is for the warning system. 

If you need help setting up IPS with Nginx and PHP-FPM, this guide is a bit dated but should help,
 

Morrigan, thank you for help.
Everything is working fine now.
I added full path "/home/{username}/web/{sitename}/public_html/uploads2" instead of relative path "/uploads2"  and migrator correctly moved all attachments.

Oops! 😁
Apologies, but we're an nginx shop. Glad it got you there!
I've edited my original post for future time travelers.

Don't do that. 🙂 That will become a nightmare to maintain over time.
Instead, leverage rewrites on your web server to take your vBulletin blog paths and redirect them to what IPS is expecting. So, in your case, create a permanent redirect from /blog/entry.php?b=XXXX to /entries/XXXX. This will then get rewritten internally by the IPS handler to the new location.
Any old links to blog/entry.php will still work and end up at the correct place and you don't need to modify/maintain any code. Behind the scenes, you'll have two redirects happening automatically:
blog/entry.php?b=1234 -> /entries/1234 -> /blog/whatever-the-new-ips-blog-url-is-5678

If you had redirect rules in vBulletin that were not the default URL paths, then the trick is to redirect from your old URL scheme back to what the out of the box vBulletin path would have been.
For example, we had a custom solution in place that would change our forum thread URLs to things like example.com/forums/forum-name/thread-name-1234/.
As part of our migration to IPS, we redirect that style of URL to what the original vBulletin URL would have been: example.com/forums/showthread.php?t=1234. This then gets redirected by the IPS handler to the correct migrated thread.

Hi Victor,
Our converter will already redirect vB Blog /entries/x URLs, all you would need to do is make sure those requests are redirected into your Invision Community platform i.e redirect yourdomain.com/blogs/entries/x-title to yourdomain.com/forums/entries/0-title our converter will automatically see this and redirect the request from there.
We don't redirect article paths because they can greatly differ from one vB install to another and may clash with our own Pages URLs.
The redirect rules are in the converter PHP files themselves /applications/converter/sources/Software/Blog/Vbulletin.php -> checkRedirects()
Thanks!
Stuart