~dr|z3d
@RN
@StormyCloud
@T3s|4_
@postman
%Liorar
+FreefallHeavens_
+Xeha
+profetikla
+radakayot
AHON1
Arch
Dann
DeltaOreo
FreeB
Irc2PGuest22479
Irc2PGuest76366
Irc2PGuest8155
Irc2PGuest87933
Irc2PGuest90168
Meow
Onn4l7h
Onn4|7h
acetone_
ardu
boonst_
cumlord
eyedeekay
hk
maylay
not_bob_afk
orignal_
pisslord
poriori_
qend-irc2p
r00tobo
shiver_
simprelay
snex
solidx66_
thetia
u5657
uop23ip
usr002
weko
woodwose
zer0bitz_
zzz
dr|z3d
where are you putting the router.config files, StormyCloud? And when?
dr|z3d
essentially, when you start the router for the first time, it will create a new router.config file in ~/.i2p/ and that's when you need to edit the router.config file or copy over your template file.
zzz
not sure if the 'deployment package' is for $I2P only or includes .i2p -- if you don't have a config dir yet, it will copy over anything from $I2P/router.config if present, which it usually is not
zzz
but if you have a ~.i2p/router.config already, it won't
zzz
or even just a ~/.i2p at all might be enough to prevent the first-install logic from happening
zzz
obviously the deployment package contained a .i2p dir with an identity, which really isn't safe to do it that way
dr|z3d
yeah, that's what I thought, and then I noticed we don't have a router.config file in i2p/
zzz
just have a $I2P dir with the default settings you want in a router.config file in there.
dr|z3d
so drop the router.config file in i2p/ and all's good, then, StormyCloud
zzz
correct, it isn't normally there, but if it is there we'll migrate it to the config dir, so you can do stuff like this safely
dr|z3d
ok, noted.
zzz
no drz. if you want a 'deployment package' thats the right way to do it, with a default router.config in there
dr|z3d
I say all's good, StormyCloud, but you'd drop the router.config file in i2p/ _before_ you run for the first time. :)
zzz
just don't include a .i2p dir at all in the package, let the first-install logic do its thing
dr|z3d
yup, yup, got it.
zzz
you don't need to remove $I2P/router.config, the only time we look at it is on first install
zzz
* first run
zzz
so you can put your port 7777 in there, for example
dr|z3d
if I had the energy, I'd probably code up a webui to create a custom deployment setup with default configs, tunnels etc. maybe someone else has the energy? :)
dr|z3d
or maybe an export settings from /configadvanced would be sufficient, where it adds the rebuildKeys config to the existing router.config, strips all the crud, and then presents a router.config file.
zzz
there's a hundred ways to do it, the flaw here was not checking that it worked
dr|z3d
true, true.
zzz
maybe, but I don't think there's any way to anticipate the requirements of a custom deployer and then write a packager
zzz
does he want an existing netdb to avoid reseeding? profiles? addressbook?
dr|z3d
I was thinking just the router.config file, not the full 9 yards.
zzz
yeah, but even then
StormyCloud
Tbf this is how my last deployment was done but I did not double check so that’s on me. I get home in 30mins so I can give the general workflow but something is missing the mark.
zzz
no need for a post-mortem StormyCloud. just do your thing