# Manually start filewalker

**URL:** <https://forum.storj.io/t/manually-start-filewalker/25698>\
**Category:** Ideas & Suggestions\
**Created:** [April 2, 2024, 5:25am UTC](https://forum.storj.io/t/manually-start-filewalker/25698 "2024-04-02T05:25:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Ambifacient](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/ambifacient/32/7815_2.png) [@Ambifacient](https://forum.storj.io/u/Ambifacient)\
**Post date:** [April 2, 2024, 2:08pm UTC](https://forum.storj.io/t/manually-start-filewalker/25698/6 "2024-04-02T14:08:31Z")

</div>

This is where the power of scripting comes in.

For example (need to first uncomment the line in the config):

```auto
#!/bin/bash
CONTAINER_NAME=storagenode
CONFIG_PATH=/mnt/storj/config.yaml

docker container stop $CONTAINER_NAME
sed -i "s/^storage2.piece-scan-on-startup: .*/storage2.piece-scan-on-startup: true/g" $CONFIG_PATH
docker container start $CONTAINER_NAME
sed -i "s/^storage2.piece-scan-on-startup: .*/storage2.piece-scan-on-startup: false/g" $CONFIG_PATH

```

However I do agree with having more feature rich APIs. It would be nice to start/stop filewalkers and query their status from the web API.

---

_[View the full topic](https://forum.storj.io/t/manually-start-filewalker/25698)._
