Bricks now with Unlimited Sites & Upcoming Lifetime Price Increase

Taking a Bricks site live and combining with existing live site

I’ve been developing a new site using Bricks for an existing WP site.

We have a live server (with lots of data: 40k+ posts, 150k+ comments). I’m developing a new front end for it using Bricks on a separate staging server (using an old snapshot of the data). Soon I’m going to need to merge the lovely new Bricks front end with the current, live data/posts.

Has anyone been through this? I’m wondering how to do it with the least amount of pain/lowest amount of downtime / least number of sleepless nights :slight_smile: ?

One thing that’s in my mind, where does Brick store all of its magic? How do I make sure I don’t miss anything? Do I need to think of specific tables to bring across? etc, etc

I’d be grateful for any pointers from the Bricks team and others (@thomas, @timmse, @luistinygod, etc) - It should be of use to many people as they take their developed Bricks site live.

Hi, flimflam!

Sorry for the late reply! 40k posts and 150k comments? Holy $h1t :astonished:
This is a lot, and I have to confess that I’ve never worked in those gigantic dimensions, but actually, it doesn’t matter if there are 40 or 40k posts :smiley:

Once you have your staging page ready and everything is working smoothly, all you have to do is switch, so the downtime should be limited. I usually put new pages in their own folder and use a subdomain for the time being.

When the new site is ready, I update the database and replace the subdomain with the final domain, which I then direct to the new folder, and that’s it usually - almost 0 downtimes. Well, of course, you have to recheck everything, but usually, it works out pretty well.

It is essential to make regular backups (especially of the database). Then, if something should go wrong during crucial steps, you can jump back and try again.

Regarding the Bricks magic: actually, you don’t need to pay attention to anything as long as your posts are already Gutenberg posts anyway it should all work smoothly. Of course, it gets more complicated if there are a lot of custom fields and co in the game - but even that shouldn’t be a problem.

Depending on how “clean” your database is, you might want to clean it up with a plugin like WP-Optimize or WP-Sweep.

What I would recommend is something like EWWW Image Optimizer (or another similar plugin) to compress your images and deliver them as webP. With 40k posts, there is undoubtedly a lot together.

Also crucial about images: the image sizes. Choose your image sizes wisely and with care. I usually regenerate my images with the plugin Force Regenerate Thumbnails, which has the great advantage of deleting the old and no longer used image sizes. To be on the safe side, make better before also a database + uploads backup.

I have recently converted an architect’s website to Bricks and noticed that relatively many images were duplicated and triplicated in the media library (because they were uploaded multiple times - for whatever reason). Looking for a plugin that removes these “superfluous” images I came across Media Cleaner, which did an excellent job (Pro version).

Last but not least, I repeat the most crucial point: backups, backups, backups, before and after every critical step. Regular backups will save you sleepless nights :smiley:

Have a nice weekend,
timmse