Does acumatica has console version of installer? - acumatica

I want to create docker image of Acumatica. For this purpose I need console version of installer of Acumatica. Does Acumatica has console version of installer?

Not Sure this is exactly what you want, but there are instruction on how to use the Command Line tool to install and do maintenance of an Acumatica Website in the S100 course and on the Acumatica Help Website
It use the ac.exe with parameter do deploy an new installation.
The complete list of parameters can be found in both of the place mentioned before.

Related

Add side-bar in JHipster application

I want to insert a sidebar into the body of the element body in a JHipster application.
Is there a command that can help me?
There is no module available for converting JHipster's nav bar into a sidebar. JHipster generates the code, but you will need to customize it yourself depending on your requirements.
You can see available JHipster commands by running jhipster --help, and the command's options by running jhipster service --help (example showing the service subgenerator options).
JHispter also offers modules, which extend JHipster's functionality with new commands. The full list can be viewed in the JHipster Module Marketplace. No module offers a sidebar option at this point in time.

I'm a little confused about install OpenNTF Domino API

I need to use FileSilo Project that require OpenNTF Domino API.
But I have some problem to install this fantastic tool.
I have follow the suggest of this blogger
So I have follow this step:
Download the last version of OpenNTF Domino API
Unzip the file
Import Database updateserver.nsf from the zip, into my UpdateSite (se the image)
Install in my Designer from my updatesite.nsf
restart HTTP task
Now I have this problems:
In my Domino Console after I restart the HTTP I see some error
In my Domino Designer I see many error
When I open FileSilo on the web I see another error
Soo am I doing wrong ?
UPDATED
After the #Paul Stephen Withers comment.. I've installed the correct library (updatedesigner.nsf) into my Domino Designer...now FileSilo app show only this two error:
The message on the Domino console about not finding a logging configuration file is fine. It's not an error, just information being logged out to the default log location. That just allows you to use a separate logging config file, outside of the API itself.
It looks like the key issue is the Designer install. Looking at the version number, I think you've installed the plugin from the server Update Site database into Designer.
The separate update site for Designer - updateDesigner.nsf - was needed in order to get typeahead but ensure the plugin for the server was as small as possible.
Because of the different packaging methods, you will need to uninstall from Application management before installing the newer version from updateDesigner.nsf. Note that a problem with DateTime class was identified which is fixed in "OpenNTF Domino API RC2.1.zip".
It looks like the errors on the web may be because it's been built in Designer.
I recently did a video on installing various plugins for your server and designer. Near the end I showed the install of the OpenNTF Domino API. That might be helpful to you.
http://www.notesin9.com/2014/10/21/notesin9-161-designer-plugins/

View node.js source code on local machine

I have node.js installed on my mac. However I am not able to find the the source code.
The 'node' binary file is located /usr/local/bin however since its binary, I can not view it.
For example I want to see internal of console.log function.
On joyent github I can see the code but I want see it when I am offline via some editor like webstorm.
https://github.com/joyent/node/tree/master/lib
Can someone please help.
Thanks
Locally you have Node.js installed. To make your life easier, Node.js developers have already compiled Source into runnable Application.
Because you downloaded already compiled Node.js (that is OK, and sensible), you need to also download source-code if you want to access it offline.
Downloading source-code is just as easy, you can grab the latest code available at the same location as you specified: https://github.com/joyent/node. Look for "Download ZIP" button on the bottom right.
In case of webstorm this link will help - http://www.jetbrains.com/webstorm/webhelp/node-js.html - see "Configuring Node core module sources"

How do I configure Nwazet Commerce with Orchard 1.7.2?

I'm trying to install Nwazet Commerce with Orchard 1.7.2.
Suddenly, nothing happens. No new menus, no errors, nothing in the logs, nothing. It is just as if I hadn't installed it.
Before you ask... yes I've enabled the modules.
I can't find even a single scrap of documentation. What is supposed to happen? I would expect to see some extra menus or something on my dashboard or perhaps some extra content types, but there's nothing.
Help please :-|
You can't. The current version in the source repository is only compatible with the 1.x branch. See https://bitbucket.org/bleroy/nwazet.commerce/issue/20/update-to-17
I have a version for 1.7.2 unfortunately I don't know what fork it was from so I don't know what bugs or issues were included.
I found it in my saved orchard files and tested quickly you will get the admin options.
Download available here

Script Create Package for Windows Store apps

I am maintaining a set of eleven Windows Store apps. I would like to automate the "Create Package" task, which I am currently doing through the wizard in Visual Studio, in order to produce test packages (signed with my test certificate).
Is there a way to script this task? I was thinking probably using MSBuild or PowerShell, my goal is to have a single script to run that would generate all my app packages and copy them all to a given target directory.
I found some documentation about using the wizard on MSDN, but nothing about scripting the task.
Any ideas?! Thanks.
MSBuild will create app packages for you, in the AppPackages folder. You can also do it manually using MakeAppx, but I've found it to be a bit more cumbersome.
Some things to note: There is a build target called Publish you should use (/t:Publish) when making the actual packages. You should look into the different command-line switches, such as DebugSymbols.
You'll likely want to use the 32-bit MSBuild, as I've had issues with the 64-bit and things like the Multilingual App Toolkit. Also in regards to the MApp Toolkit, make sure you do a full rebuild before building your app package. If an entry is not in a given language and is in another, the entry for the secondary language will be used, so you can end up with multiple languages all popping up on the same page.
Hope this helps and happy coding!

Resources