--
You received this message because you are subscribed to a topic in the Google Groups "sage-cloud" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-cloud/S9WqlcaZ_9k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-cloud+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cloud/CAGG4CB4AY0RxAZKsvrEywbRCiSfM30CJQbVvPQnZtJW%3DGsnszA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
-- harald
--
You received this message because you are subscribed to the Google Groups "sage-cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-cloud+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cloud/CA%2BjwZMj%2B6sjNWs1d6yjA7TSUyGLgzqmSYr8_tDJJaFN%3DfwKsOw%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "sage-cloud-members" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-cloud-members+unsub...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-cloud-members.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cloud-members/CAC6x94SpdP1bpkBjK5mmyw%2B8GC3RKhYGEnYfFFAOQc%2BsqjbioQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Thanks again.
I have a question about using the docker image for development and
testing. Does it make sense to use docker to help with development?
Suppose I clone the smc repo, create a branch, make some changes
locally and then in src/dev/docker/
$ make build
$ make run
If I understand correctly this should give me a reasonably good way to
test my changes locally. If I like what I did, then I could just
commit, push my changes and make a pull request. Does that sound OK?
--
BTW, here is another note for people like me who are less familiar
with using docker: Rather than using a random port assignment (-P) and
leaving the terminal attached to the container as suggested in the
README.md, I prefer to create the smc container like this:
$ docker run --name=smc -v ~/smc:/projects -d -p 8080:80
williamstein/sagemathcloud
This gives the container a name (smc), detaches the terminal and
assigns local port 8080 for http (you can use a different unused port
and also assign another port for https). The name makes it easier to
refer to the container and to use commands like:
$ docker stop smc
$ docker start smc
--
You received this message because you are subscribed to a topic in the Google Groups "sage-cloud" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-cloud/S9WqlcaZ_9k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-cloud+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cloud/CA%2BjwZMi6RqQpRj6KLLUQYrE7sD3piG8SQwx4DPLu3cXM4hMBCQ%40mail.gmail.com.