In a support thread titled “Migrating from SMF to Discourse,” user dbm seeks to reset their Discourse instance to a fresh state before migrating from SMF 2.0.9. elberet explains there’s no built-in reset feature but suggests reinstalling Discourse and manually preserving customizations. They outline a migration process involving copying SMF files, installing the mysql2 gem, and running the importer script with database and timezone parameters. dbm opts to start fresh and manually copy key content, also asking about changing the domain name in app.yml — elberet confirms it’s possible and links to a guide on domain changes. riking adds that deleting /var/discourse/shared/standalone/postgres and rebuilding the container effectively wipes the database. Silvanus clarifies whether MySQL must be installed inside Docker or on the host — Mte90 elaborates on script usage, stressing the need to adjust MySQL settings, allocate sufficient RAM, and use proper timezone syntax (e.g., Europe/Rome). They also note the script can resume after crashes and share a patched mysql2 gem for date issues. Finally, justin provides two updated migration guides for SMF2 to Discourse. The thread ends with dbm praising the community’s helpful support.
I’m planing to migrate from SMF 2.0.9 to Discourse. I already have discourse running and everything is working fine. So my question is it possible to “RESET” discourse to look like i installed it fresh. And then migrate to Discourse from SMF?
EDIT: Also i have Woltlab 4.0.8 forum running (Also i can migrate to phpbb or any other that is required for the simpliest migration) ty
No, unfortunately there is no reset feature. You may need to reinstall Discourse and manually copy the things you wish to keep, i.e. your design, customizations, category settings and such.
Migrating SMF2 to Discourse is quite possible, but because it involves interacting with the Linux console and since there are a few technological barriers to bridge, the process can be somewhat finicky. Basically:
setup Discourse,
make a backup,
copy your old SMF2 forum to your new server under /var/discourse/shared/standalone/smf,
install the mysql2 gem in the container and run the importer:
cd /var/discourse && ./launcher enter app
apt-get update && apt-get install libmysqlclient-dev
su - discourse
gem install mysql2
cd /var/www/discourse/script/import_scripts
ruby smf2.rb /shared/smf -h $myql_server -t $php_timezone
In the last command, replace $mysql_server with the hostname or IP address of SMF2’s database server. This server must be reachable over the internet; if direct access isn’t possible (due to a firewall, for instance), you can try to tunnel the connection through SSH (see TCP FORWARDING in man ssh). If you can’t connect to your old server via SSH, you may need to temporarily install MySQL on the new Discourse server and import an SQL dump.
Finally, $php_timezone is the default timezone used by PHP on your old server. You can skip this setting (also remove the -t switch in this case), but imported timestamps may be slightly off.
Thanks @elberet for replying. I decided that i’ll start clean and just copy the important topics from last site. I’ve bulked all email and sent invite codes to users so no problems. Also changing host in containers/app.yml name from lets say
“www.oldname.rs” → “www.newname.rs” should be simple right? just modify app.yml and after my isp change ip from newname.rs to this discourse i can then modify it and rebuild it correct? there shouldnt be much problems with it?
You may need to run a script inside the container that rewrites internal links embedded in posts, but that’s it. There’s also a howto about changing the domain name.
The path is required to parse the Settings.php file and get the database connection parameters. In my case I imported the db locally and updated that file and created a folder with only this file
For timezone you have to write in that syntax: Europe/Rome as example and UTC
Add many ram to your vm. I forgot it to do it and now is important 45000 user with the default parameters
Don’t forget to install your discourse in your installation
Tweak a little bit the MySQL settings for more cache and more connections because with an huge db the connection can stop and you have to start again
The script reconize the already stuff imported so in case of crash you can execute again