Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
We run 1.10.4 stable via Docker on Ubuntu 16.4 are fully synced and connect to ethereum mainnet.
It would be useful to support some form of log rotation. This would allow us to keep the node up 100% of the time while keeping disk space in check. This could either be managed internally (but of course means more things to maintain). Or it could be managed by support for a utility like `logrotate`. In order for something like that to work there needs to be a command to reload the log files.
[Nginx](https://www.digitalocean.com/community/tutorials/how-to-configure-logging-and-log-rotation-in-nginx-on-an-ubuntu-vps) for example does this via:
```kill -USR1 `cat /var/run/nginx.pid` ```
[Passenger](https://www.phusionpassenger.com/library/admin/standalone/log_rotation.html) has a similar option to reload application logs: