Is it possible to deploy a linked Git branch to vercel at a custom folder www.abc.com/customFolderA/customFolderB.
Also, www.abc.com/customFolderC is an existing deployment which i don't want to touch.
Related
i'm already thankfull for anyone reading this.
I've stumbled across some problems trying to deploy a Nuxt application in a correct way. For testing purposes i've created a clean installed Nuxt application so i'm sure nothing is wrong with my codebase. What my ultimate goal is is to push all my nuxt code to github which than gets picked up from a azure deployment pipeline and generates the needed build files and drops them to the webapp service and runs the needed start command. There's no documentation to be find about Azure which is really annoying for me. I'm not used to deploying stuff through a pipeline but need this to be working for this project.
Has anyone experience with Nuxt and deployments through Github -> Azure pipeline -> Build -> Web app running immediatly
What's i've tried already is pushing all the source code to a repository which get's picked up by azure pipeline. The only thing the pipeline does is paste the code in the wwwroot folder. Which is obviously not enough to make the application run automated.
What i expect is some insight from someone who is experienced with nuxt and azure deployments through github/bitbucket (doesn't really make a difference)
You have to configure your pipeline to build the nuxt files and deploy them. You can usually achieve the first step through npm commands, npm install then npm run build.
There's a few different ways to deploy them, which you'll have to decide between depending on your use case and environment. You can create an endpoint pointing to a CDN serving a blob, zip the built files and publish the artifact which is then used by a release pipeline, etc. Once the next files are created, you have all you need to deploy.
My question is about separate package/deploy steps. What I want to do is to package the service at step 1 of the deployment process, then copy the content of the package to another machine and deploy from there. Can't make it work. I use no parameters, and "serverless package" seems to work fine (creates ".serverless" folder without an attempt to deploy), but when I copy the ".serverless" folder to another location and execute 'serverless deploy" it only says "packaging service" and does nothing. Is this how deployment of a package supposed to work? This happens on a vanilla aws node service.
The command serverless deploy --package path-to-package seems to be what you are looking for, as specified in the Serverless Framework documentation.
This deployment option takes a deployment directory that has already been created with serverless package and deploys it to the cloud provider. This allows you to easier integrate CI / CD workflows with the Serverless Framework.
You were probably missing the --package option.
I need to use hosted repo's in nexus, in order to pull all the dependencies from the nexus. I have dependencies from different sources but I need all the dependencies pulled from nexus. I have created one hosted repo, but when I click the URL it shows
"This maven2 hosted repository is not directly browseable at this
URL.
Please use the component browser or asset browser to inspect the
contents of this repository."
Can you please explain descriptive steps to use host repo's in order to pull all the dependencies from the nexus.
Thanks in advance
First you need to upload to the hosted repository all the dependencies you want to pull with the command mvn deploy as mentioned here - Guide to deploying 3rd party JARs to remote repository.
When you done to upload all your dependencies you can browse your components throught the UI in the Search Components box on the top. You can't browse the components in your repository from the url at this moment.
My old company using glassfish, when I deployed I can view deployed as folder, view inside with .xhtml and .class file
Ex: if I need hot fix something, I just access to folder that glassfish deploy and change something.
How can I do it JBoss, when deploy success just have a *.war, I cannot view inside.
It depends how you are publishing you war.
If you are using Eclipse to deploy WAR follow these steps.
Goto server view
Double Click on server
Goto Deployment tab
Uncheck "Deploy projects as compressed archives"
Publish it again.
Play will normally reference core modules such as crud and secure out of the Play installation directory. Is there any way to force these dependencies to be copied to my project modules directory when I run play deps?
Our deployment process requires that all app resources be available inside the project directory.
No, you will need to copy them into your own local repository and use the dependencies file to import them. See this (question has solution in it) on how to do it
The 1.2.x branch of Play on GitHub now contains an option to force Play core modules to be copied into project directory:
play deps --forceCopy
This should copy modules like secure and crud into your project directory.