Dotnetpanel Forums

Oooooh...thank you Fedor for looking into this! Very exciting.

At this stage of the game, for us, the ability to provide scripting support and ColdFusion DSNs.

This would be a great start! As time moves on, CF Sandbox Security.

We're running CF v8 but I assume minimum support would start at CFMX (v6) since there still seems to be quite a bit of installs with v6.

I belive if CF v8 is supported, the administrative API's you would be tapping into is backwards compatible to v7 (but  don't quote me on this).

Thank you once again Fedor for addressing us CF hosters!

Feodor Fitsner:

OK, could you please say what a minimum should be implemented to say "ColdFusion is supported"?

The ability to set up coldfusion database dsn connections within the control panel for the supported databases would be the bare minimum. 

The option to enable/disable coldfusion on accounts would be nice but most people who provide coldfusion hosting provide it with all account levels (at least I do).

The lack of coldfusion support in DNP is the main/only reason I am not considering using it.

Adding or removing cf from an account is a must.  We'd be willing to invest in dotnetpanel if it just had that ability.  Thats said, DSN connections is pretty important. 

 Feodor,

Thanks for taking the time to peek at this.

 

At a minimum it should support automated sandboxing of sites, assignment of a specific number of datasources, allow the user to configure datasources, allow the user to review their log files. It should also allow the system admin to determine which clients can access what tags, like cfobject, cffile, etc

 Can I just ask if CF MX7 is now supported or an ETA?  This is a major part of our business and is currently stopping us moving from Helm...

I talked to sales and they would not commit to anything. Including future support for CF. Its a shame because we have seen more growth in CF hosting this year than any other language.

 Lack of ColdFusion support is the only thing stopping us moving a 10 server network to DNP from Helm.  DNP - You are missing a trick here...

renhack:

I talked to sales and they would not commit to anything. Including future support for CF. Its a shame because we have seen more growth in CF hosting this year than any other language.

I wonder why this would be the case? There are quite a few ColdFusion hosting companies out there that could really benefit from DNP (including us) and would be a great market for SAAS.

I was quite excited to see v2.6 of DNP come out but was a bit disappointed to see the continued lack of support for ColdFusion.

I do hope that they might reconsider agressively supporting CF and tap into this market. From what I've observed, it's one of the primary reasons why many HELM users won't migrate to DNP.

That's really very bad news :(

75% of our clients are using ColdFusion  and they use HELM to create DSN etc. on daily basis. 

If you could just give options to enable / disable ColdFusion for sites and add ColdFusin DSN than it is more than enough and I don't think it should take too much time. I was about to buy licenses for DNP but after reading this thread, I have left no options :(

xuser:

If you could just give options to enable / disable ColdFusion for sites and add ColdFusin DSN than it is more than enough ....

 At this stage of the game, I would be happy with just that....enable / disable ColdFusion Scripting. I think that just that feature would encourage a lot of migrations from HELM. I have to admit, it didn't stop me since I didn't have a lot of people using HELM. I was waiting for it to stabilize which never happend.

Yeah. I dont get it. How hard is it to just execute the following?

cf_root/runtime/bin/wsconfig.exe -server coldfusion -ws iis -site "web31" -coldfusion -v

Scripting enabled. Voila.

There's a webservice for adding DSN's built into cf. This stuff isn't rocket science.

 

I just spent thousands of dollars (yet again)  to renew plesk SUS's.

The process of enabling scripting for CF is quite simple but I believe there's quite a bit of development necessary to "manage" it as a resource (from any application).

I'm not too concerned about development timelines...as long as it's part of the plan of implementation.

I suppose that's my biggest question...will it be supported?

I don't think were talking about sandbox support yet. Just the ability to turn it on and off and some DSN support. This is the same implementation most of the other control panels are using.

COLDFUSION!!!!!!! seriously... why is this so hard to implement? There is an API for this provided by adobe. At least get the ability to add or remove coldfusion dll's in IIS.

Application Extensions needed.

Limit Verbs to 3, Script Engine enabled

.cfr (D:\ColdFusion8\runtime\lib\wsconfig\jrun_iis6.dll)
.cfswf (D:\ColdFusion8\runtime\lib\wsconfig\jrun_iis6.dll)
.jsp (D:\ColdFusion8\runtime\lib\wsconfig\jrun_iis6.dll)
.jws (D:\ColdFusion8\runtime\lib\wsconfig\jrun_iis6.dll)
.mxml (D:\ColdFusion8\runtime\lib\wsconfig\jrun_iis6.dll)

Wildcard application map
D:\ColdFusion8\runtime\lib\wsconfig\2\jrun_iis6_wildcard.dll