5

I have a question maybe a little silly, I'm trying to deploy a static site with codeship but I can't understand the documentation:

https://codeship.com/documentation/continuous-deployment/deployment-to-aws-codedeploy/

Currently it's a little different the way to setup, I don't know what to write in "Local Path" input

enter image description here

1 Answer 1

16

You should interpret "Local Path" as a reference to the working directory in the virtual machine.

It took me awhile to figure it out. You can see this in the cloning step. You will see something like this.

Cloning into '/home/rof/src/bitbucket.org/<your_user>/<you_repository>'

The path /home/rof/src/bitbucket.org/<your_user>/<you_repository> is what you are looking for.

If you want to upload something inside of that directory just concatenate the rest like /home/rof/src/bitbucket.org/<your_user>/<you_repository>/internal/path

For example: You can compile your NodeJs App and compress the dist directory to build an artifact and then upload it to S3.

It would be something like this. In your setups commands:

nvm use 5.6.0
npm install
npm run deploy
tar -zcvf artifact.tar.gz dist/
mkdir upload/
mv artifact.tar.gz upload/

Finally your "Local Path" is:/home/rof/src/bitbucket.org/<your_user>/<you_repository>/upload

Hope this help!.

Sign up to request clarification or add additional context in comments.

1 Comment

in my case just using upload or dist worked also

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.