arfa wrote: Mon Jul 22, 2024 12:08 am
Most of my development is offline; I am off-grid quite a lot.
Developing on a windows localhost environment tends to be very problematic.
Basically you should put up a webdev env as close to the production env you will install the website at the end.
One of the basic things you'd need to do is to resolve the target domain on your localhost by configuring apache webserver in your wamp (assuming you work on windows OS).
I can't get into details as I haven't done this for years. Just pointing out crucial things.
This way you should have less problems with all configuration data during migration.
There are dozen approaches to migrate a
website. One of the most important things before is to always use relative links, but most of the CMS available on the market tend to force absolute links in content.
anyway, installing a fresh CMS instance on production server, and then importing data from locally developed website tends to be the least problematic. You don't even need to use any backup solutions, just upload the content of /bl-content directory, and this should be enough. Like with every flat file cms. Ohh with 1 exception: do not overwrite the site.php config file in /databases dir as it contains installation settings.
unfortunately bludit's website is still down and as far as I remember there were some migration and update hints for new users.
.