With 1.7 million freelancers, we'll match you with the perfect talent.
The client has made the following changes to the job.
Client prefers freelancers from:
You are still able to submit a proposal for this job.
The client prefers freelancers from
a different location.
I have a Jekyll-powered website (source code stored in a bitbucket git repository).
I use wercker.com to fetch the code on each git push and automatically build and deploy (via FTP) the new version.
This works great, but I need some changes to this approach:
1) Split the build process into a TEST and PROD version.
In prod, I serve the assets from a different subdomain, so it generates other output for that environment. Currently, I use an environment variable holding the target environment, but wercker can only connect once to the same repository, so I need both environments to be built with one build procedure.
Ideally, the images should only be generated once. This is however not the highest priority for now.
Keep in mind that splitting the wercker-build in two build steps should not break a build on a local machine.
2) When the build is green, I automatically deploy to an FTP server. However, this is not the perfect solution, because:
- it takes a lot of time (~17 minutes for ...
Sign in or Register to see more