248
edits
Changes
Jump to navigation
Jump to search
Line 65:
Line 65: + + + + + + + + + +
no edit summary
I personally use the same setup except I don't use git to transfer the files. Because I work in a linux environment, I use git on my primary computer and then just pull it over to the xo using scp. The advantage to this is you don't need to use git to transfer test commits which means my git repo is always in a fairly stable state.
I personally use the same setup except I don't use git to transfer the files. Because I work in a linux environment, I use git on my primary computer and then just pull it over to the xo using scp. The advantage to this is you don't need to use git to transfer test commits which means my git repo is always in a fairly stable state.
===Building XO Release===
When you are ready to package your activity into an xo release.
# From your activity folder, run '''python setup.py fix_manifest'''
# If you have set your system up for localization, next run '''python setup.py genpot'''
# If this is a new xo release, update the activity version in your activity.info file.
#* You only need to update the activity version if you have released an xo file to the public.
#* When testing, it can be useful to build activity bundles every now and then to test on other xo's.
# Finally build the file running '''python setup.py dist_xo'''
#* Your xo file will be build and put into a dist directory with a name like ActivityName-1.xo.