guilleamutio / rekcod Goto Github PK

Alias only last for powershell session so, in order to make them permanent we should use a Powershell alias

Running minikube start with context of Linux throws Can´t create context in C.\...\.minikube Access denied.

Running the same command as admin does not throw any error

AS A Developer
I WANT a CI pipeline
TO check that the powershell script syntax meets the standard defined by Microsoft

AS A user
I WANT TO run the script as admin by default
SO I don´t have to right-click and select "Run as admin" for install, with a pop-up window is okay

Create a script like 'rekcod-dashboard.ps1' that will spin up a portainer container and portainer agent container, it doesn´t matter if portainer server is in windows and agent on linux or viceversa, as long as we have two environments in the portainer server that can help to manage docker from a UI

AS A Product Owner
I WANT TO automate the Docker binary install for Windows containers
SO I dont have to click anything else apart the install script

ACCEPTANCE CRITERIA
Dockerd is intalled on Windows and is able to run Windows containers. Tets with the Hello World is enough
rekcod is used on the command line instead of Docker

AS A Product owner
I WANT WSL installation to be automated
SO I don´t have to click anything else that the 'install.ps1' script

ACCEPTANCE CRITERIA

• WSL is installed with the name rekcod
• WSL distro uses systemd
• Dockerd runtime is installed
• Dockerd is configured to be started on bootup

AS A Product Owner
I WANT TO have a .zip/tar.gz each release on the GitHub repository
SO we can have a track of the releases.

ACCEPTANCE CRITERIA:
Each merge time we tag a new version (Not each time we merge onto the main branch) a release has to be created with a zip and a tar.gz compressed file with all the code in that version

Docker is started as admin, understandable, but a user seems to not be allowed to execute 'docker ps' and it should be!

Maybe this is related to the docker-users group created by Docker installation and maybe the user should be added there.

AS A user
I WANT TO have documented all rekcod repository
SO I can contirbute when needed and understand how the process is done without having to open an issue

ACCEPTANCE CRITERIA
Documentation should contain info about:

• rekcod itself
  • motivation
  • approach
  • installation
  • future work
• Definition of Done
• Definition of Ready
• Members/Owners
• CICD process
• Git strategy

Is your feature request related to a problem? Please describe.
As scripts are being run using relative paths can lead to erros

Describe the solution you'd like
Instead of using .\script.sh nomenclature lets use ${rekcodInstallationPath}\script.sh

Download WSL distro from release, remove tools folder and clean everything after install

AS A developer
I WANT TO have an virtual machine
TO develop rekcod without affecting my system

ACCEPTANCE CRITERIA
Have a virtual machine restricted to developers with virtualization enabled.
Have the credentials securely stored

When the command rekcod-start is executed, the Docker service must start and the WSL should expose the daemon directly to the Windows host and create a Docker link to that daemon.

Maybe a new bash script should be created and call from start.ps1 script

As we are not going to use multiple branching strategy (DEV/ACC/PRD), and instead, we are going to use version tagging with releases, it may be important to research a good git strategy with just a development/main branch

Is your feature request related to a problem? Please describe.
The install.ps1 script has three curl/Invoke-WebRequest/wget calls. This solution translates into more time for installation as it have to download 1.04GB only for the WSL.

Describe the solution you'd like
As there are two branches, develop and main, it would be good that once a new merge is done to main, which means that a new release is ready and this process will be automated through a CD pipeline, this pipeline could make a zip or something, even an exe file, with all the things needed.

As we are going to use a default WSL distro and due to the limits of git lfs option, we need to study an alternative solution that doesn´t need to be paid.

Once the WSL distro is stored in another site, the main script should be modifed to download the file and put it in the 'tools' folder with the same name

AS A user
I WANT TO select the installation folder
SO I can decide if it´s going to be installed on D:/ C:/ or wherever