updated readme
This commit is contained in:
15
README.md
15
README.md
@ -54,6 +54,21 @@ format, but it only supports the following options:
|
||||
Also it doesn't support sections. Didn't realize that at first. Will address
|
||||
soon.
|
||||
|
||||
## Static eepsite in like no seconds
|
||||
|
||||
Using this port forwarder, it's possible to create an instant eepsite from a
|
||||
folder full of html files(and the resources they call upon). Probably obviously
|
||||
to everybody reading this right now, but maybe not obviously to everyone reading
|
||||
this forever. A go application that does this I call eephttpd can be built with
|
||||
the command:
|
||||
|
||||
make server
|
||||
|
||||
and run from ./bin/eephttpd. The default behavior is to look for the files to
|
||||
serve under the current directory in ./www. It can be configured to behave
|
||||
differently according to the rules in [USAGE.md](USAGE.md). A Dockerfile is also
|
||||
available.
|
||||
|
||||
## Quick-And-Dirty i2p-enabled golang web applications
|
||||
|
||||
Normal web applications can easily add the ability to serve itself over i2p by
|
||||
|
@ -57,6 +57,21 @@ format, but it only supports the following options:
|
||||
Also it doesn't support sections. Didn't realize that at first. Will address
|
||||
soon.
|
||||
|
||||
## Static eepsite in like no seconds
|
||||
|
||||
Using this port forwarder, it's possible to create an instant eepsite from a
|
||||
folder full of html files(and the resources they call upon). Probably obviously
|
||||
to everybody reading this right now, but maybe not obviously to everyone reading
|
||||
this forever. A go application that does this I call eephttpd can be built with
|
||||
the command:
|
||||
|
||||
make server
|
||||
|
||||
and run from ./bin/eephttpd. The default behavior is to look for the files to
|
||||
serve under the current directory in ./www. It can be configured to behave
|
||||
differently according to the rules in [USAGE.md](USAGE.md). A Dockerfile is also
|
||||
available.
|
||||
|
||||
## Quick-And-Dirty i2p-enabled golang web applications
|
||||
|
||||
Normal web applications can easily add the ability to serve itself over i2p by
|
||||
@ -142,12 +157,12 @@ their own projects. An i2p-native static site generator in the style of jekyll
|
||||
(but in go) could be cool.
|
||||
-----BEGIN PGP SIGNATURE-----
|
||||
|
||||
iQEzBAEBCAAdFiEEcNIGBzi++AUjrK/311wDs5teFOEFAltrX4UACgkQ11wDs5te
|
||||
FOHGTAgAl7/56Z/ZU8/xjWFzEfRmp/036vZu63y4j9cyeT+MnRsRAUh6tgMPHIN1
|
||||
7ydkpEVU4eGmLYidkpG0dZnrhNeg1Maqkj2/POZLR5XsJaeM6UjMRDV+dflTfT+V
|
||||
M1puTV15SNhX5OOtO2c/EGR/31yvv6LDG+7u7VqlOgwC6irFvGzx2WVfaXiflPdR
|
||||
g/v406N/7rlk8V0vZYoGVZ+9rinhJbYQOoR5ef+ZSb9N/iygFnx+Drxs9WH8oI3o
|
||||
G5eaAo/mcBne4I5eOced9xOwqbv9KNXeSNTNHULmFfypmiFdD3RF30RLBVmj42Bq
|
||||
iYvHQBXbUr85+fCTk5t3/q5W+HvQIQ==
|
||||
=Xs/g
|
||||
iQEzBAEBCAAdFiEEcNIGBzi++AUjrK/311wDs5teFOEFAltrYfwACgkQ11wDs5te
|
||||
FOFuuwf8DWWFPTPtwTaxLJD7+P6/5WSohTU3j9FLgndK45GDs614HE727vcpyeov
|
||||
gMUo4cxpVCQsXDGzsnBzlWGrsCG93QPO83zzxZ4Z/GSNi7XwVWYWyeqbYCh0P5Jg
|
||||
jU/odscCHyeoiUu/8LXFc+Bxnd1ZJH9ihGTBC3mXPdcmrXIJRNLebEMnsLMCZRjO
|
||||
ZSRdy1gnmGdxjIPQ31qDRqQYn46ITGm3mkPSB4H1XuCbzFP2GG6bFMu1ncrd15Un
|
||||
/LZkKJEQYYgY8amoVYEgVmBUJnVk4tqxPEIL52sztg0u55BH4JMCSqaEYUdqeT+9
|
||||
SX56L+X0FG/ZECZDjf7wNV+ps3AsjQ==
|
||||
=0gal
|
||||
-----END PGP SIGNATURE-----
|
||||
|
Reference in New Issue
Block a user