Service/activities4: Difference between revisions

Newer edit →

Revision as of 01:48, 20 January 2021

Description

A redesigned Sugar Activity Library for Python3 Activities.

Hostnames

http://v4.activities.sugarlabs.org/

Hosted on

Machine/sunjammer

Administrative contact

activities AT sugarlabs DOT org

Sysadmins

For non-emergency calls, preferably send email to the administrative contact.

Srevin Saju, maintainer.

Notes

To add your activity bundle to aslo-v4 , you need to be a member of the sugardl group. Then, copy your bundle to /srv/activities-v4/bundles , for example:

 rsync dist/Pippy-17.xo user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/
 
 # optionally, generate the metadata and copy them to the same bundles directory

 # add a link to source code repository
 git config --get remote.origin.url > org.laptop.Pippy.git
 
 # get a list of authors of the activity
 git -P --log --pretty=format:"%an" > org.laptop.Pippy.log

 # copy it to sunjammer's bundles/metadata directory
 rsync org.laptop.Pippy.* user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/metadata/

A cron job will automatically rebuild the aslo-v4 and deploy it. Verify that your changes are deployed within 12 hours. TODO: , use a better tool to rebuild the source on detecting changes.

Deploy directory: /srv/www-sugarlabs/v4-activities Source directory: /srv/activities-v4/src Bundle (*.xo) directory: /srv/activities-v4/bundles

Upgrade notes

As activities-v4 user on Machine/sunjammer, do

 ~/bin/also-refresh-src
 ~/bin/aslo-rebuild

This will pull master from the source repository, and the python library will be installed to ~/.local/lib/python3.x/site-packages . Once this has been done, it will be accessible from any directory. ~/bin/aslo-rebuild will rebuild v4.activities.sugarlabs.org, and deploy it to /srv/www-sugarlabs/v4-activities .

Sources

source repository.

@@ Line 22: / Line 22: @@
 == Notes ==
-'''TODO'''
+To add your activity bundle to {{ code | aslo-v4 }}, you need to be a member of the {{ code | sugardl }} group.
+Then, copy your bundle to {{ code | /srv/activities-v4/bundles }}, for example:
+  rsync dist/Pippy-17.xo user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/
+  # optionally, generate the metadata and copy them to the same bundles directory
+  # add a link to source code repository
+  git config --get remote.origin.url > org.laptop.Pippy.git
+  # get a list of authors of the activity
+  git -P --log --pretty=format:"%an" > org.laptop.Pippy.log
+  # copy it to sunjammer's bundles/metadata directory
+  rsync org.laptop.Pippy.* user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/metadata/
+A cron job will automatically rebuild the aslo-v4 and deploy it. Verify that your changes are deployed within 12 hours.
+'''TODO: ''', use a better tool to rebuild the source on detecting changes.
+Deploy directory: {{ code | /srv/www-sugarlabs/v4-activities }}
+Source directory: {{ code | /srv/activities-v4/src }}
+Bundle (*.xo) directory: {{ code | /srv/activities-v4/bundles }}
 == Upgrade notes ==
-''TODO''
+As '''activities-v4''' user on [[Machine/sunjammer]], do
+  ~/bin/also-refresh-src
+  ~/bin/aslo-rebuild
+This will pull {{ code | master }} from the [https://github.com/sugarlabs/aslo-v4 source repository], and the python library will be installed to {{ code | ~/.local/lib/python3.x/site-packages }}. Once this has been done, it will be accessible from any directory. {{ code | ~/bin/aslo-rebuild }} will rebuild v4.activities.sugarlabs.org, and deploy it to {{ code | /srv/www-sugarlabs/v4-activities }}.
 == Sources ==
 * [https://github.com/sugarlabs/aslo-v4 source repository].