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

fix create_node and start_stop_node #1

Merged
merged 7 commits into from Feb 1, 2014
Merged

fix create_node and start_stop_node #1

merged 7 commits into from Feb 1, 2014

Conversation

leif
Copy link

@leif leif commented Jan 20, 2014

This makes create_node and start_stop_node able to work again. (I've merged this into my truckee branch and tested it successfully with my quickgrid.sh script there.)

See further comments at https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2045#comment:36

  - logdir -> incidents_dir
  - storedir -> storage_dir
  - removed unnecessary os.path.join
  - removed default "" argument to config.get (there is a None there anyway)
  turns out it was actually necessary if you want to run things
    allow create-introducer et al to set web.port, incidents_dir and tempdir
instead of relative to the basedir
this was actually returning None anyway, because these options are actually
present in the dictionary with values of None when they are not specified on
the commandline.
No web ui for introducers has been the default behavior for a long time, so
lets leave it that way now even though create-introducer can configure a
web.port now. This also makes the one test that was failing pass.
@meskio
Copy link
Owner

meskio commented Feb 1, 2014

They look good to me.

meskio added a commit that referenced this pull request Feb 1, 2014
fix create_node and start_stop_node
@meskio meskio merged commit 07e5915 into meskio:meskio Feb 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants