Author: admin

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Break the PR

The week saw a lot of commands been added to the sTeam-shell script.

The earlier PR sent during the proposal writing period was addressing a lot of issue’s. As a result the PR was cherry picked and rebased to form smaller PR’s for each issue.

Import from git script

The import to git script was further enhanced to support the feature whereby a user can specify the name of the object in the sTeam directory when a single object is been imported.

The user can now import a single object to the steam work area using the import-from-git script.

import-from-git.pike ~/gitfolder/zy.mp3 /home/sTeam/

import-from-git.pike ~/gitfolder/zy.mp3 /home/steam/ab.mp3

./steam-shell.pike -u uname -h hname -p pno

./steam-shell.pike -u user -h host -p portno steam-command

create user test

delete user test

list users

create file filename destination

list my groups

list groupname members

delete groupname

send_email

Logs

log

The log files include errors, events, fulltext.pike, graphic.pike, http, search.pike, security, server, slow_requests, smtp, spm..pike and tex.pike.
Enter the name of the log files you want to open.
Note: The filenames should be separated by ",".

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

User Utils

User  convenience is an important aspect for any application to succeed. The sTeam root user should be able to create or delete a user. A command to add / delete a user was added successfully.

create_user username password email

 _Server->get_module("users")->get_users();

Similarly a command to delete the user was added to the steam-shell.

delete_user username

delete test.pike

query_attribute("

 Import from git script

sudo ./import-from-git.pike gitfolder/xyz.mp3 /home/sTeam/

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Logs

Week 3 included working on to provide support for logs and exporting of the content from sTeam directory to a git repository. Week 3 also witnessed a breakthrough in sTeam development by Siddhant Gupta who was able to successfully implement the TLS protocol in pike.

The Logs were displayed erroneously. Also the user was not able to scroll down the log to the latest message.  During the course of the week the golden ratio script used in the program was updated to it’s latest version.

Also the editor is opened using sudo command so as to access the vim scrips in the /usr/local/lib/steam/tools directory.
The files are opened using the vim command:
vim -S script -c edit filename1|sp filename2

Only one buffer is accessible at a time. In order to switch the buffer to log buffer the command is CTRL+Ww. Enter this command directly without entering the vim terminal using :.
The log buffer would be accessible, can be edited and scrolled down to the latest log message.

The logs were displayed erroneously. Ideally the log should be displayed based on the buffer where the sTeam function is called and accordingly the relevant log buffer should be called and display the output. This error was fixed.

The log is displayed in the file named after the file which is opened and concatenated with the suffix “-disp”. In Vi the  :% buffer stores the value of the current file. Consequently this value was concatenated with “-disp” to display the buffer accordingly. The Vi script can be seen below.

Export to git script.

The later phase of the week saw that the export-to-git script was tested vigorously.  All the known issue’s based on the script were replicated in the system and solution was found for them.

The export to git script is now capable of exporting multiple sources at a time. If the last argument is always the target repository then any number of previous arguments can be sources.

Example command :
./export-to-git.pike /home/sTeam/file1 /home/coder/file2 /home/sTeam/container3 ~/gitfolder

The export-to-git script also exports the source name in the branch.  To help distinguish between the branches, we need more descriptive names:

./export-to-git.pike /sources/ /tmp/export-test/

./ecport-to-git.pike /home/coder/demo1.txt /temp/export-test/

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Indentation of Output made independent of the screen-width.

The week 2 saw that the work done till date is tested and looked out for errors. The pull requests made by all the other contributors were tested individually. The errors encountered in them were resolved and the solutions updated in the code base.

There were errors encountered in the Pull request. These needed to be modified. The notable one’s were the Indentation of the output displayed by the look command in the steam-shell. The earlier display was taken into consideration that the default size of the linux terminal is 80 char long. However this can differ from individual to individual terminal settings. Therefore the module reference of pike was studied and a method to display the contents in the output of ls command format was written down. Thus now the output is independent of the screenwidth of an individual.

Also there were minor errors in the edit.pike script. These were resolved too. The edit.pike was not able to exit the program. Therefore an exit(0) call was made. This resulted in the edit.pike being able to exit successfully but a new error was introduced in the steam-shell.pike. When the edit.pike command was called inside it, the steam-shell.pike would exit on successfully completing the edit command. The steam-shell should not exit in this case. There were changes made in the VisTeam.pike, edit.pike and applauncher.pike in order to get the utility working correctly.

The steam-shell vim plugin was modified and the support for multiline commands was added. Now the user can type the commands in multiplines, format them and then execute them. The output will be displayed in a new tab.

An example of it can be seen below:-

Output:

The import-from-git.pike script is used to import contents from a normal git repository into the steam directory. The import from git script was studied and understood initially. The issue’s listed were replicated in the system and a possible solution for them was found out.

The script has support for importing multiple documents at the same time. Also the objects imported supported only text mime type. The script was modified to support other mime types by initially detecting them through an external process. However later in the server/factories/Document_factory.pike file the auto detecting of mime type was found out and used in the code. Now the mime types are detected and updated successfully for documents of other mime types like MP3, jpg,png etc

The contents of objects of types other than text mime type were not been read by the existing process. As a result this resulted into creation of empty objects with the set mime type. The process to read the contents were modified and the contents of objects of other types were set accordingly. The content is read in the form of a string. Since every object can be read as a string.

However in the import-from-git an issue was encountered. Indexing over Null value with set_contents for every object created by the script. On running the script again the earlier object is successfully imported but the same error is encountered over the next object to be imported. This issue would be looked down in the coming week and tried to solved. Also support for importing single objects will be provided.

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Indentation of sTeam-shell output

During the 1 st week the Indentaton of the output in the look command in steam-shell is formatted to be displayed in the way the output is displayed when the ls command is executed.

The module reference provided by the pike language is used for formatting.

he screenwidth of the the user is calculated using the command tput rows.
This value is then passed as an argument to the write function to display it in the form of output of an ls command.
The example of this can be seen in the modref by Pike.

Example:

write("%-$*s\n", screen_width,"Given a\nlist of\nslosh-n\nseparated\n'words',\nthis option\n"+ "creates a\ntable out\nof them\nthe number of\ncolumns\n"+"be forced\nby specifying a\npresision.\nThe most obvious\n"+"use is for\nformatted\nls output.");

Output:

 Given a          list of          slosh-n
 separated        'words',         this option
 creates a        table out        of them
 the number of    columns          be forced
 by specifying a  presision.       The most obvious
 use is for       formatted        ls output.

The following chnages have been made in order to incorporate the changes:

Integration of sTeam-shell into Vi

For integration of sTeam-shell.pike into the Vi, the steam-shell is made compatible to be run when a command is passed as an argument to it. The changes have been made in steam-shell.pike and the applauncher.pike. Also a new file called as VisTeam.pike is created. When this is executed it validates the user and opens two vi buffers. One for typing the command and the other to display the log/ output of the executed command.

A steam-shell.vim vi plugin is created so as to be able to run the Steam function in vi. Whenever this function is executed the selected text in the vi visual mode will be executed.

The results are displayed in the log buffer in a new tab. Since the already existing vim scripts Golderratio.vim and watchforchanges.vim divide the command buffer and the log buffer in the ration 2:1, the output is not visible in the logs. Thus a newtab consisting of the logs is opened.

Execute the command:

Display the output:

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Let the Coding Begin…!!!

Finally May 23, 2016 sets in.

The paths of glory lead but to the grave.

-Thomas Gray

The path of the GSOC journey is a bed of thorns and roses.

The community bonding period has elapsed and the real GSOC journey begins

The community bonding period has lead to some real constructive work been done in the project.
The installation and deployment of the sTeam was largely dependent on the linux environment. This was a major hurdle for the development process.
Also the installation process of the sTeam project was quite cumbersome. These had to be improved.

The community bonding period was spent in addressing these issues.

For simplying the installation process I began with the creation of the .deb package. There was a .deb package for the earlier versions of sTeam. The .deb package was made to incorporate the new changes.
Finally a decision was made to rename the sTeam package to societyserver.
This renaming has lead to several deb source config issues in the package.

These issue’s will be addressed during the later part of the Summer.

In order to facilitate development in all the environments and give the user the ease from the cumbersome installation steps a docker image was made for the sTeam project.
This docker image contains all the necessary dependencies to start the sTeam server.
It also includes the sTeam UI and the Rest API along with it’s dependencies. These have already been installed and developer can start collaborating to it.

The docker image can be found at :

https://hub.docker.com/r/ajinkya007/societyserver/

It has all the necessary information for it’s usage and installation.

The community bonding period also included in me exploring the import and export from git commands, the usage of steam-shell, resolution of some minor bugs in it, integrating the steam-shell in vi. This period also witnessed me getting hands on with the other repositories of the societyserver.org.
The repositories which were analyzed and explored include :-

https://github.com/societyserver/sTeam-web-interface-gsoc-2015

https://github.com/societyserver/steam-rest

So having formed a strong bond during this period, the real showdown begins from May 23, 2016.
The coding period has began, and the time to put words into action has come….
Happy Summer GSOC’ers  🙂

Talk is Cheap, Show me the code !!!

FOSSASIA bring’s people together to share, create, develop and make things with Open Technologies and software. We organize science hack labs, Open Tech events, meetups and coding programs with developers, designers and contributors.
Checkout the FOSSASIA Idea’s page for more information.
(ˢᵒᶜⁱᵉᵗʸserver) aims to be a platform for developing collaborative applications.
sTeam server project repository: sTeam.

Bond, Community Bond

The bond was very highly covalent :p

The community bonding lead to sharing of knowledge between all the developers all around the world, their views and opinions on various technologies used in the current times.

The community bonding period saw to it that interaction between the organization mentors, developers , project mentors and colleagues and GSOC’ers all round the world takes place on a regular basis.

The interaction was initiated by Lays Rodrigues by forming a facebook group for 2016 GSOC’ers.

https://www.facebook.com/groups/GSoC2016/

The personal webblog can be found at ;

https://laysrodriguesdev.wordpress.com/2016/05/

Lays has also taken an initiative and created a map where by all the GSOC’ers in the world were mapped according to their place of residence. This can be seen at :

The community bonding period also ensured that I got included in the developer groups of the various organizations for ensuring that the development happens throughout the summer.

Notable include : sTeam.devel group

Additions to the FOSSASIA, Societyserver and PlanetGSoC organizations on github.

 https://github.com/ajinkya007

One of the project which would be having the links to the majority of the blogs published by the GSOC’ers during the course of Summer is Planet GSoC developed by Rohan Verma.

Planet GSoC is Google Summer of Code Blog Aggregator.

This can be found at :

http://planetgsoc.github.io/