Skip to content

Bugfix: mount nginx as /home/omero#46

Closed
joshmoore wants to merge 1 commit intoome:masterfrom
joshmoore:user-1001
Closed

Bugfix: mount nginx as /home/omero#46
joshmoore wants to merge 1 commit intoome:masterfrom
joshmoore:user-1001

Conversation

@joshmoore
Copy link
Copy Markdown
Member

0.2.0 (#31) works fine for user 1000 on openstack or docker-machine, but for higher users, the nginx job fails. This change corrects that.

@joshmoore
Copy link
Copy Markdown
Member Author

Note: to test this, I had to be very careful about which user cloned/created/started up what where. This is the script I used:

omero@jamoore-docker:/data$ cat test.sh
REPO=${REPO:-aleksandra-tarkowska}
BRANCH=${BRANCH:-round2}
USER=${USER:-omero}

sudo mkdir $BRANCH
sudo chown -R $USER:$USER $BRANCH
cd $BRANCH
sudo -u $USER git clone git://github.com/openmicroscopy/devspace .
sudo -u $USER git remote add test git://github.com/$REPO/devspace
sudo -u $USER git fetch test
sudo -u $USER git checkout test/$BRANCH

sudo -u $USER git config user.email josh@glencoesoftware.com
sudo -u $USER git config user.name jmoore
sudo -u $USER git remote add m53 /data2/metadata53
sudo -u $USER git fetch m53
sudo -u $USER git cherry-pick d9c58d4^..a45b3f2

sudo cp -r /data/metadata52/slave/.ssh slave/
sudo cp /data/metadata52/slave/.gitconfig slave/
sudo chown $USER:$USER slave
sudo -u $USER -s
omero@jamoore-docker:/data$

@atarkowska
Copy link
Copy Markdown
Member

atarkowska commented Jun 14, 2016

I have just installed 0.2.0 devspace/master@3f62596cb6029fa522505e80441551e933fb067b (without that PR) and the only problem with web was

File "/home/omero/workspace/OMERO-web/OMERO.web/lib/python/omeroweb/webgateway/api_marshal.py", line 23, in <module>
    from omero_marshal import get_encoder
ImportError: No module named omero_marshal

I will update that to pip install omero_marshal. Assuming ome/openmicroscopy#4708 is coming in

diff --git a/home/jobs/OMERO-web/config.xml b/home/jobs/OMERO-web/config.xml
index 60f2630..0c8ad0a 100644
--- a/home/jobs/OMERO-web/config.xml
+++ b/home/jobs/OMERO-web/config.xml
@@ -58,6 +58,7 @@ source $OMERO_INSTALL/settings.env
 pip install -r $OMERO_DIST/share/web/requirements-py27-nginx.txt
 pip install &quot;zeroc-ice&gt;3.5,&lt;3.7&quot;
 pip install &quot;django-redis-cache&gt;=1.6.5&quot;
+pip install &quot;https://github.com/openmicroscopy/omero-marshal/tarball/master&quot;

 #start-config
 $OMERO_DIST/bin/omero config set omero.web.application_server &apos;wsgi-tcp&apos;

Web is now working on https://10.0.51.133/web

@atarkowska
Copy link
Copy Markdown
Member

I deployed devspace on plane openstack purely via ansible scripts https://github.com/aleksandra-tarkowska/infrastructure/tree/devspace/openstack/examples omedev-docker.yml and devspace.yml

(venv)[omero@devspace develop]$ docker-compose --version
docker-compose version 1.7.1, build 6c29830
(venv)[omero@devspace develop]$ docker --version
Docker version 1.11.2, build b9f10c9

@joshmoore
Copy link
Copy Markdown
Member Author

For comparison,

ubuntu@jamoore-docker:~$ docker --version
Docker version 1.11.0, build 4dc5990
ubuntu@jamoore-docker:~$ docker-compose --version

@aleksandra-tarkowska, if you think this is dangerous, we can close. But I spent a solid day trying to get 113 to work, and this was required. I don't know what the difference is, but I'll leave it running on 113 and we can see if any problems arise.

@atarkowska
Copy link
Copy Markdown
Member

atarkowska commented Aug 22, 2016

sorry for a slow response to that, but could you point me where exactly is m53 branch or d9c58d4^..a45b3f2?

@joshmoore
Copy link
Copy Markdown
Member Author

Late October, I'll try to migrate the m52 build to use the newest devspace version to take advantage of the Bio-Formats tests. Closing this for the moment.

@joshmoore joshmoore closed this Oct 15, 2016
@atarkowska
Copy link
Copy Markdown
Member

be aware of #55

@joshmoore
Copy link
Copy Markdown
Member Author

Thanks for the heads up. It won't be for a couple of weeks, and I'll contact you before starting work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants