Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change gofer to output node-identity.json to /var/tmp #4

Open
ross-spencer opened this issue Nov 21, 2024 · 2 comments
Open

Change gofer to output node-identity.json to /var/tmp #4

ross-spencer opened this issue Nov 21, 2024 · 2 comments

Comments

@ross-spencer
Copy link
Member

Describe the issue

The file needs to persist or be recreated on reboot therefore it is better if it is in a more persistent location on the node's hard-drive.


What component or features of Orcfax are affected?

  • gofer

Provide any further information

Good practice should be to create a default location /var/tmp/node-identity.json with the possibility of over-riding this as required.


@ross-spencer
Copy link
Member Author

NB. while it exists in /tmp folks might want to check its existence before the node runs. If it doesn't exist, it is recreated. TODO: add to docs.

@ross-spencer
Copy link
Member Author

Via the helpful A4EVR pool. https://github.com/A4EVR/A4EVR-Pool/blob/fcd44611cc269b98d9291ef4675be73ba84df75d/orcfax/node-suite/orcfax_node_suite.sh

# Check if .node-identity.json exists in /tmp
if [ ! -f /tmp/.node-identity.json ]; then
    echo "Creating .node-identity.json..."
    # Run gofer to generate the .node-identity.json if it doesn't exist
    /orcfax/$NODE_NAME/gofer/gofer data ADA/USD -o orcfax
else
    echo ".node-identity.json already exists."
fi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant