the full backward compatibility is provided. As a general rule of thumb, encoded files could be processed on PHP versions that are equal to and higher than the source Encoder language, i.e. When selecting a particular engine, you need to consider it’s compatibility with ionCube Encoder version your scripts were initially converted with. Here, application server choice depends only on your preferences (since both Apache and NGINX are supported), whilst a little more attention should be paid to the PHP versions list. First of all, let’s ensure you have a proper PHP environment for processing your protected code with ionCube Loader.įor that, launch the environment topology wizard (by clicking either New Environment button at the dashboard top or Change environment topology icon next to the existing one) and switch to PHP tab. So, log in to the Jelastic dashboard with your credentials and follow the instruction how to start operating encoded scripts in a matter of minutes. Thus, to enable executing secured PHP source code without struggling on manual server configurations, the Jelastic Cloud provides dedicated lightweight ionCube Loader add-on for one-click installation. Whilst encoding shouldn’t be a big problem for the majority of developers, running such protected application can become a real point of concern for an average user, since often it requires the involvement of some auxiliary modules and libraries. Being PHP-oriented, ionCube provides two correlated tools – Encoder to compile PHP files into bytecode and Loader, which handles execution of such encoded files. Today we’ll talk about ionCube - one of the most popular and widely used solutions to prevent unauthorized use. Encoding application sources is a common practice when it comes to protecting and/or licensing your application source code.
0 kommentar(er)
