starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #2455] Manual installation guide can be difficult to understand #1130

New issue

Closed

opened 2026-03-01 21:49:09 +03:00 by kerem · 5 comments

kerem commented

2026-03-01 21:49:09 +03:00

Owner

Originally created by @julisod on GitHub (Sep 11, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2455

Details

I had a lot of issues figuring out how to install Act, and I feel like I some people might have similar struggles. I didn't have any of the package managers installed, so I tried the bash script. It says that it's executable on any systems, but it didn't work for me on windows, so I assumed it works on unix systems. So I went for the manual installation.

First issue was that I didn't know which file to download since I didn't know what the difference between them was. Took me a while to figure out it was about the CPU architecture and then to also figure out which one I have.

Second issue was that I didn't know what adding something to the PATH variable meant and how to do that.

Maybe this is me not being skilled enough with computers, but it would be nice if the installation guide was made as easy to understand as possible. The instructions could be more detailed, or maybe include links to external sites that walk you through the individual steps.

Originally created by @julisod on GitHub (Sep 11, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2455 ### Details I had a lot of issues figuring out how to install Act, and I feel like I some people might have similar struggles. I didn't have any of the package managers installed, so I tried the bash script. It says that it's executable on any systems, but it didn't work for me on windows, so I assumed it works on unix systems. So I went for the [manual installation](https://nektosact.com/installation/#manual-download-of-prebuilt-executable). First issue was that I didn't know which file to download since I didn't know what the difference between them was. Took me a while to figure out it was about the CPU architecture and then to also figure out which one I have. Second issue was that I didn't know what adding something to the PATH variable meant and how to do that. Maybe this is me not being skilled enough with computers, but it would be nice if the installation guide was made as easy to understand as possible. The instructions could be more detailed, or maybe include links to external sites that walk you through the individual steps.

kerem

2026-03-01 21:49:09 +03:00

closed this issue
added the
stale

area/docs

kind/discussion
labels

kerem commented

2026-03-01 21:49:09 +03:00

Author

Owner

@sebastien-perpignane commented on GitHub (Sep 16, 2024):

First issue was that I didn't know which file to download since I didn't know what the difference between them was. Took me a while to figure out it was about the CPU architecture and then to also figure out which one I have.
Second issue was that I didn't know what adding something to the PATH variable meant and how to do that.

I read a lot of installation guides (I'm an old man) and, to be totally honest, act guide is perfectly clear.

Manually installing a software requires some skills. Understanding that you have different binaries for different CPU architectures and adding a command to the PATH are one of them.

Now I think you can perceive your experience with this installation guide from two points of view:

the installation guide needs to be more detailed
by trying to manually install act, you acquired new skills that are needed to install softwares manually

I think the 2nd option is the best one :)

@sebastien-perpignane commented on GitHub (Sep 16, 2024): > First issue was that I didn't know which file to download since I didn't know what the difference between them was. Took me a while to figure out it was about the CPU architecture and then to also figure out which one I have. Second issue was that I didn't know what adding something to the PATH variable meant and how to do that. I read a lot of installation guides (I'm an old man) and, to be totally honest, act guide is perfectly clear. Manually installing a software requires some skills. Understanding that you have different binaries for different CPU architectures and adding a command to the PATH are one of them. Now I think you can perceive your experience with this installation guide from two points of view: 1. the installation guide needs to be more detailed 2. by trying to manually install act, you acquired new skills that are needed to install softwares manually I think the 2nd option is the best one :)

kerem commented

2026-03-01 21:49:10 +03:00

Author

Owner

@TheFabulousDeath commented on GitHub (Sep 16, 2024):

I read a lot of installation guides (I'm an old man)

Not trying to gotcha you, but don't you think that's exactly why you would think that it is perfectly clear?

2. by trying to manually install act, you acquired new skills that are needed to install softwares manually

I guess we agree that if the installation guide was more detailed, it would make the experience better. Why shouldn't this be the resource from which someone learns to install programs manually?

I can't see why this wouldn't just combine the positives of 1 and 2.

@TheFabulousDeath commented on GitHub (Sep 16, 2024): > I read a lot of installation guides (I'm an old man) Not trying to gotcha you, but don't you think that's exactly why you would think that it is perfectly clear? > 2. by trying to manually install act, you acquired new skills that are needed to install softwares manually I guess we agree that if the installation guide was more detailed, it would make the experience better. Why shouldn't this be the resource from which someone learns to install programs manually? I can't see why this wouldn't just combine the positives of 1 and 2.

kerem commented

2026-03-01 21:49:10 +03:00

Author

Owner

@julisod commented on GitHub (Sep 16, 2024):

I know that it would've been easy if I was more experienced with installing programs manually, the point was more that I'm not 😢 I was thinking about how easy this would be to use for a newbie (me). Glad that I learned something new, but I was also close to just giving up because of the complexity.

This is just in case someone else ends up having the same problem, because if I'm the only one who would have this issue, it's not really an issue.

@julisod commented on GitHub (Sep 16, 2024): I know that it would've been easy if I was more experienced with installing programs manually, the point was more that I'm not 😢 I was thinking about how easy this would be to use for a newbie (me). Glad that I learned something new, but I was also close to just giving up because of the complexity. This is just in case someone else ends up having the same problem, because if I'm the only one who would have this issue, it's not really an issue.

kerem commented

2026-03-01 21:49:10 +03:00

Author

Owner

@sebastien-perpignane commented on GitHub (Sep 16, 2024):

@TheFabulousDeath

don't you think that's exactly why you would think that it is perfectly clear?

Hehe honestly, no :) I think it is perfectly clear because I read lot of installation guides not containing that level of details and not proposing 9 package managers to facilitate the process of installation instead of installing manually.

For example, the guide says:

You can unpack and run them in terminal specifying full path or add them to one of the paths included in PATH environment variable.

All you need to do is search "what is path environment variable" on your favorite search engine.

First result when using duck duck go is :

PATH is an environment variable on Unix-like operating systems, DOS, OS/2, and Microsoft Windows, specifying a set of directories where executable programs are located. In general, each executing process or user session has its own PATH setting

And what if a reader of the guide does not know what is an environment variable ? Do you think it should be explained in the act installation guide too ? Do you see what I mean ?

@julisod

I totally understand. I don't forget the time when I was a newbie and when these kinds of guide were difficult for me too. But a guide to install a specific program cannot also be a linux guide or a CPU architecture guide. It must consider that some prerequisites are already acquired. At least, that's what I think. Maybe the maintainers of act won't agree with me, after all :)

@sebastien-perpignane commented on GitHub (Sep 16, 2024): @TheFabulousDeath > don't you think that's exactly why you would think that it is perfectly clear? Hehe honestly, no :) I think it is perfectly clear because I read lot of installation guides not containing that level of details and not proposing **9** package managers to facilitate the process of installation instead of installing manually. For example, the guide says: > You can unpack and run them in terminal specifying full path or add them to one of the paths included in PATH environment variable. All you need to do is search "what is path environment variable" on your favorite search engine. First result when using duck duck go is : > PATH is an environment variable on Unix-like operating systems, DOS, OS/2, and Microsoft Windows, specifying a set of directories where executable programs are located. In general, each executing process or user session has its own PATH setting And what if a reader of the guide does not know what is an environment variable ? Do you think it should be explained in the act installation guide too ? Do you see what I mean ? @julisod I totally understand. I don't forget the time when I was a newbie and when these kinds of guide were difficult for me too. But a guide to install a specific program cannot also be a linux guide or a CPU architecture guide. It must consider that some prerequisites are already acquired. At least, that's what I think. Maybe the maintainers of act won't agree with me, after all :)

kerem commented

2026-03-01 21:49:10 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 16, 2025):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Mar 16, 2025): Issue is stale and will be closed in 14 days unless there is new activity

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1130

No description provided.

Rows
Columns