I want to load a module which is stored in a database under the modules named as "/modules/mylib.xqy".
Currently, in the document requiring these module, I am writing
import module namespace rb2lib="http://example.com/modules/lib" at "/modules/mylib.xqy";
Unfortunately, this expression makes a lookup on the filesystem and not on my database.
Is there a way loading modules stored in database?
Thanks in advance!
Yes, change the application server configuration's modules setting from (file system) to the Modules database (or any database). The XQuery module must be stored in that database, and its URI must be the app server's module root plus the import location. For example, you could set your module root to / and store the module at /modules/mylib.xqy.
This is controlled by a setting on the administrative console. Look at your App Server configuration for the "modules" config item. It is currently set to file system, right? Change it to the database that has your modules.
Related
I am trying to use an environment variable in the odoo.conf
file to specify the path where the logs are stored.
So far I have tried:
logfile = ${test.rueda}/odoo.log
But it does not work.
Is there any way to achieve this?
The Odoo configuration files do not support access to environment variables.
I can think of 2 possible approaches:
Use relative paths. The file names in the configuration are relative to the working directory of the Odoo server process. Start the Odoo server in different directories, one for every purpose, and keep the same structure relative to that.
Use environment variables in the command line. When starting the Odoo server, any configuration option can be passed using -- (2 dash signs) as a prefix. In the start script, you can then use environment variables as in any other shell script.
See https://www.odoo.com/documentation/11.0/reference/cmdline.html for details.
For referencing files or path:
When i work without external disk (where i can find my datadir):
i use in odoo config file data_dir = my_absolute_path_in_my_local_disk.
This path have a symbolic redirection to where is my local physical location of my local data directory
When my external disk come back, i change the symbolic link:
my_absolute_path_in_my_local_disk -> my_external_disk_..._data
I'm an experienced (ASP.NET|Java|PHP|web) developer, new to DotNetNuke.
Currently I'm following a blog tutorial to try to get an Angular module up-and-running in my local installation of DNN 7 (http://www.bitboxx.net/Blog/Post/505/DNN-module-development-with-AngularJS-Part-1#)
My environment: Windows 2012 Server R2, SQL Server 2016 Express, Visual Studio 2015 and DNN 7 on IIS 8.
DNN nuke runs fine.
I installed the downloaded module from the blog to my DNN. I'm having problems to run the HelloWorld example (at the bottom of the 2nd part of the course).
Through some trial-and-error I found out this has to do with the [SupportedModules] attribute on the controller.
Without this attribute it runs fine, but with the attribute it won't.
How does DNN determine the name of the module? The "installation" process was no more then unzipping the modules contents to the DesktopModules directory within my DNN directory (in inetput\wwwroot).
Do I need to install/configure the modules in Settings > Extensions?
Or am I missing some other point with regards to the DNN 7's security?
Thanks in advance for any help/thoughts!
Yes, you need to install the module through the Extensions mechanism in DNN. This will register the module so DNN is aware of the module as well as make sure the files get copied to the right places, in accordance with the installation manifest (the .dnn file you should find inside that .zip file)
However, looking at the blog article you referenced, I don't see an actual installation zip file anywhere. The only download I found was for the project as a whole. You would need to package your compiled solution into an installable zip file (with a .dnn manifest file) or you need to manually register your extension from the Extensions page.
On that page you should click the "Create New Extension" button which will walk you through supplying details for the module. Choose Module as the Extension Type
Only a few of the items are required. The "Name" you use for the module will be the name you use in SupportedModules. It will also default your folder name (the folder in /DesktopModules) to the module name. Friendly Name, incidentally, is what will be displayed in menus and such.
Once you've created the module it should be registered with DNN. You will probably need to restart your AppPool and website for the change to take effect.
FYI, SupportedModules isn't strictly required. If you're building this for a client and not building this for distribution.
Hope this helps.
I am wondering if there is a module that gives the ability to install modules via an interface instead of copy a module files and create database tables manually and add it to config/main.php .
Is there any ? I mean something like what is in Joomla or Drupal?
As of now, I don't think there is something like this on Yii.
What we did for our projects, is this.
We created our module, that will automatically create / copy the files and the same time, add the configuration files.
While learning how to create Lua file output code with the support of LÖVE, I've always hated that LÖVE filesystem handler always saved the specific file somewhere in C:/Documents and Settings/...
How can I create a code that saves a file into a specific folder that I'd like to define (and maybe to change while running the application)?
The love.filesystem library doesn't let you do anything outside the sandbox. However, LÖVE doesn't disable Lua's built in io library, so you can use io.open to open files outside the sandbox and read/write them as normal, as well as other Lua functions like require and loadfile.
It also doesn't restrict loading of external modules, so you can (for example) require "lfs" to load LuaFileSystem and use that, if it is installed.
Background:
I have about 170 SSIS packages. A new requirement is that users from other workstations can run them from their command lines using dtexec.
Question:
To make this possible I'd like to set change the protection level to encrypt sensitive with password, and change the password in each package.
Is there a way to automate this?
It's not something I've tried personally, but you could potentially amend or add the property in the XML source of the packages using a global search and replace.
A much easier method is to use the built in package configuration functionality. Configure your package to look to load its configuration from a config file. Distribute the config file with the package(s). You'll have to decide on what technique to use for the package to find it's config file (this technique will be used on all dev workstations). I've typically used registry entry. You can also use system variables. From an execution stand point, you can pass in the name and location of the config file to dtexec.