I am deploying my next.js app through fab.dev to cloudflare workers and after generating the fab.zip file I'm unable to deploy it.
Here are some of the steps you can try ,
Reinstall fab actions module
npm install #fab/actions
Make sure you are running fab in bash env or any linux env
it doesnt really work well with windows powershell
Related
I have an ansible playbook to install eclipse. This works fine but I would like to add some plugins to it, like subclipse for instance. Does anyone know how to do it? It might also be a shell script which allow me to install subclipse. This I can run via ansible. I've already tried many things but most often end up with an error:
The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized
I successfully downloaded and started GitHub runner on my own Ubuntu machine. GitLab have a nice runner installer, but GitHub have only package with files and run.sh file.
When I will start the run.sh, it works and GitHub runner starts for listening of actions.
But I couldn't find it anywhere in the documentation, how to correctly integrate the package with sh file into Ubuntu to start sh automatically after Ubuntu starts.
Also I didn't find, if there is needed to do some steps to make runner secure from the internet.
...and also I don't know, where I can setup to be able to run parallel actions, and also where I can setup the limitations of resources, etc...
Thanks a lot for an each help.
I've created a VS Code dev container for my project. To help new contributors get started, should the dev container Dockerfile run npm install?
No. Dev container define a development environment and should not perform actions that would be part of a normal development workflow (such as running npm install).
There are a couple of reasons why npm install in particular should be avoided:
If you run npm install in the dev container Dockerfile and it fails, the dev container will fail to launch. It's farbetter if the developer can open the dev container successfully, and then run npm install in an environment where they can investigate potential failures
npm install must be re-run when the project's dependencies change. Running npm install as part of dev container setup hides this from developers.
Dev container should only use npm install to install global scripts or tools that do not belong in the project's package.json.
It is actually good practice to call npm install as part of the dev container configuration. It eases and accelerate setup of the development environment, ensuring it's ready to use out of the box without extra steps possibly missed.
Note that the npm install must be in a postCreateCommand where sources and package.json are available (contrary to the Dockerfile).
Due to the nature of docker and devcontainer, there is very little reason for the npm install command to fail and need debugging. If it ever happen, VSCode logs will provide meaningful information, otherwise the postCreateCommand can be disabled quickly to investigate the issue.
There exists an official VSCode video, so we can assume calling npm install as part of the dev setup is a common practice: How to automatically run npm install in a dev container.
I am able to configure Fastlane locally and working well with terminal, but when I am trying to run it with Jenkins(I have configured Jenkins locally on my macbook) it is failing every-time(i have installed ruby 2.5.0 again).
Any help on the same would be highly appreciated.
I am attaching SS for your reference.
Jenkins run its build scripts using specified user 'jenkins'. You might want to check if 'jenkins' user had installed requires dependencies to run fastlane, for e.g ruby ...
Have you set up your PATH in Jenkins? In the configuration of your node, in the environment variables section, you'll want to include /usr/local/bin/ with Jenkins's PATH by entering /usr/local/bin/:$PATH.
I have created a webapp based on the the Mean Stack( MongoDB, Express, AngularJS, NodeJS). I had followed this tutorial on setting up AWS: https://scotch.io/tutorials/deploying-a-mean-app-to-amazon-ec2-part-1
I got to the point where they started their server.js file by just calling node server.js. I do not have a server.js though. In webstorm I run grunt serve and it launches everything. On aws I run grunt serve and it just says cannot find bower components. I also try to run bower install and it fails saying I do not have permission but when I run sudo bower install it says bower cannot be run with sudo.
I am not sure how to solve this issue. Should I figure out how to use a server.js?
Any help wold be greatly appreciated
You can use npm start instead of node server.js, if you have initialized the app using npm init.