container issues to be aware of

[mikkokotila]

The only missing thing is having jupyter accessible after ./container new, start and restart commands. The idea is that we have a standard link which gets generated in the HTML, so the notebook link becomes functional in the GUI. This is why I chose a port number that would be very rarely in use, so there might be some much better way to do this as well if we have jupyter running as a service.

Apache is also not actually running as a service, we just use docker exec as part of the relevant ./container commands.

Other than that, you can see everything in the Dockerfile. I found that it's probably easy to do things in a way where you go in to the box and then do some changes there, but I completely avoided anything like that in order to make sure that when we make changes later, we can always just automatically build the functional system without having to go in to it. As I understood, the goal would be that there is never need to go in.

That's about it I guess, otherwise it should be pretty straightforward.

I guess one nice thing would be also to have the container not as localhost but /autonomio/ now that we are talking about what I was not able to complete.

Thanks a lot! :)