search

janreges / siteone-crawler-gui

Multi-platform desktop application with the included SiteOne Crawler, which will help you analyze the entire website in depth and recommend improvements, or export sitemap or an offline version of the entire website
https://crawler.siteone.io/
MIT License
41 stars 6 forks source link

Configuration of the output base directory #1

Open GitHub-Mike opened 1 month ago

GitHub-Mike commented 1 month ago

Is there a way to configure the output base directory? Currently the directory is created on the desktop of the logged in user, but I would like to move it to another drive. I am using the portable version 1.0.8 for Windows.

Almost forgotten. Thanks for making this project available in the GUI and CLI versions under the MIT license. I've been looking for an inexpensive alternative for the SF for a long time. And Xenu is getting a bit long in the tooth.

janreges commented 1 month ago

Hi @GitHub-Mike, I'm glad the tool helps you.

The Crawler GUI app is functional for Windows, macOS and Linux. When I was looking for a suitable placement that is well functional and usable on all platforms, the desktop placement worked everywhere, as one of the few.

If you are a developer and have the ability to research and try other placements to give the user the ability to change it, I would be very grateful.

The situation on Windows is also complicated by the fact that the CLI version of the crawler that the GUI app uses runs under cygwin, which is a virtual environment with its own paths.

Alternatively, it is possible to specify absolute paths starting with a slash in the settings in the screenshot below. But this will only work intuitively on macOS and Linux. On Windows there is the aforementioned cygwin and there it is more complicated. I also noticed when taking the screenshot that I got a validation error there and it's not possible to specify an absolute path. I will fix it in the next version.

image

GitHub-Mike commented 1 month ago

Hi Jan,

thanks for the quick reply and the detailed explanation.

My recommendation would be to create an environment variable for the base directory. Then everyone can decide for themselves whether to use a central base directory or set the paths selectively. If you "touch" the GUI anyway, you could use curly brackets or the percent sign.

In the meantime, I have found another solution. I have created the target directory in my desired location, on the other drive. And I have also created a symbolic link to this directory on the desktop. This works wonderfully.