Open Journal Systems (OJS) is open-source software for running academic journals online: authors submit papers, reviewers assess them, editors publish issues and finished articles go live as open-access PDFs. Many university and research institute journals in Uzbekistan run on OJS. The software is free, but stable operation and correct indexing depend on choosing and configuring hosting properly.
What OJS needs from hosting
OJS is written in PHP and works with MySQL, MariaDB or PostgreSQL. Requirements differ by major version: the 3.3 branch ran on older PHP, while 3.4 and later need the PHP 8 line, so check the official documentation before installing or upgrading. Typical extensions are mbstring, xml, intl, curl, zip, gd and the database driver. Editorial work itself is light; most load comes from readers, search engines and bots crawling article pages and PDFs. A small or medium journal is fine on well-tuned shared hosting, while a publisher running dozens of journals on one server is better off with a VPS.
Keep the files directory outside the web root
OJS stores manuscripts, reviews and published files in a separate directory that must not be reachable from a browser, or unreviewed manuscripts and reviewer comments could leak. The path is set during installation and kept in config.inc.php, along with the journal address and clean URLs, which need Apache's rewrite module and a matching .htaccess rule:
[general]
base_url = "https://journal.example.uz"
restful_urls = On
[files]
files_dir = /var/www/ojs_files
[security]
force_ssl = On
Turn on force_ssl only once the certificate is installed and the site opens over https, otherwise the login page can get stuck in a redirect loop.
Disk space and the article archive
Disk usage grows mainly through PDFs, and every article is kept in several versions: the first manuscript, the revised text and the final galley. A journal publishing four issues a year with ten to fifteen papers each builds up a noticeable archive within a few years, especially in medicine or engineering where papers are full of figures. A full disk means authors get upload errors, so size your plan for a year or two of growth and watch disk usage in the panel.
Scheduled tasks and email
Review reminders, usage statistics processing and cleanup run through tools/runScheduledTasks.php. A server cron job, added in the ISPmanager scheduler, is the reliable way to run it:
0 * * * * /usr/bin/php /var/www/journal.example.uz/tools/runScheduledTasks.php > /dev/null 2>&1
All communication with authors and reviewers goes by email, and messages sent through PHP's plain mail() often land in spam. Enable SMTP in the [email] section of config.inc.php, send from a real mailbox on the journal's domain and set up SPF and DKIM records.
Indexing: Google Scholar and OAI-PMH
OJS adds the meta tags scholarly search engines look for and exposes metadata to aggregators through OAI-PMH. That only works if the site is reliably available, PDFs are not blocked and URLs stay stable; when moving to a new domain or URL structure, add 301 redirects from old addresses. Be careful with bot blocking: a university journal in Samarkand that blocks every bot because the site got slow may find its new articles missing from search a few months later. Restrict only abusive crawlers.
Backups and the upgrade routine
Upgrades change the database schema, so before each one save the code, the files directory and the database. sayt.uz hosting keeps automatic backups, but a manual copy before a major upgrade is still worth having:
mysqldump --single-transaction -u ojs_user -p ojs_db > ojs_db_$(date +%F).sql
tar -czf ojs_files_$(date +%F).tar.gz /var/www/ojs_files
Test the upgrade on a copy of the journal on a separate subdomain first, check plugins and the theme, then upgrade the live site. Outdated OJS versions are an easy target, so do not postpone security fixes.