Step 2: Create project

To generate a project structure there are mandatory and optional arguments to the command. In this tutorial we will take defaults and only supply the mandatory values.

Please open a terminal and set the directory where you would like the code generated. The tutorials assume that all tutorials are folders in a folder named tutorials folder.

qaskx-cli   generate project --parent ./tutorials/course502 --create

A project folder named course502 is generated in the tutorials folders

This should return a successful message something like

	      ______           ___           _______. __  ___ ___   ___ 
	     /  __  \         /   \         /       ||  |/  / \  \ /  / 
	    |  |  |  |       /  ^  \       |   (----`|  '  /   \  V  /  
	    |  |  |  |      /  /_\  \       \   \    |    <     >   <   
	    |  `--'  '--.  /  _____  \  .----)   |   |  .  \   /  .  \  
	     \_____\_____\/__/     \__\ |_______/    |__|\__\ /__/ \__\ 
																   															 
	
          qaskx-cli  - command line tool 
          version     - 0.0.5
          url         - https://docs.qaskx.one/qaskx-cli/
          copyright   - 2023 qaskx.one, usage license limited

QX>>> 2024/03/24 21:00:09 Defaulting gitea repository name to 'course502'
QX>>> 2024/03/24 21:00:09 Defaulting artefact name to 'course502'
QX>>> 2024/03/24 21:00:09 'C:\tmp\qaskx.testarea\tutorials\course502' directory already exists. Please name a new directory.

If you look at your directory structure for the created project location you should see:

The Windows “tree” command does not list hidden directories like .git

And now we can move onto the next Step.

Errors

If the above did produce error messages, you might need to delete the generated directory and then issue the same command with the additional argumber of “-v” for verbose logging to console.

Issues may include push access to create new repository in the remote VCS, proxy internet access required, duplicate repository names.
The command may partially complete.

If you receive a message in regard to VCS token such as below,

then please check your access token to your GitHub or Gitea.

You can supply an access token for VCS also via environment variables.

 $env:QASKX_VCS_TOKEN=" your GitHub or Gitea access token here "

 EXPORT QASKX_VCS_TOKEN=" your GitHub or Gitea access token here "