Replies: 2 comments 1 reply
-
Did you miss anything? This was the perfect approach for me, solved hours of headaches so thank you!!! |
Beta Was this translation helpful? Give feedback.
1 reply
-
Thanks for posting this. The first bit about build directory for docker is covered in our Docker Usage Guide#build-slate. I've amended Deploying State guide to include a note on using |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In order to avoid having local ruby, I need to be able to build and deploy with pure docker. I have it working now but it took me ages to figure out. These are the steps I take:
Run
docker run --rm --name slate -v $(pwd)/source:/srv/slate/source -v $(pwd)/build:/srv/slate/build slatedocs/slate build
Note the extra mounted build folder, took me a while to figure out that was needed. Although this could be my lacking Docker skills.
And then locally run
./deploy.sh --push-only
with the push-only flag in order to prevent invoking ruby gems which are not installed.It works, but I feel like there must be a way easier way. Did I miss something?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions