I am new to featherjs when I run npm install and run by using npm start I am getting the below error. I tried to use the one sample project from github [https://github.com/swina/feathersjs-webpush-notifications][1]
Like the error says, you need a secret (and probably additional) configuration for authentication. This is usually located in config/default.json (or config/<environment>.json). Have a look at the feathers-chat configuration which is the standard configuration generated by the CLI and the recommended way to get started. More information on authentication configuration can be found in the authentication API documentation.
Related
I have NextJS app with SSG. This functionality was added recently and according to it I should do next-export after next-build to get static files. But after appearing in 9.4 of Incremental Static Regeneration I need to keep server on by npm-start command (in my case I use custom server file with next-express functionality). It works good locally and It works good when I get artifact from Azure. But It doesn't work globally when it will be deployed finally. Help please
Through my attempts, I found that it is impossible to install globally or use next in Azure Web App. That is, it cannot be deployed through Github.Deploying using other methods such as FTP cannot run successfully. It should be related to the azure node environment.
But the method provided in this post says that it can be processed by adding web.config. I think it should be useful and helpful to you. Please read it carefully and try it.
You also can read this document, maybe it useful to you.
I am trying to deploy a node application which imports a private npm module to Google App Engine. I'm still stuck at npm install failing due to Unable to authenticate, need: Basic realm="GitHub Package Registry".
One method of npm authentication is via the NODE_AUTH_TOKEN environment variable. GAE does not accept environment variables via the command line, only app.yaml, so I added my token to the app.yaml during my Github Actions CI process. It turns out that App Engine uses a separate Cloud Build environment to build which doesn't have this environment variable; therefore, failure again. I also tried creating a cloudbuild.yaml and subbed in my environment variable but no luck there. Lastly, I've tried to set my key via .npmrc like so:
//npm.pkg.github.com/gw-cocoon/:_authToken=$NPM_TOKEN
#gw-cocoon:registry=https://npm.pkg.github.com/gw-cocoon
and subbed in the token during CI. This fails for the same reason but I am not sure why. This token is autogenerated on each CI run so I cannot use Google Cloud KMS.
I was disappointed to find that using private npm modules with App Engine Standard is apparently not supported at all. This seems like a pretty glaring limitation given the rising popularity of GitHub packages etc for building modular (private) applications.
Interestingly, Google Cloud Functions apparently supports private npm modules, so perhaps it's just a matter of timing to gain support in App Engine.
I have been following this
guide to installing Parse Server on Amazon AWS with Elastic Beanstalk, and the set up is working fine, however that particular guide only addresses the installation of Parse Server and not the Parse Dashboard, which I would also like to have set up.
Being as Parse is a Node.js app, I was hoping I could get away with "npm install -g parse-dashboard" through the command line, but seeing as the changes on the instance might be overwritten by the load balancer I am not sure this is the right path.
I do know that Amazon has an EB CLI that can be used to install applications but I am not sure if that is the best/simplest way either?
What I would like is the easiest way to install Parse Dashboard and connect it with my AWS EB set-up, and I would also like for the Parse Dashboard to be easily updated when changes are made available through Github.
So my question really boils down to two alternatives, as I see it;
1) Should I install the Parse Dashboard on AWS, if so - what would be the best way to do this?
2) Can I perhaps set up a local install of the Parse Dashboard and connect it to my Parse Server hosted on AWS EB? If so, what would be the recommended method of doing this.
For question 1, you don't want to put the dashboard in public domain. Parse dashboard gives full access to modify your database.
If you still want to do it, it can be done just like the parse-server. Once you have clone the repository add an app.config file under /your_project_folder/.ebextensions/app.config with the following content:
option_settings:
aws:elasticbeanstalk:container:nodejs:
NodeCommand: "npm start"
and then follow this guide.
I'm currently moving on with reading about node. I'm getting through the tutorials well using the command line. However I am thinking ahead and I want to create a simple register, log in and log out website.
Where would I place the node files on a server (all examples I see run from local host:3000)?
What is the best tutorial for creating this type of website from scratch with node?
Thanks in advance!
It doesn't really matter where you put the files on the server. The localhost:3000 bit comes from the fact that your core server file tells the server to listen on that port.
I would recommend using the express-generator from npm. It's pretty versatile and does a lot of the leg work.
Just run the following:
npm install express-generator
After installing, you'll need to just run the following to create a new web app:
express
The details are here: http://expressjs.com/starter/generator.html.
Also, try to read through and understand all of the pre-provided code.
I have been using winston for logging in my node application.Now I need to setup scribe for aggregating the application logs.I noticed the node-scribe client for node app to interact with scribe client.But my doubt is how to make the existing logs to interact with the scribe client without changing my logging from winston.
Thanks in advance
There's a winston-scribe npm module. Its source code has been removed from github but it's still there in npm registry. It's fairly simple (49 lies of code) and depends on scribe module (hosted on github as node-scribe). Just install it, import the Scribe transport and give it a try.
DISCLAIMER: I haven't tested it but I think it should work.