I have a production build on server but I have no project setup (source code), so now I want to release a new update in front end - then how should I do that?
Projects in AngularJs.
--source-map=true|false
I try this command but it requires a src folder
Related
We have one Java/Spring Boot/React project hosted on GitLab. After initial development we decided to move to Azure DevOps. Project structure hosted on the GitLab and in local folder structure is simple:
-- Parent project (parent folder)
------- First Spring Boot Project (built with Maven, produces JAR1)
------- Second Spring Boot Project (built with Maven, uses JAR1 as dependency, produces JAR2)
------- React project (built with NPM, produces static pages)
I need to setup separate build process for React and for Spring 1 and 2 projects.
In Azure DevOps there is selector for build from specific branch but I don't see how can I set pipelines to build project from specific folder?
When you use Maven task to build your Spring Boot Project, you need to specify the path to your pom.xml file by changing the value of Maven POM file field. The file path value should be relative to the root of the repository, such as IdentityService/pom.xml or $(system.defaultWorkingDirectory)/IdentityService/pom.xml.
Here is the document about Maven task.
When you use npm task to build your React project, you can set the working folder that contains package.json. Please select the folder instead of the file when you set the working folder.
Here is the document about npm task.
In addition, you may also need to set path filters in Continuous integration (CI) triggers. Here is the document about CI Triggers.
You have path filter:
# specific path build
trigger:
branches:
include:
- master
- releases/*
paths:
include:
- docs/*
exclude:
- docs/README.md
Please check documentation here
I am developing a project with frontend on ReactJS and backend on Java (Spark framework). To build server with frontend, I build the frontend using yarn build and then, using Maven, copy contents of build folder to src/main/resourses/public folder, from which Spark serves all static files. Recently, I moved to CRA and since then all icons disappeared on production build.
When I run the project on webpack-dev-server, everything works fine. All icons are loaded as you can see below:
But when I build production version of the frontend and copy it to the public folder, I get an this error:
The same fragment on production build:
My thoughts are that either icon fonts are copied incorrectly at some point, or the server cannot properly load the fonts, which is less probable as they were loaded earlier when I did not use CRA.
Also, it seems that fonts do exist in the website, because they appear as Sources in Chrome Dev Tools. However, as I said they might be loaded improperly.
P.S. I'm using the following versions of Semantic UI. I generated semantic folder in src directory using npm i semantic-ui.
semantic-ui: ^2.4.2;
semantic-ui-react: ^0.85.0
I found an issue. The problem was that after I built the frontend, Maven incorrectly copied the production build to the public folder
The solution was found here
I am very new to ExtJS and Sencha Touch. I am trying to learn Sencha Touch, and was able to get a demo version running locally using 'sencha watch'. But I want to deploy this somewhere like Heroku, Azure, AWS or wherever.
How do I get this in production?
I'd appreciate it,
CMazz
How do I get this in production?
Developing your application simply means editing source code and refreshing the browser. All source files are dynamically loaded on demand. There's no building process involved. When it comes to deployment, Sencha Cmd provides the following four build environment options:
Production environment
Creates a production build that is normally hosted on a web server and serves multiple clients (devices). The build is offline-capable using HTML 5 application cache, and is enabled to perform over-the-air updates. You can build using below command :-
sencha app build //Or
sencha app build production
Testing environment
Intended for QA prior to production. All JavaScript and CSS source files are bundled, but not minified, which makes it easier to debug. You can build using below command :-
sencha app build testing
After run the following command, In you app there is build folder. See below screenshot
Now if want to host production then go inside of production folder then after build you code in to your web server (Heroku, Azure, AWS or wherever) and same for testing environment.
For more details you can refers Sencha docs
I maked angular project. I used this generator:
https://github.com/swiip/generator-gulp-angular#readme
I have serwer and domain. My question is: How publish this working project on serwer? Should I use Apache http?
Since you used Gulp, you can check its docs to find out exactly you can build your Gulp application and deploy it to server.
On your command line run this in your working directory of the app
gulp //to build an optimized files to be deployed on to the server
Now in your dist folder in your root of your working directory, you'll find all the files and folders that have been created by gulp task default.
Now you can deploy this on with Apache or node or Nginx or any other server you want. Simply paste all the files to the to the
path/of/the/root/on/server
You can also preview your app the browser and watching for files changing and auto-reloading the browser to review changes by running
gulp serve
More grunt tasks here.
I am working with EXTJS6/sencha cmd 6.1.
I am running sencha app build development on my application but it does not copy my javascript files to the build folder. I searched and learnt that QA & Production builds minifies the JS files and copy it to the build where as Development build does not. I believe, using copy task in build.xml we can copy the JS files in the build folder.
Since, the JS Files are copied in the build folder, I can not send the DEV build from build folder to Server.Can someone has an example or guide me on how to write the copy task in build.xml or are there any other alternatives?
Thanks,
gendaful
I believe that what sencha app build development has changed. in previous versions, it created a development build directory. Now, it just minifies the data in your root directory so that you can run it directly from there.
My workflow is now I just do "Sencha App Watch" and run from my root while doing development. When I want to test my production build I do sencha app build production and the folder gets created as before.
HTH's.