- Posts: 846
- Thank you received: 92
use licence in local ?
13 years 5 months ago - 13 years 5 months ago #100149
by lionel75
use licence in local ? was created by lionel75
when i have a look to my hikashop account Isee ### Subscription attached to http://... ####
Can we install the licence in local intranet web server ( debug) ?.
Since my desktop is behind the adsl router Does my ADSL box must have an ip fix ? May i need to redirect my local internal ip to the router ?
Does it make no difference for hikashop if i switch the same joomla root directory beetween IIS or apache using different port ?
Thank's
Can we install the licence in local intranet web server ( debug) ?.
Since my desktop is behind the adsl router Does my ADSL box must have an ip fix ? May i need to redirect my local internal ip to the router ?
Does it make no difference for hikashop if i switch the same joomla root directory beetween IIS or apache using different port ?
Thank's
Last edit: 13 years 5 months ago by lionel75.
Please Log in or Create an account to join the conversation.
13 years 5 months ago #100182
by Jerome
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Replied by Jerome on topic use licence in local ?
Hi,
You can install HikaShop on a debug server without any problem.
The website where the license is attached is for the services we provide (updates, cron, support, etc).
If your website do not have a public url it is not a problem but you could use the the Joomla auto-updater for HikaShop and we couldn't provide the cron service.
Regards,
You can install HikaShop on a debug server without any problem.
The website where the license is attached is for the services we provide (updates, cron, support, etc).
If your website do not have a public url it is not a problem but you could use the the Joomla auto-updater for HikaShop and we couldn't provide the cron service.
Regards,
Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.
Please Log in or Create an account to join the conversation.
Time to create page: 0.218 seconds