6.5 KiB
ADDITION OF A REPOSITORY PROCEDURE
INTRODUCTION
This document is a guide on how to add your own repository to store your projects and exercises. This guide assumes that you have understood the files structures of the repository public. It will only address the settings part of this task. The addition of projects will be treated first as it does not require the knowledge of docker.
However being familiar with docker is mandatory for adding your own exercises with your tests.
PREQUISITES
-A github account where your exercises repository will be stored https://github.com/.
-A dockerHub account https://hub.docker.com/.
I- SETUP OF YOUR GUTHUB REPOSITORY THRU A FORK
Instead of starting with an empty repository, for the very first time we recommend forking the official public. repository.
The advantages of this way:
This will give you a base to work on regarding the file architecture of an exercise repository with examples.
You will also be able to customize already existing exercises to your needs.
With just a quick modification the repo will be ready to be linked.
1. Create your own public repository
Once logged into your github account, click on the creation of new repository:
It is the button New
(the button is on the top corner right side)
2. Git clone your repository and prepare an example for the folder structure for projects
- Create a folder called
subjects
- Inside this folder create a folder called what you wish (example:
firstproject
) - Inside the folder
firstproject
create aREADME.md
file which you will use as the subject content of your first project - After the subject content
README.md
is created, create a folderaudit
inside thefirstproject
directory - Inside the
audit
folder create aREADME.md
that respect the audit type of file. We advise you to take an example such as the ascii-art auditREADME.md
file. Here is the link to the raw file. - Once all those files are done, git push them to your new repository
3. Publish the repository on github pages
- Go to the settings tab of your projects repository.
- On the option page find the GitHub Pages section.
- Please see below the settings to follow.
- Note that the branch may be called
main
instead ofmaster
. (Please not that it might take up to 10 mins for your page to be pusblished)
- You will notice that a message says `Your site is published at https://yourgithublogin.github.io/nameofyourrepo
**4. The addition of a custom project
Take note of the paths of a project subject you added and add them to the attributes
Example:
If user Frenchris, added an exercise to the nameofyourrepo called firstproject
This is the path where the README.md subject would be.
https://frenchris.github.io/nameofyourrepo/subjects/firstproject/
Note that you do not keep the README.md at the end of the path but you do keep the /
This path should be added to the attribute “subject” of type string in the object attribute of the new exercise.
Additionally the README.md audit path would be. https://frenchris.github.io/nameofyourrepo/subjects/firstproject/audit/
This path should be added to the attribute “subject” of type string in the object attribute of the new exercise.
-
Once both those path are noted, create your project on your server.
-
Add the regular attributes (
groupMin
,groupMax
,language
,exerciseType
) -
Add the optional attributes to test if your wish (
auditsRatio
,auditsRequired
) both set to 1 -
And add the
audit
andsubject
attributes (of typestring
) with the previously noted paths
Once the attributes are filled.
- Create a module, called
Div-custom
for example. Add its standard attributes. - Add
firstproject
as a child toDiv-custom
.
Note: If you do not wish students from other events to be selected for matches in this new event. in the children attributes of the module,
-
Add
matchWhere
as aFUNCTION
-
Set its value to
USERINEVENT
This attribute will isole the event during matches to the user of the event. -
Add this
Div-custom
as a child in your campus object -
Go to event, and launch the event
yourcampus/Div-custom
-
Add yourself and other testing accounts to the newly launched event.
-
Test your subject by creating a group and launching an audit.
If the paths are correctly inputed and your repository is correctly publicly published on gitHub pages, you will see your subject and your audit in the platform.
II- SETUP OF YOUR DOCKER REPOSITORY
-
- Sign in your docker hub account the 01 public repository.
-
- In your account, go your settings and link your github account.
-
- Create a repository named “test” and make sure that your github account is linked. If you see this image,
It means your github account is correctly linked.
-
- In the Builds tab configure the automated build settings as below (for the go tests).
-
- Once the build is complete (it can take 5 to 15 mins). Go back to the attributes of the exercise, Add the attribute testImage (type string) Fill it with the name of the repository, In this example: frenchris/test
-
- Once your exercise has both the attributes completed correctly, the exercise is viable and can be tested on the server which was selected for its addition.
-
- As a reminder to test the exercise it is suggested to follow these steps:
a.
Create
a customQuest-test
object b.Adding
the newexercise
object as a child to the newly createdQuest-test
object c.Create
aPiscine-test
object d.Adding
the newQuest-test
as a child to the newly createdPiscine-test
object e.Adding
thePiscine-test
to thecampus
object as first child f. Go to the event page and launch the newly createdPiscine-test
. (You may need to refresh the page 2-3 times before thecampus/Piscine-test
option appears) g. Once the event is launched, use the event page to add yourself as a student in the launched eventPiscine-test
h. You can now try the exercise. If everything is well set, the subject should be loaded and, when you submit a correct solution, the exercise should pass.
- As a reminder to test the exercise it is suggested to follow these steps:
a.