Windows installation issues about atlas

[rotemtam]

Hi @int-2147483647,

Thanks so much for trying Atlas and reaching out!

We are actively working on fixing code signing so the onboarding process doesn't have this kind of friction.
I don't want to make promises but I hope that the next patch release (v0.3.1) that should be out tomorrow will have this.

[int-2147483647]

Hi, @yonidavidson
TBH I don't have personal experience with distributing a CLI but for comparison, I would follow Azures steps on how to install Terraform (https://tinyurl.com/57mtbxej)

1. Download Terraform - A zip file containing the executable. It is important to call the executable atlas.
2. Extract the executable to a specific folder that will be added to PATH.
3. Update the PATH environment variable to include this folder (https://stackoverflow.com/questions/1618280/where-can-i-set-path-to-make-exe-on-windows)
4. Open a new terminal window and run atlas (this is why its important that the executable is called atlas)

If a "Publisher Registration" is still necessary to avoid the Defender warnings, then I suppose these steps are required: https://docs.microsoft.com/en-us/azure/active-directory/develop/mark-app-as-publisher-verified

[int-2147483647]

@yonidavidson I just realized that you can also use Powershell.
Invoke-WebRequest -Uri https://release.ariga.io/atlas/atlas-windows-amd64-v0.3.0.exe -OutFile atlas.exe

But it is important that the OutFile will be in directory that is in %path%

[yonidavidson]

@int-2147483647 Hi, do you have any recommendations for the distribution of the CLI in windows? I looked at https://scoop.sh/, and some CLI's are distributed as MSI.

Do you have some experience with creating such releases? I would like to hear your thoughts.

[yonidavidson]

Thanks, @int-2147483647 for your great insights.
I will also handle the publisher registration process soon.

[masseelch]

Hey, closing this as you found a solution.