Cloud Dev

Installing Homebrew on a Mac Installation Homebrew is package manager for Macs which makes installing lots of different software like Git, Ruby, and Node simpler. Homebrew lets you avoid possible security problems associated with using the sudo command to install software like Node.

nvm is a version manager for node.js , designed to be installed per-user, and invoked per-shell.

The new way of development in the Microsoft world has chnaged. In other to keep up, you must keep abreast with information.  Here are couple of sites you may need: https://github.com/sharepoint https://sharepoint.stackexchange.com/ https://developer.microsoft.com/en-us/office https://sharepoint.uservoice.com/

There is no need to panic if your node.js version is wrong or if you need to deep clean. Follow these steps: Calm down and take a deep breath. From your shell environment, run the command - npm cache clean --force From the operating system, carry out an uninstall with the uninstaller. Reboot the machine. Find these folders and remove them and all the contents if they exist. Some of them may or may not exist: C:\Program Files (x86)\Nodejs C:\Program Files\Nodejs C:\Users\{User}\AppData\Roaming\npm (or %appdata%\npm ) C:\Users\{User}\AppData\Roaming\npm-cache (or %appdata%\npm-cache ) C:\Users\{User}\.npmrc (and possibly check for that without the . prefix too) C:\Users\{User}\AppData\Local\Temp\npm-* Confirm that the  %PATH% environment variable has no references to Nodejs or npm exist. If node is still there,  type where node at the command prompt and you can locate where it resides -- delete all the folders. Reboot your machine again.

If you are encountering issues and need to rebuild the office web app server, follow this guideline:   On the office web app machine Try and take the farm offline (if for example you are in a load balanced environment Then, backup the current Farm information using Powershell commands on the office web app server.   Import-Module -Name OfficeWebApps  Get-OfficeWebAppsFarm > c:\Farmsettings.log Use Powershell on the office web app server to remove all the machine from the farm, then remove the parent machine.  This will delete the farm. Remove-OfficeWebAppsMachine Reboot  the Office Web Apps server(s). Recreate the farm via Powershell on the office web app server. using (if appropriate) the parameter values from the " Farmsettings.log " . New-OfficeWebAppsFarm -InternalURL  " http://farm.com "  -ExternalUrl  " https://farm.com "   -CertificateName "OfficeWebApps Certificate" -Allow...

The default log file in the office web app is usually not too detailed for some faults.   To enable verbose logging, do this: Set-officewebappsfarm -LogVerbosity Verbose After this restart the OWA service using this command Restart-service wacsm -force On completion of your troubleshootings, you can set the log level back to default using the command  Set-officewebappsfarm -LogVerbosity and then restart the service using Restart-service wacsm -force   QED