Search the Community

Morty is getting upgraded! Our fastest and most up-to-date server is getting even faster and even more up-to-date. We will be starting a major upgrade soon, and wanted to let you know what to expect if you're on the Morty plan. What is changing: PHP: All of the versions of PHP currently available on Morty will still be available after the upgrade. Node.js: We are adding versions 25 and 24. All other versions of Node.js currently available on Morty will remain available after the upgrade. Python: We are adding version 3.14. Version 3.9 will remain the same. Version 3.12 will be removed. Django: We are adding version 6.0.4 running on Python 3.14. We are removing version 6.0.3 running on Python 3.12. Flask: We are adding version 3.1.3 running on Python 3.14. We are removing version 3.0.3 running on Python 3.12. Unfortunately, we don't have a way of tracking which accounts are using which Python modules right now. So if you're using any modules, please take a look at https://morty2-info.heliohost.org/pyinfo/info3.14.py as soon as possible, and request any modules that you'll need that aren't already available. In the future, we plan to add a system for tracking which modules each account needs, allowing us to pre-install them before an account is moved. For now, you will need to re-request them. You can reply to this email or click the contact support button below to let us know if any modules you need are missing. Another thing to keep in mind during an upgrade like this is that your IP address will be changing. If you use our nameservers, ns1.heliohost.org and ns2.heliohost.org, your DNS records will be updated to the new values for you. If you use external DNS, such as Cloudflare, you'll need to manually update your DNS records yourself. You will receive an email with the correct values when it's time to change them. If you don't want downtime due to incorrect DNS records, you could temporarily use our DNS until you're moved, and then go back to the external DNS afterwards. You will receive an email when your account begins its migration to the new hardware, and a second email when the move has completed. We are taking volunteers to be the first ones to experience the upgraded speed and features, so if you're ready to move, let us know. If you need a little more time to make sure your website is ready for the upgrade, let us know, and we can move you to the end of the list too. If we don't hear from your we will assume you're ready to move now. Let us know if you have any questions.

tldr; I'd like to add an `.htaccess` rule to rewrite `*.phps` URLs to their actual `.php` source document, but instruct FastCGI to syntax highlight and render the source file as HTML instead of interpreting it. Some due diligence: I searched the forums for: "phps" (Old thread from 2009 about bypassing apache/suPHP configs and highlighting via `RewriteRule /highlight.php?file=$1`.) "fastcgi" (Nothing obviously php/fastcgi/htaccess related.) "fcgi" (Nothing obviously php/fastcgi/htaccess related.) "handler" (There's an old thread about telling apache to process `.pro` files as PHP.) "htaccess" (Nothing obviously php/fastcgi/htaccess related.) etc. I searched the wiki. I've done loads of Google searches similar to the above, and read dozens of StackOverflow QAs. I've browsed the Plesk docs, but they don't get to the level of config file detail. I've tried adding a `SetHandler fcgid-script` (among many others) in my `.htaccess`. I've experimented with a bunch of stuff in my Heliohost Marty space. General info: Morty username: beporter Site: https://gravatar.redirect.channel PHP file URL: https://gravatar.redirect.channel/gravatarizer.php (On its own, configured to bounce invalid requests back to the homepage.) Desired .phps URL: https://gravatar.redirect.channel/gravatarizer.phps (should render html version of the source code for the `.php` version of the same filename.) I tried symlinking this in git, but: the Plesk logs say I can't use `<Directory>` which means I can't use `Options FollowSymlinks` either. According to the Plesk file browser, git doesn't push the symlink over SFTP, at least not with the Github Action I've been using. Example non-functional `.htaccess` rules: # Allow PHP source code to render as text for inspection AddType application/x-httpd-php-source .phps # RewriteRule ^(.+\.php)s$ $1 [H=application/x-httpd-php-source] # --or-- # RewriteRule ^(.+\.php)s$ $1 [H=php-script] # Allow examining .phps files. # <FilesMatch "\.phps$"> # SetHandler application/x-httpd-php-source # </FilesMatch> If this were `mod_php` in Apache, I suspect that first commented-out RewriteRule would have been sufficient. But since PHP files are passed through to FasgCGI, it seems like that Apache handler isn't recognized or responding. What I can't find is documentation on how Heliohost has named its PHP handlers. I found a support page about using the plesk cli tool, but obviously I can't run that myself. It's totally fine if this is outside the realm of possibility, but since this whole single-page-site is meant to be a learning experience, it'd be nice to get this working in the`.htaccess`, if possible. Thanks for your time!

Could you please install the MS SQL Server extensions for PHP? The files needed are: php_pdo_sqlsrv_xx_ts.dll and php_sqlsrv_xx_ts.dll (where xx represents your PHP version) into your PHP's ext directory. Thanks

Can I change the plan to Morty?Hi

Just a quick question. The new Morty server seems very promising. However I am wondering how much would it cost to scale and is it auto-scaling (scale and charge more automatically)?