We go get the code from the official website.

git clone https://github.com/picodotdev/alis/

We change the name so we know that is the official code and we stay off. We only go in there to do a git pull and check the new code. You can use tools like gitahead or gitfiend to read all the changes.

We copy/paste the code of ALIS into our own github. We will add the maintenance files and push the changes to our own github.

  • Introduction to Project Workflow: The process starts with obtaining the official Alis code via git clone, emphasizing the importance of maintaining a copy for reference and updates.
  • Creation of a Dedicated AA Folder: Alis is given its place alongside other projects like ALCI, Carli, and ArcoLinux in a new folder named AA, highlighting the significance of organizational structure in project management.
  • Updating and Tracking Changes: Utilizing Git tools to stay updated with changes in the official Alis repository, ensuring the project remains current with the latest developments.
  • Establishing a Personal Project Repository: The necessity of creating a personal GitHub repository for Alis is underscored, allowing for customization, backup, and sharing of the project with the community.
  • Copying and Customizing Code: The official Alis code is copied to the personal repository, with non-essential files like website information being omitted to tailor the project to individual needs.
  • Utilizing Git Scripts for Efficient Management: The introduction of an updated Git script accommodates the shift from “master” to “main” branches in GitHub, simplifying repository management across different projects.
  • First Commit and Cleanup: Initial changes are pushed to the personal Alis repository, marking the commencement of the project’s development and the removal of unnecessary files to streamline the project.
  • Planning for Detailed Configuration: The video concludes with a promise to delve deeper into configuring Alis in subsequent tutorials, laying the groundwork for comprehensive project customization.

Booting and virtual machines

VirtualBox and VMware designate drives as /dev/sda, while Qemu identifies them as /dev/vda.

Alternatively, opting for 'auto' allows the script to automatically select the appropriate option.

Grub is compatible with both BIOS and UEFI systems.

Refind and systemd are exclusively compatible with UEFI environments. (Configure your virtual machine to match these requirements)

We manage our githubs with two scripts. Use them as a template but change them. Download here.