Some component properties like FileWrite or SlackFilesUpload are making references to folders and file paths. On this page, we describe how files can be referenced in Gravio.
The Default Folder
All paths referenced on Gravio refer to the below paths on the respective operating systems:
Windows: C:\ProgramData\HubKit\action\actmgr\data\
Mac: /Library/Application Support/HubKit/action/scripts/actmgr/data/
Linux: /var/opt/hubkit/action/scripts/actmgr/data/
Linux with Docker (e.g. on a Raspberry Pi): /home/gravio/hubkitrepo4/data/actmgr/data/
which is then mounted on /var/opt/hubkit/actmgr/data
if you are accessing it from within Gravio.
Therefore you have 3 ways of making references to files:
1. Direct Reference
Mac and Linux:
File path | Description |
---|---|
sample.txt |
Sample.txt in the actmgr/data/ folder. |
./sample.txt |
Refers to sample.txt in the actmgr/data/ folder. |
Windows:
File path | Description |
---|---|
sample.txt |
Refers to sample.txt in the actmgr\data\ folder. |
.\\sample.txt |
Refers to sample.txt in the actmgr\data\ folder. |
2. Relative References
Mac and Linux:
File path | Description |
---|---|
../../../../gravio/sample.txt |
Refers to gravio/sample.txt 4 levels up from the actmgr/data/ folder. |
Windows:
File path | Description |
---|---|
..\\..\\..\\..\\gravio\\sample.txt |
Refers to gravio\\sample.txt , which is four levels up from the actmgr\data\ folder. |
3. Absolute References
Mac and Linux:
File path | Description |
---|---|
/home/gravio/sample.txt |
Refers to /home/gravio/sample.txt under the root. |
Windows:
File path | Description |
---|---|
c:\\temp\\sample.txt |
Refers to c:\temp\gravio\sample.txt under c: drive. |
In the example, it is assumed that the sample.txt file is readable by the user under which Gravio is operated.
Log Folders
Windows: C:\ProgramData\HubKit\logs\
Mac: /Library/Logs/HubKit/
Linux: /var/log/hubkit/
Need more help with this?
Join our slack community for help