I'm currently trying to deploy a web application using Firebase Cloud Functions
Everything works fine locally with firebase serve. But when I use firebase deploy, I got the following error on the firebase console :
Error: EROFS: read-only file system, mkdir '/user_code/node_modules/.cache'
at Error (native)
at Object.fs.mkdirSync (fs.js:932:18)
at sync (/user_code/node_modules/#babel/register/node_modules/mkdirp/index.js:71:13)
at sync (/user_code/node_modules/#babel/register/node_modules/mkdirp/index.js:77:24)
at sync (/user_code/node_modules/#babel/register/node_modules/mkdirp/index.js:77:24)
at save (/user_code/node_modules/#babel/register/lib/cache.js:50:20)
at _combinedTickCallback (internal/process/next_tick.js:73:7)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
I'm afraid not to be able to use babel-register on the production environment because of the read-only property of the environment. Do you have any idea to fix this problem ?
This is an old question, but I found out that you can set the default directory where you want to create a folder, I had this same issue when deploying to firebase functions also, but read about this issue happening with heroku, where you only have write permissions to a tmp folder
https://babeljs.io/docs/en/babel-register#babel-cache-path
Related
I'm playing with Azure Bicep and I was expecting that I can take practically any ARM JSON template and translate it into Bicep. I'm intentionally using the word "translate" instead of "decompile" here, because the JSON template was not originally created with Bicep, so it was not compiled from Bicep to JSON in the first place.
I'm creating a VM deployment in the Azure Portal and when it's successfully deployed I download the JSON template (deployment.json and deployment_operations.json).
Then I run the following command:
bicep decompile deployment.json
The command fails with the following error message:
/deployment.json: Decompilation failed with fatal error "[1:1]: Unable to find a template property named $schema."
What should I do to resolve this error?
Bicep CLI version 0.13.1 (e3ac80d678).
PS The VM deployment is the simplest possible Windows Server VM with no data disks and extra features. Created via Azure Portal by clicking Next-Next-Create.
It appears that I've found the solution when writing the question. I was downloading and trying to decompile a wrong file.
The problem was that I was downloading the deployment.json file instead of an actual template file template.json. You need to click Download on the Template tab.
So instead of downloading the from the Overview tab, click the Template tab and then click Download. Or use the Save-AzResourceGroupDeploymentTemplate PowerShell cmdlet.
Similar problem, same solution: https://github.com/Azure/bicep/issues/5237
I want to host a website via Firebase hosting. When i run firebase init on cmd i get this:
First, let's associate this project directory with a Firebase project.
You can create multiple project aliases by running firebase use --add,but for now we'll just set up a default project.
i .firebaserc already has a default project, using my_project.
How can i change my project? Since I've deleted the default project that firebase mentioned, when i run firebase deploy i got this error:
Error: Failed to get Firebase project my_project. Please make sure the project exists and your account has permission to access it.
Can anyone show me the way out? Thanks.
The solution to this is very simple. All you have to do is go into your .firebaserc and change the defualt to the name of your project. You can probably also just delete .firebaserc and rerun firebase init.
I have created a Nodejs application (sdgnodeapp) in my OpenShift domain, and was trying to import the sdgnodeapp application using OpenShift Explorer into my empty workspace in JBoss Developer Studio 7.1.1 GA .During the Import-Application workspace, I specify the git-clone-directory to be the same as my workspace-directory, JBDS then throws an error
"Could not import project to the workspace.
Invalid project description.
OK
/Users/sddasgu/SDGDevCode/Node/NodeWorkspace/sdgnodeapp overlaps the location of another project: 'sdgnodeapp'".
NOTE: If I change the git-clone directory to some other directory (not my workspace-directory), then the project is added to my workspace as expected.
I am used to creating projects inside my workspace-directory, but it seems to me in the above case, that the git-clone happens successfully, but then then the project creation fails. Is there a way to circumvent this problem ?
This is caused by there already being a directory called 'sdgnodeapp' in your eclipse workspace. Rename the existing one directory on your machine in your workspace to something different and then run the clone command again. That should fix it
We are trying to configure a deployment of ASP.NET application using Octopus deploy.
All is working fine, but sometimes the step fails while trying to overwrite files saying the the file is already locked by some other process.
We already stop IIS before the deployment starts, so not sure what we can try here.
Sometimes the error is in the application customlog folder(txt files), sometimes its in the bin folder for some dll etc.
Exact error is:
*Unable to copy the package to the specified directory 'D:\Apps\XYZ_Stage'. One or more files in the directory may be locked by another process. You could use a PreDeploy.ps1 script to stop any processes that may be locking the file. Error details follow.
Access to the path 'D:\Apps\XYZ_Stage\bin\XYZ.Business.dll' is denied.
System.UnauthorizedAccessException: Access to the path 'D:\Apps\XYZ_Stage\bin\ACA.Business.dll' is denied.*
Any suggestions?
If you're using Octopus 2.0 or higher, you can leverage the "IIS web site and application pool" deployment option which causes Octopus Deploy to handle all the complexities of deploying to IIS without you performing manual steps.
Here's some information: http://docs.octopusdeploy.com/display/OD/IIS+Websites+and+Application+Pools
I am trying to build a Visual Studio Package project via Hudson CI. This is a Visual Studio 2010 project. The project builds fine in my dev box, but for some reason, I keep getting the following error only when building in Hudson:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\VSSDK\Microsoft.VsSDK.targets(378,5): error : Error trying to read the VSIX manifest file "obj\Release\extension.vsixmanifest". The system cannot find the file specified. (Exception from HRESULT: 0x80070002) [C:\hudson\workspace\MyProject_Daily_Compilation\Source\MyProject.VisualStudio\MyProject.VisualStudio.csproj]
I have verified that the file exists on disk in the following location:
C:\Hudson\workspace\MyProject_Daily_Compilation\Source\MyProject.VisualStudio\obj\Release\extension.vsixmanifest
What could be causing this issue?
You are likely to experience such error if the user you are running your build as does not have administrative privileges.
So there are 2 solutions:
1) Run your build (build server) with administrative privileges.
or if you can't really change the user your build server is running on
2) and you actually don't need to deploy the VS extension on the build server itself, set the DeployExtension property in your *.csproj file to false.
Microsoft.VsSDK.targets sets that property by default to true
<DeployExtension Condition="'$(DeployExtension)' == ''">true</DeployExtension>
but if you don't need to deploy that extension locally (but rather would prefer to get the *.vsix bundle built you can safely put
<PropertyGroup>
<DeployExtension>false</DeployExtension>
</PropertyGroup>
The original error is basically happening because the attempt to get the deployment path fails at some point in the build and disrupts successful vsix package generation. By setting the property to false the build doesn't attempt to deploy the extension locally (but a valid *.vsix is generated)
I am guessing you running hudson as a service. If so the "0x80070002 - The system cannot find specified file" could well be due to the user being used to run hudson does not have access.
The quick solution to this is change the "Log on" user for the Hudson service to be your normal account.