Download the application package from CodeCanyon, unzip it and upload the contents to the web root folder of your domain (on shared hosting environments the web root folder is usually named public_html).
If you install the application on a VPS or dedicated server please ensure that the web server (usually www-data user) has write permissions to the following folders:
The easiest way to ensure proper permission is to make www-data user owner of the above folders (and files recursively). It can be done with the following shell commands:
>_ cd /var/www/myproject >_ chown www-data public_html >_ cd public_html >_ chown www-data public >_ chown -R www-data storage bootstrap/cache
Please also check that URL rewrite is enabled and custom .htaccess files are allowed (AllowOverride directive set to All) in the Apache web server configuration. You can check the latter by inspecting your virtual host config file (e.g. /etc/apache2/sites-enabled/yourwebsite.conf) or the main Apache config (/etc/apache2/apache2.conf). It should contain a block similar to this:
<Directory /var/www/myproject/public_html/>
Options FollowSymLinks MultiViews
AllowOverride All
Require all granted
Order allow,deny
allow from all
</Directory>
Please note that you need to restart the Apache service after making configuration changes.
Create a MySQL (or MariaDB) database on your server, as well as a database user who has all privileges for accessing and modifying it.
Run the application installation script by accessing the following URL in a web browser: http://yourwebsite.com/install.php (substitute yourwebsite.com with your actual domain name). Follow the on-screen setup instructions to complete the installation.
Please make sure to add a system cron job in order to automatically execute scheduled tasks (such as bots). The system cron job parameters are provided on the last step of installation and on the Maintenance page in the backend.
It happens when necessary .htaccess files are either missing (there should be 2 .htaccess files - one in the application root folder and another in public sub folder) or not allowed by the Apache web server.
Please create a symbolic link (symlink) from public/storage to storage/app/public folder. Normally, it should be created automatically during installation, but on some hosts automatic creation is disabled, in which case the symlink should be added manually.
If you have SSH access you can create the symlink by navigating to the web root folder of your domain and running the following command:
>_ php artisan storage:link
If you do not have SSH access please ask your hosting support to create the symlink for you.
The following error is displayed in the browser console: Mixed content: The page at ... was loaded over HTTPS, but requested an insecure resource.
If you are using Cloudflare please check that Automatic HTTPS Rewrites are enabled in the Cloudflare settings. Please also check that you added a wildcard redirect from HTTP to HTTPS version of your website. If this still doesn't help please edit .env file and add the following line:
FORCE_SSL=1
Try to add the following line to .env file:
SESSION_DOMAIN=yourdomain.comClear cache on the maintenance page after that.
All games results are completely random, you can't manually set the win rate or otherwise affect the roll process. However, you can adjust the Slots game settings to make it more difficult for a user to win (or to be more precise - make it more difficult to have the positive net result, because winning 5 on a 20 credits bet is not actually a win). You can:
Chat uses Pusher to function. In order to enable chat functionality you need to create a free account at pusher.com, create a new channels app and obtain its credentials (such as app ID, key, secret and cluster). After that input these credentials in the application settings in the backend (under Integration tab). The chat should then start working automatically.
To enable authentication (using OAuth) with one of the supported social providers (Facebook, Twitter, Google, LinkedIn, Yahoo, Coinbase, Steem) complete the following steps.
Here is how the app settings page looks like on Facebook for developers.
Things to note:
To override the default website logo create an image file named logo-udf.png and put it to public/images folder. This way you will be able to keep your custom logo during future updates.
The OG image is used when sharing website content on social media. To override the default OG image create an image file named og-image-udf.jpg and put it to public/images folder. This way you will be able to keep your custom OG image during future updates.
The website favicon files are located in public/images/favicon folder. You can just overwrite the original files with your custom ones.
You can change translation strings for any language by editing JSON translation files in resources/lang folder.
To change the default text strings it's not necessary to modify the application code. All you need to do is to create a JSON translation file called en.json and put it in resources/lang folder. The file can be created as a copy from any other translation file, such as resources/lang/de.json for instance. In this translation file you need to keep only those text strings that you would like to override. The left side represents the original text string in English and the right side represents the overridden string. Example:
{
"Crypto Casino": "My custom casino name"
}
If you like to apply some custom CSS styles create a file called style-udf.css inside public/css folder and put your styles there. This will help you to preserve your custom styles after upgrading the app to a new version.
Sometimes you might want to override default header, footer and front page templates. It's better than just changing the template files directly, because in this case you will not lose your customizations when upgrading the application.
To override these templates create the following files and edit them the way you like:
Suppose you want to add a new static text page, which is available at http://yourwebsite.com/page/my-text-page. To do so create a new template file named my-text-page.blade.php in resources/views/frontend/pages/static folder. You can copy the default page structure from other static pages templates in this folder and then modify it as needed. After the template is created the static page will automatically become available.
To disable the maintenance mode when you don't have access to the backend delete the following file: storage/framework/down.
The application settings will be preserved, but please note that if you changed any of the application files you will have to re-apply customizations manually.
Please note that support can only be provided during the application support period. 6 months of free support are provided with your purchase. Should you need support outside of this period you will need to renew it. How to extend / renew the app support?
To get technical support please submit a new ticket at https://support.financialplugins.com. If you see an application error please do the following before submitting a support request:
In case the issue is difficult to trace our support team can request SSH / cPanel access to your server and / or website admin access.
© Built by FinancialPlugins.com