RE: [coldbox:26251] Coldbox v4.3.0 - Modules error - Directory does not exist

Communities ColdBox HMVC
1

Do you have an appmapping locally? You shouldn’t need to change any of the convention folders to accommodate for the app mapping. ColdBox does that for you.

Happy Connecting. Sent from my Sprint Samsung Galaxy S® 5

2

Yes the same dev folder is used in local too.

The idea is to maintain a common configuration and multiple versions of code.

As an example

/coldbox/*
/config/*
/versions/v1/{handlers, views models modules}
/versions/v2/{handlers, views models modules}

/versions/v3/{handlers, views models modules}

/Application.cfc

The config will set which version based on database. I haven’t really explored on different ways to achieve that. May be this is not the best approach to take with coldbox?

Is this related to why coldbox sometimes cannot find a module that is inside the coldbox folder itself?

Thanks,
Aswin

3

I think you should probably look into external handler locations and/or modules for your purposes. I’d hate to guess what’s going on with your module errors since it sounds like you’re doing some funky stuff there I don’t quite follow. What is the purpose of the different versions? Is this a REST API or something?

https://www.ortussolutions.com/blog/rest2016-versioning-your-coldbox-rest-api-with-modules-runnable-example

Thanks!

~Brad

ColdBox/CommandBox Developer Advocate
Ortus Solutions, Corp

E-mail: brad@coldbox.org
ColdBox Platform: http://www.coldbox.org
Blog: http://www.codersrevolution.com

4

Hi Brad,

Thank you for the help. I change the code to use colbox app mapping and removed the conventions. Now everything seems to be loading correctly. I guess I was breaking something by messing around with the conventions.

At the time when it was crashing, the app mapping were not resolving. The moduleRegistry had the correct path to coldbox module but ExpandPath on the module name was not resolving to the correct folder.

Its not a REST app, versioning is so that some new features can be released to a customer A while customer B is still one old code base. Just the version name in database will change. All sites will be pointed to same root folder, the application will keep the domain.com/main/index path, and there is no need to configure IIS to the specific folders check for permission every time a new version is released. Unique application name space is maintained using the domain name.

Thanks,
Aswin