Quote from: talpan on February 12, 2012, 09:40:37 AM

Hello,

I want to look a bit at the source may be contribute something to the community but I can't figure out,
how to install/upload this to dnn 6.0.
Sorry but I haven't any experience with dnn, but the first look is impresssive

.

Any help is appreciated

kind regards, talpan

Hi Talpan,

Sorry for the late bump, I just committed the latest version with a DNN 6 compatible extension.

Are you still interested in looking up the source code?
Here's the procedure to get started:

Install DotNetNuke 6
Download the latest dnnbitcoin source from the codeplex site
In the PortalKeeper folder, you'll find 2 extension Zips to be installed within DNN. The Shared extensions must be installed first. To install a DNN extension, log as a super user and move to the Host/Extensions, Manage Extensions/Install Extension Wizard. Then it's all about checkbox and validation buttons until an App restart
Once both extensions installed (they should appear in the list), create a dedicated page (Top Panel/Pages/Add Page), and within that page, instantiate the PortalKeeper module (Top Panel/Modules/Select with Categories=All/Add Module)
Once the module is displaying, click "Register components" (it will update your web.config file with dedicated parameters)
The module now displays your main configuration form. There is a default Firewall tab, move to the Scheduler Bots tabs
The scheduled farm is disabled by default. You won't want to enable it directly, only after having done prior tests through on-demand runs with the "Run Forced Bot" button
The farm contains a series of "Master" bots, which can optionally be transformed into "User bots". User Bots are copies of master bots where authorized site users can have their own instance of a selection of the parameters. Enabling a user bot usually comes in pair with defining default parameters in the master's definition and disabling the master instance. This is the case with the existing Bitcoin bots.
The default configuration features 2 trading bots (MtGox and CryptoXChange APIs) and 3 corresponding user bots (2 distinct types of strategies for MtGox and one for CryptoXChange). You'll have to choose and enable a user bot, and include the master bot in the forced bots selection.
Next step is to create a dedicated portal user, distinct from the super-user, and to configure the user bot display for such a user.
This is done in the module's Manage/Settings page. In the permission tab, you'll want to grant "Edit" permission to the target user role (or simply "registered users" if you don't care about authorization roles). In the "Portal Keeper Settings" tab, check "Assign User Bot" and choose the user bot to display for this specific module instance (Super users always get the global configuration display, where as regular users get the display configured here for this specific module instance)
If you come back as a regular user (you can use distinct browsers to keep both sessions), you'll be familiar with the form, identical on dnnbitcoin, and you can save an instance of your parameters (don't forget to disable it on dnnbitcoin.aricie.com first if you plan on using the same Exchange account)
come back again as a super user to perform your tests. In order to get detailed logs, move to admin/event viewer/Manage/Edit log settings/Add Log Setting/Type=Debug Info (this is the log type used by the module and it is disabled on a default DNN installation). Event logs will be reported in the admin/event viewer page. You can enable logging for a bot in its "technical settings" tab.
Click the "Run Forced bots" button. If everything went fine, you should see the result on the exchange platform, in the event viewer, and in your user's bot history
Once you get the bot running, you can configure the scheduler. DNN comes with a event scheduler, which has 2 modes: timer or request (default). You'll want to switch to timer mode (Host/Host Settings) or to enable the bot that pings the site on the desired frequency in order to get a consistant schedule. The scheduled bot farm is embedded into a single DNN Scheduled task (Host/Schedule), but it maintains its own additional frequency as well as each individual bot (Technical Settings).
Finally about the code itself. A bots is made of a XML definition and related .Net libraries declared and consumed within the definition. There are 2 dlls for the trading material: You can build the related VB.Net and C# projects from the source and replace the original dlls in the bin folder to start debugging. You can also edit the definition within the configuration form, and Export/Imports files are located at the root of your site's directory (~/Portals/0/)

Well I think that's about it.
Let me know if you have any additional question.
As for me, I'm still to upgrade the dnnbitcoin website to dnn 6 and install the new CryptoXChange bot.

Regards,

Jesse