I am planning to make a script but I have a question which is very important before beginning. On the main website, domain.com there will be the info of using the script. Everybody can register and use the script so it will run on sub.domain.com. But I also want to make it possible that people can pay for using the script on a chosen .com. Now what is the best way to do this. Like if there is an update there is no possibility I have to change the files on every hosting manually. (In no way the users can get the source of their script, they can only use there registered version)
So you have functionality on your site (as you dont say what it is lets say its a tax calculator) and you want other people to be able to add the same functionality to their site without you having to give them the source code. One option is to create a webservice and so their site passes you their login credentials along with the data, your site runs the function and returns to them the results. The advantages of this is that they can then style things exactly how they want, they can use it with any programming language not just the one you like to use and if you change the logic in the function there is no need to redistribute it. The disadvantages are that it will be more complex for them to integrate, you cannot enforce them showing their using your system and it will be more complex for them to update if you change the input or output parameters The other option is to simply encrypt your source code and distribute it as a solution to run on their servers. The advantages/ disadvantages are more or less the reverse of the other solution but you would be sensible to include a remote kill code for each license if your wanting to enforce continued subscription etc.
The script actually is comparable with bux websites like the sites from buxhost.com The main website is information that people can use. when user registers he gets a subdomain like user.bux.com and there evereybody can use his bux website and his users and himself can earn money. This is easy because I can set make one script and every subdomain can use this script with the right settings. But now is the problem how can I fix this when users can get their own .com domain. Won't it be too slow if every customer will use the same database, script and host?
How slow it would be will depend on the volumes of data, efficiency of the programming and the specification of the servers/ connections.
That's true, but will it be possible to run a script on example.com and just access this script from every other .com domain with the right settings?
I had this same problem when I developed a eCommerce platform, where I wanted to continually give my clients upgrades as they arrived as part of the initial agreement. The best and fastest way I found of achieving this, is to create a template of what you want to include, which contains information that will never change (hopefully) and then include the rest from a remote database. Every client on the system updates as soon as you have updated your database. You can even include some kind of script initially on each client, where when the page is loaded, check if there is an update from comparing a version number that will be stored on the client side, and then another stored on a database on the remove server. If they dont match then, get the user to include the update. This include could always been stored locally by the client too.
To be honest it all depends on what you are really wanting to achieve, the short answer is yes, you can. How its best to do it depends on what exactly it is that the site/ function is.
Thanks a lot, this helped me out a lot. Indeed and this is my question the site function is really close to compare to the bux system I described.
I don't know what the "bux" system is and don't really have the time to investigate websites to try and guess which functionality you are wanting to replicate.