search

getavalon / docker

Avalon in a Dockerfile
MIT License
5 stars 2 forks source link

Initial tests. #21

Closed tokejepsen closed 6 years ago

tokejepsen commented 6 years ago

This is related to #17

tokejepsen commented 6 years ago

Alright, we are back to the same issue as before; the avalon executable on linux does not seem to be forwarding on the arguments passed to it.

mottosso commented 6 years ago

Ok, not entirely sure testing the CLI through Python is the right approach. Maybe we should try testing the CLI via the command-line instead. Let me try something..

mottosso commented 6 years ago

Sorry, I'm totally hijacking this. :P

mottosso commented 6 years ago

Done, let me know what you think.

tokejepsen commented 6 years ago

Sorry, I'm totally hijacking this

Its all good. I was lost anyways :)

So we are currently not using nose for any tests, then?

mottosso commented 6 years ago

So we are currently not using nose for any tests, then?

Hah, no. It doesn't look like it. Let's save nose for when we do tests not involving the CLI.

mottosso commented 6 years ago

Btw I've added the synchronisation with CGWire, so that should work now.

I haven't figured out a good way of running it yet, at the moment you can start it from terminal.bat like so:

$ python a:\sync.py

It'll refresh Avalon with data from CGWire every 10 seconds. So now we can create projects, assets and shots from there, but there isn't any way to manage applications or path templates yet. That's something we should have a chat with Frank about.

tokejepsen commented 6 years ago

Btw I've added the synchronisation with CGWire, so that should work now.

Very cool!

I was thinking the syncing daemon would be part of the docker container?

mottosso commented 6 years ago

Let's continue here: https://github.com/getavalon/docker/issues/23