Service/activities4: Difference between revisions

Line 37:

# copy it to sunjammer's bundles/metadata directory

rsync org.laptop.Pippy.* user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/metadata/

# trigger a new build of aslo-v4

rebuild-aslo

~~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 }}

Line 52:

Line 53:

~/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 }}.

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 }}. This is only recommended if the user is '''activities-v4'''. For all other cases, please use {{ code | rebuild-aslo -> /usr/local/bin/rebuild-aslo }} and {{ code | source-update-aslo -> /usr/local/bin/source-update-aslo }} for rebuilding and updating the source code.

ASLO-v4 also maintains host specific configuration in {{ code | /srv/activities-v4/etc }} which is maintained in a git repository. To make changes, add yourself to the {{ code | activities-v4 }} group and commit your changes.

@@ Line 37: / Line 37: @@
    # copy it to sunjammer's bundles/metadata directory
    rsync org.laptop.Pippy.* user@sunjammer.sugarlabs.org:/srv/activities-v4/bundles/metadata/
+  # trigger a new build of aslo-v4
+  rebuild-aslo
-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 }}
@@ Line 52: / Line 53: @@
    ~/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 }}.
+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 }}. This is only recommended if the user is '''activities-v4'''. For all other cases, please use {{ code | rebuild-aslo -> /usr/local/bin/rebuild-aslo }} and {{ code | source-update-aslo -> /usr/local/bin/source-update-aslo }} for rebuilding and updating the source code.
+ASLO-v4 also maintains host specific configuration in {{ code | /srv/activities-v4/etc }} which is maintained in a git repository. To make changes, add yourself to the {{ code | activities-v4 }} group and commit your changes.