Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build static assets in Azure #6

Closed
howlowck opened this issue Mar 22, 2017 · 0 comments
Closed

Build static assets in Azure #6

howlowck opened this issue Mar 22, 2017 · 0 comments
Labels

Comments

@howlowck
Copy link
Owner

Currently the client code is generated in the development machine. This means that every time we want to push to the server, we have to run yarn run deploy:prod on the local machine. The generated file names has a hash between the filename and file extension (ie app.28f32jdi123fnbvbh.js) for cache busting.

Since the generated files are in the git repository, it makes collaboration difficult. Every time someone pushes with a newly generated files. Another developer will get merge conflicts when he/she tries to push.

The ideal is Azure needs to generate the static assets during the build process. This will make development with multiple developers much easier, eliminating merge conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant