Alfresco discussion and collaboration. Stick around a few hours after asking a question.
Official support for Enterprise subscribers: support.alfresco.com.
Join in the conversation by getting an IRC client and connecting to #alfresco at Freenode. Our you can use the IRC web chat.
More information about the channel is in the wiki.
More help is available in this list of resources.
2018-11-01 14:44:20 GMT <yreg> ~later tell angelborroy I have been experimenting with the alfresco-docker of keensoft, that docker-compose setup is neat, it works perfectly on my Mac, but not on a fresh ubuntu 18.04 server, I needed to to manually fix permissions on the Postgres logs folder
2018-11-01 14:44:20 GMT <alfbot> yreg: The operation succeeded.
2018-11-01 14:45:45 GMT <yreg> I think, but I am not sure, creating the parent folder for the logs in the folder structure and using a .gitkeep file to version it can help resolving the issue
2018-11-01 14:45:54 GMT <yreg> Will test it later and keep you posted
2018-11-01 15:24:21 GMT <AFaust> yreg: What is the current state of SDK "next version" and integration test? Just wondering because I today I am creating some Docker-based profiles in my general project parent POM(s)...
2018-11-01 15:25:38 GMT <yreg> To be honest there is not much new over there...
2018-11-01 15:29:16 GMT <yreg> What Ole and I worked on during last hackathon is the following: lose a lot of hardcoding and un-needed complexity to manage (among other things) artifacts naming changes ... remove the h2 stuff, remove the possibility to setup the local run with h2/pgsql/mysql, remove the solr4 dependency in the sdk and the ability to run that from the plugin, add a set of docker images to cover for DB/solr6/share/repo with configurable base image/tag, keep running alfre
2018-11-01 15:29:17 GMT <yreg> sco with RAD stuff in embedded tomcat for dev
2018-11-01 15:29:57 GMT <yreg> I haven't had time to continue working on it, I assume the same for ole
2018-11-01 15:30:11 GMT <yreg> AFaust, you should be looking at the plugin open sourced by Xenit
2018-11-01 15:31:15 GMT <yreg> I think it is quite good for building spinning and integration testing docker images
2018-11-01 15:31:20 GMT <AFaust> I believe we already talked about that. I am already using a standard / widely used Maven plugin...
2018-11-01 15:31:50 GMT <yreg> Still you could use that plugin to get some inspiration
2018-11-01 15:34:00 GMT <AFaust> Too late for that... I already have a working setup, and only need to write some actual tests to call i.e. web scripts.
2018-11-01 15:35:06 GMT <AFaust> The only thing missing is a working two-way communication between Repo + SOLR (likely just a matter of finding the best network setup), and the option to run any of the secondary containers (i.e. transformers / Share)
2018-11-01 15:58:01 GMT <yreg> AFaust, I thought that was easy to setup using docker
2018-11-01 15:58:08 GMT <yreg> What plugin are you using ?
2018-11-01 15:58:19 GMT <yreg> Can you use a docker-compose ?
2018-11-01 15:59:48 GMT <AFaust> I could use docker-compose (if everything else fails), but then I would have project configuration living outside of the pom.xml without support for placeholder substitution, which I need in order to be able (e.g. to switch base images between projects)...
2018-11-01 16:00:42 GMT <AFaust> I have not tried all the options yet, as I want to first have a basic setup running with ReST-based unit test client...
2018-11-01 16:01:01 GMT <AFaust> As for "what plugin" => fabric8io:maven-docker-plugin
2018-11-01 16:01:54 GMT <AFaust> Yeay - the ReST test is running correctly.... and failing "correctly", because I did forget to configure authentication
2018-11-01 16:04:24 GMT <AFaust> Ahh, too bad... when the tests fail, Maven quits immediately, so the plugin does not have a chance to clean up the running containers...
2018-11-01 16:06:25 GMT <yreg> Anyway, if everu
2018-11-01 16:07:20 GMT <yreg> Everything else fails you can use this magic string along with binding ports to host : https://github.com/yregaieg/acs6-sdk3-poc/blob/master/docker-compose.yml#L26
2018-11-01 16:07:21 GMT <alfbot> Title:acs6-sdk3-poc/docker-compose.yml at master · yregaieg/acs6-sdk3-poc · GitHub (at github.com)
2018-11-01 16:08:02 GMT <yreg> That points to the host running docker
2018-11-01 16:08:25 GMT <AFaust> Of course that requires I expose every port that the containers need among themselves..
2018-11-01 16:09:01 GMT <AFaust> I.e. for the DB container I have not yet exposed the port, relying solely on a link for their communication
2018-11-01 16:09:10 GMT <yreg> But I assume a plugin as mature as the one you're using should have what it takes to setup networks as well and then any host should be reachable from within the network using the service name / hostname
2018-11-01 16:09:17 GMT <AFaust> But yes, I already considered the fallback to use host-based loopback
2018-11-01 16:09:32 GMT <AFaust> Yes, it does support setting up custom networks..
2018-11-01 16:09:42 GMT <AFaust> As I said, I did not yet try out all the options available to me...
2018-11-01 16:10:04 GMT <AFaust> Only started sometime after lunch today...
2018-11-01 16:10:25 GMT <AFaust> Around 1 or 2
2018-11-01 16:18:23 GMT <yreg> I honestly do not consider keeping the docker containers running a bad thing
2018-11-01 16:18:34 GMT <yreg> As it can speedup consequent runs
2018-11-01 16:31:19 GMT <AFaust> Well... next run the plugin will try to create new, clean containers (remember that integration tests may require a certain state), and run into a conflict.
2018-11-01 16:33:49 GMT <AFaust> I may decide to patch the plugin to add optional VM shutdown hooks to ensure a clean shutdown. If I can manage that in a clean way, may even PR that back...
2018-11-01 16:35:42 GMT <AFaust> At the moment this is only a container name conflict, and I'll also have to check if there is some way to configure/trigger random container name generation...
The other logs are at http://esplins.org/hash_alfresco