Package Details: zeronet-git 0.6.0-1

Git Clone URL: https://aur.archlinux.org/zeronet-git.git (read-only)
Package Base: zeronet-git
Description: Decentralized websites using Bitcoin crypto and the BitTorrent network.
Upstream URL: https://zeronet.io/
Licenses: GPL2
Conflicts: zeronet
Provides: zeronet
Submitter: lothar_m
Maintainer: redfish
Last Packager: redfish
Votes: 22
Popularity: 0.464121
First Submitted: 2015-06-20 08:38
Last Updated: 2017-11-18 21:02

Dependencies (5)

Required by (0)

Sources (3)

Pinned Comments

redfish commented on 2016-03-15 06:01

MANUAL INTERVENTION REQUIRED ON THIS UPGRADE (to 0.3.6): data dir is now set to /var/lib/zeronet in zeronet.conf; upgrade script will create the dir, but you need to 'mv /opt/zeronet/data/* /var/lib/zeronet/'.

Log dir set to /var/log/zeronet for consistency, but daemon logs are in systemd journal.

@SplitFire: thanks, changed tmpfs /var/run/tor to /var/lib/tor-auth (until Tor Arch repo updates Tor to 0.2.8); removed redundant CookieAuth; chmod -R not needed, since that dir is created, it's empty.

Latest Comments

giowck commented on 2017-04-05 13:07

To make tor work I had to add the following additional line to the /etc/tor/torrc file, in addition to the ones mentioned in the wiki and post install message:
ControlPort 9051

And if you want zeronet to be able to change the config file, for example when clicking on tor modus only from the web interface, then you need to make /etc/zeronet.conf editable for the zeronet user:
sudo chown zeronet:zeronet /etc/zeronet.conf

pmgouveia commented on 2017-03-26 00:06

I made it run by installing docker and running it in docker:

install docker as root:
# pacman -S docker
starting docker:
# systemctl start docker

install the zeronet-git with yaourt:
$ yaourt -S zeronet-git

run the docker image
$ docker run -d -e "ENABLE_TOR=true" -v /opt/zeronet/:/root/data -p 15441:15441 -p 127.0.0.1:43110:43110 nofish/zeronet

and then visit: http://127.0.0.1:43110/

JZA commented on 2017-03-05 09:58

expiriencing issues with python2-gevent not finding coros.py anyone have this problem?

Gaming4JC commented on 2017-02-05 22:42

I bumped into a an issues with this package, here are the fixes:

1) Make sure and mention that Control Port has to be added to torrc (else it fails to start properly)
>>> Add/edit the following options in /etc/tor/torrc:
>>> ControlPort 9051
...

2) Consider adding sane defaults to zeronet.conf that match Arch's TOR build:
## Fix TOR connection by using default ports
echo "tor_controller = 127.0.0.1:9051" >> $pkgdir/etc/zeronet.conf
echo "tor_proxy = 127.0.0.1:9050" >> $pkgdir/etc/zeronet.conf

3) All PKGBUILDs should be using git+https:// in the source array, and SHA512sum is preferred for hashes.

After that it's all green in ZeroNet and appears to be functional.

redfish commented on 2016-11-19 20:07

@ZerataX: the directory must be owned by zeronet user:
sudo chown -R zeronet:zeronet /path/to/dir

But, keep in mind, that you need to 'sudo -u zeronet zeronet.py ...' for any commands to run them as zeronet user. Also, 'journalctl -u zeronet' will show you the log to know the exact error why zeronet does not start.

ZerataX commented on 2016-11-18 16:47

If I want to move the data folder to my home folder what would I need to do,
besides editing /etc/zeronet.config
I've tried that and couldn't start zeronet anymore.
I imagine it's some kind of permission problem.

dmp1ce commented on 2016-10-12 21:39

I think you should also include opening the ControlPort in your instructions. I needed to uncomment the ControlPort on my system.

ControlPort 9051

redfish commented on 2016-05-25 15:14

@FlyingJay1: Upstream follows a convention of "pushing" a new version to the nodes before releasing that version on github. If you run latest release from github, or zeronet package, it will complain that 'new version available'. This package zeronet-git takes latest master, and version is in src/Config.py (PKGBUILD's pkgver extracts the version from that file).

FlyingJay1 commented on 2016-05-24 07:36

How come the latest version on github is 0.3.6 and this package is 0.3.7. Where does 0.3.7 come from?

redfish commented on 2016-04-29 04:47

@SplitFire: the pkg ver is extracted from upstream source, so if you actually build the package, it will build as the correct version automatically (now, 0.3.7.xxxxxx). The version on the website is from the .SRCINFO file. I agree that it makes sense to manually bump the .SRCINFO version to match the pkg ver, so I'll do that on every release, along with upgrading the 'zeronet' pkg.

All comments