web-dl-tools / web-dl-tools.github.io

Landing webpage source for Web DL's main GitHub.io website.
https://web-dl-tools.github.io
5 stars 1 forks source link

Installation issue please help ! #1

Open LuciferxR opened 2 years ago

LuciferxR commented 2 years ago

Hello i try many times to install web dl tool but I can't please make one installation video please help me out of this.

RineshRamadhin commented 2 years ago

Hi,

What OS and architecture are you trying to install this on? (e.g. Raspberry Pi OS/Debian 11 (64-bit), macOS 12 Monterey (Apple Silicon), etc.)

Additionally have you already installed all the required software? If so, which versions of git and docker are you currently running?

LuciferxR commented 2 years ago

I'm running on windows 10 Home . Please help

RineshRamadhin commented 2 years ago

This tool is mainly build for running on a (headless) instance of Raspberry Pi OS running on a Raspberry Pi 4. You can run it on Windows or macOS, but that does require some more knowledge of Docker (and especially it's limitations on Windows).

I'm assuming you're running on an x64 chipset (e.g. Intel® Core™ i7, AMD Ryzen™ 9, etc.)

You should start by performing the following steps:

  1. Install Docker Desktop and Git.
  2. Start Docker desktop. You should see it's whale icon appear on the taskbar (bottom right, next to the clock somewhere).
  3. Verify it all installed correctly. You can do this by opening a terminal (Search for either Command Prompt or Windows PowerShell) and run the following commands:
docker version

docker compose version

git --version

Please let me know the output of those commands.

LuciferxR commented 2 years ago

Hare is the output results

IMG20220911182035.jpg

All those code hare .

PS C:\WINDOWS\system32> docker version

Client: Cloud integration: v1.0.28 Version: 20.10.17 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 23:09:02 2022 OS/Arch: windows/amd64 Context: default Experimental: true

Server: Docker Desktop 4.11.1 (84025) Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:23 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.6 GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1 runc: Version: 1.1.2 GitCommit: v1.1.2-0-ga916309 docker-init: Version: 0.19.0 GitCommit: de40ad0 PS C:\WINDOWS\system32> docker compose version Docker Compose version v2.7.0 PS C:\WINDOWS\system32> git --version git version 2.37.2.windows.2 PS C:\WINDOWS\system32>

RineshRamadhin commented 2 years ago

Looks alright, have you also cloned both the API and website repositories? Preferably to somewhere in your home directory.

If you haven't yet, you can do as follows:

  1. Open the folder where you want to clone the files in Windows File Explorer.
  2. Hold SHIFT and right-click somewhere in this folder.
  3. Select the Open PowerShell window here option.
  4. Run the following commands:
git clone https://github.com/web-dl-tools/api.git
git clone https://github.com/web-dl-tools/website.git

Two new folders should have appeared inside the folder in Windows File Explorer.

LuciferxR commented 2 years ago

I was successfully cloned 2 folder, how to run the program please tell me .

RineshRamadhin commented 2 years ago

Great. The only things left to do are to add some config values and then start it up.

For defining the config values both the API and website expect that there is a .env file available. An example file is available in both repo's (.env.dist). Now in order to perform this step you will need an editor that can view/edit dotfiles. Dotfiles are normally hidden in Windows File Explorer.

I'd personally recommend Visual Studio Code, but any other file editor will work (Sublime Text, VIM, etc.). Once you have one installed, you can follow the next steps:

  1. Open one of the repo's in the text editor.
  2. Make a copy of .env.dist called .env. Place it also in the root folder, alongside the template .env.dist file. Make sure you don't forget to add the dot at the beginning of the file name.
  3. Fill in the values in the .env file. You can refer to the documentation for additional information about each field.
  4. Repeat for the other repository.

image

Once you've done that both repositories should have a filled in .env file. You probably won't see it in Windows file Explorer, but when opening the folder in the text editor it should be there.