xZero

Hi, So I own small-to-medium sized community with a lot of content (~2.5 mil. posts). My database hit the hardware limit and I cannot afford to vertically scale any longer. What I am experiencing are frequent lockups and general performance degradation at this point. No database optimisation helps, it just needs more resources. I decided to remove content for some users that posted a lot of trash and I know how to do it from the interface. The problem is that IPS processes tasks in batches, so background task is extremely slow and deleting content for the single user takes ages, even when I deploy the community on my desktop with 16 cores and 64GB RAM. What I would like to do is to use raw SQL or write my own script in Go to clean this content up, but I'm worried that I'll miss some relations. So far I think that removing topics involves following tables: forums_posts forums_topics forums_archive_posts core_attachments core_social_promote core_reputation_index core_follow I do not update core_search_index because I prefer to rebuild the index afterwards, But is that all? I know how to craft the query and how to target the posts, but I'm concerned of adverse effects I might experience later? This is query set I run on dev version when I sync database with production: DELETE FROM core_members WHERE member_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM forums_posts WHERE author_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM forums_topics WHERE starter_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM archive_posts WHERE archive_author_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM core_members_known_devices WHERE member_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM core_members_known_ip_addresses WHERE member_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM core_member_history WHERE log_member NOT in(1,1914,1476,1911,1642,1650); DELETE FROM core_follow WHERE follow_member_id NOT in(1,1914,1476,1911,1642,1650); DELETE FROM core_item_markers WHERE item_member_id NOT in(1,1914,1476,1911,1642,1650); TRUNCATE core_statistics; -- DELETE FROM forums_topics WHERE state='link' AND moved_to LIKE CONCAT( '3654&', '%' ) This leaves forum quite clean with some content to test with. It does not leave forum broken. I am basically trying to reverse engineer content deletion per member task. Code is quite messy and not fun to go through. What do you guys think? EDIT: I discovered that some tables like core_output_cache and core_log have grow extremely large. By truncating them, and recreating the database, everything is so much better now, that I might not even need to delete anything else.

It really depends what you're trying to achieve. If by "years of service" you mean "years since installed", then you can alter that by modifying conf_global.php file. conf_global.php should be in your suite web root. There should be, and if it's not just add following: $INFO['board_start'] = '1599604121'; Note that number is UNIX timestamp. You can use this site to convert between human readable date and UNIX timestamp. This is tested on Invision Community Suite 4.4.x so I don't know if that is going to work with 4.5.x. In any case, should not cause any downtime. even if unsupported.

Hi @Cookie Monster. How much is the limit? I've recently encountered the same message after just 3 downloads. Is it that low?

Just to add something that was not mentioned; Free domains are usually way-to-go for malware and scam websites, as these often get blacklisted, so they can be easily republished on new domain for no cost. For reasons above, reputation of free domains is non-existent. That does impact site ranking, and also repel some visitors (eg. myself).

When it comes to advanced technical stuff, easiest solution is not to use Windows at all. On Linux, when localisation doesn't work, culprit is usually missing locale on the system, and single command fixes it. Have you tried installing German locale on Windows? My general advice is to save yourself a trouble and considering moving to Linux if possible. EDIT: Sorry, I just noticed I awoke really old topic.

Considering that IPS is doing really good job patching all security issues promptly, and WebFlake is delivering new versions quickly, as long as you keep your installation up to date, have sane number of addons and chose them wisely, you should have no problems. Now, don't just relax; everything else is on you. Don't use weak passwords nor allow other staff members to do so. Keep your computer secure. Keep your hosting/server/cluster secure. Etc etc. If technical side is fully secure, most vulnerable point is human error, so chose your staff wisely.

Depends of what you're planning to use it for. BTC is currently very volatile, which could bring profit if you trade it. ETH is good choice too, but not as volatile. Easier to start with. XLM is pretty cheap to buy, so if you want to invest, it might be worthy choice. At the moment all 3 are in bullrun and good for hodl.

IPS is easily recognizable. Just by coming to the site you get that feel. Looking and the site HTML reveals many IPS specific classes and code.

I believe that you're having issues with random 500 errors because of your server/environment configuration. I use IPB for 8 years, and it's rock solid, stable. Despite the fact that scalability can be an issue (docker support, etc).

Welcome Andrew!

The guy is complete imbecile. Doing what he does in name of "revenge", but coming all the way to Islamic state level and making f*cking massacre. Hey, yes, Islamic state killed a lot of our people, but it's not the fault of Muslims, but fu*cking extremist imbeciles like himself. My heart go to the victims, families and everyone affected. I'm so so sorry. I know words mean nothing to soothe your pain. I wish I could do better.

I have a cat called Iris. She is almost 3 years old. I'm looking forward getting chinchilla as well, hopefully they'll get a long. ?

I would recommend using docker. There is ready-for-use docker image for redis. Once you spin up the container, you'll get IP address and then it's really easy to configure IPS. Make sure to use static IP for your docker container, so it will not change and leave your site broken. If you're new to docker, I would recommend usage of this docker management GUI tool. Installation is simple. How to install docker on CentOS: https://docs.docker.com/install/linux/docker-ce/centos/

That is an amazing policy @Davlin. Well done.