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

Allow changing the path that oasis uses for ssb stuff (i.e. normally ~/.ssb/) #589

Open
Powersource opened this issue Jan 28, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@Powersource
Copy link
Collaborator

Powersource commented Jan 28, 2021

What's the problem you want solved?

When developing oasis you often want to e.g. publish messages just to test that things are working a certain way, but you don't want those test messages to end up in your normal profile/network. E.g. @lindskog is working on #537 right now and is posting fruit to see how the bug works/if it's fixed (not calling her out :P , I'd do it too).

Is there a solution you'd like to recommend?

Adding (if it doesn't exist) and documenting a command line option --path that sets where to store ssb related files.

I think I read some time ago that this was possible but I can't find it documented anywhere. Either way patchwork has this flag and that helped me while I was working on the peer invites PR, it let me make a new profile on the same machine that I could then try inviting.

@Powersource Powersource changed the title Allow changing the path that oasis uses for ssb stuff (i.e. normally Allow changing the path that oasis uses for ssb stuff (i.e. normally ~/.ssb/) Jan 28, 2021
@Powersource Powersource added documentation Improvements or additions to documentation enhancement New feature or request labels Jan 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Development

No branches or pull requests

1 participant