Change mimosa web package build directory - node.js

I am trying to change the directory of Mimosa's "dist" folder. It is currently set via the node package "mimosa-web-package", and there is a config file in there. However, I do not want this config to be overridden if I update my node modules.
I have looked on Mimosa's page to see if there is an option to change, however I cannot work out how they are linked.
Anybody encountered this issue?
Thanks!

Set this to whatever you want in your mimosa.config file:
webPackage.outPath: __dirname + "/nameOfBuildDir"

Looks like you found the answer, but hopefully this helps...
mimosa-web-package has its documentation on its GitHub page instead of the website because it isn't a "default" module that comes packaged with Mimosa. The config for mimosa-web-package is what controls that particular setting, and yep, its outPath that you want to change. It is set to dist by default.
webPackage.outPath: "nameOfBuildDir" should also work in the case you mention above.

Related

What is node_modules_bak?

I've got a folder in my project directory called 'node_modules_bak'. I don't know where it comes from or what it does. Google and StackOverflow do not provide any information about this name.
Does anyone know what it is and whether I can delete it safely?
It’s not a folder generated by node or npm or any well known tools.
It might be something generated internally by a script or even another developer wishing to backup the modules.
I would do a code search in all project files to see if the name comes up anywhere.
Like the other answer mentions, there are some tools that create this directory. It is not created by node or npm.
In my case it was https://github.com/siddharthkp/cost-of-modules/blob/0a009d670a4e4fcb185b29979b5f58668664da4b/src/helpers.js#L47-L49
/* Check if node modules exist and then backup */
let nodeModulesExist = fs.existsSync('node_modules')
if (nodeModulesExist) fs.copySync('node_modules', 'node_modules_bak')
There are a couple more of these on github when I search across all repos https://github.com/search?q=node_modules_bak+language%3AJavaScript&type=Code&ref=advsearch&l=JavaScript&l=

How do I edit files with Web IDE in Bluemix DevOps?

My ultimate goal is to simply edit the package.json file to add the momentjs library so I can access it my node red app running in bluemix, but my question is even more fundamental.
My setup:
I have a bluemix nodejs app running a simple node red app I created. I want to use the moment.js library to do some date math and understand I need to update the dependencies file in the package.json file.
Question:
When I go to my Bluemix console runtime screen for node.js I can see the package.json file and can click on it to see the contents, but can't edit. I have tried creating projects/Git and can't see this file. I can use CLI using CF and get to the file and view it but again I just don't know how to edit it.
I would really like to understand how I can see these files and edit/source code control them using the Web IDE and just can't figure it out. I do fundamentally understand source code control just don't understand how to set this all so I can specifically see this file.
Main goal is simply to update the package.json file in the app directory.
In your Bluemix Dashboard,click on your APP and in the APP Overview you will see ADD GIT BUTTON(top right corner).
Click on it and once you've added your project to GIT, you will get a GIT URL.
Go to that URL and click on EDIT CODE( you can update your package.json) and then commit the changes.

Running a github repository for Node Js - configure env

I'm quite new at Node and Git, I've been working on this repository for a couple of days and I'm not sure how to make it work. It tells me to configure some vars but I don't quite understand how to. Which file should have the actual LOGIN, PASSWORD, SLACK, etc.(Or should I just type them in the terminal)? What should I be typing in the Node Terminal?
Neither am I sure how to run the github files since every time I call it in the terminal it types "No local config found" or "Cannot find module"
I have no clue how to go on, so any help would be REALLY appreciated.
https://github.com/nicolsc/slack-sigfox-last-message
Create a file config.local.js and store the parameters inside. each existing parameter will override the defaults.
the files named config.*.local are also added to .gitignore which self-explain that those kind of files are configuration files.

How to configure Mailsac (a disposable email server)?

Has anybody set up Mailsac on a server (Linux and/or Windows)? On the Mailsac GitHub page it says just change config.js file. Does anybody have detailed instructions or an example of a config.js file?
I think you should use Ubuntu installation script as reference.
And looks like config file that you looking for is mailsac.conf

How do I add a project to CruiseControl.NET?

I am looking at the cruisecontrol web dashboard. I can see one farm and one server. However, I don't see any way to add a project?
Is this something I can do with the UI or do I need to edit the config file by hand?
You'll need to edit the ccnet.config file by hand (located within the CruiseControl directory) to add projects. There are some graphical tools to help you do this however you do get used to doing it by hand fairly quickly - just have the documentation near by!
Update: An example of one such tool is http://www.codeplex.com/ccnetconfig
You can use CCNETConfig to edit the config file through an UI although it doesn't support higher version > CruiseControl.NET 1.4.
You have to basically edit the configuration file by hand, however I have it setup so that the raw config file is split into different include files, each of which is setup in my source control system. Then I created a project for the configuration, and then for the whole config. So when something changes in the config, CC.NET itself pulls out the changes, recreates it's config files and the refreshes the system configuration.
This means that anyone can edit the config (if they can access the files in sourcecontrol), and no-one has to go into the program files directory of the CC.NET machine itself.
Not sure whether this answers the question you asked, but this is how our setup works

Resources